One hundred comments here and practically none of them are about the technical content of the article.
It gives a fascinating history of technical developments in Windows kernel scheduling. For example how they solved a scaling bottleneck exemplified by poor SQL Server performance, through introducing finer grained locking. Or the challenges of heterogenous scheduling on certain 64-bit ARM processors, in ensuring service performance isn't degraded for foreground processes.
But all the fools' gallery of HN can muster up is whining about SKUs, mumbling about the cost of licences, complaining about the Windows 10 UI, fantasizing about Linux, or making irrelevant wisecracks.
For a community that prides itself on the hacker mentality and the curiosity that comes with it, you lot certainly don't show it. Idiots.
It gives a fascinating history of technical developments in Windows kernel scheduling. For example how they solved a scaling bottleneck exemplified by poor SQL Server performance, through introducing finer grained locking. Or the challenges of heterogenous scheduling on certain 64-bit ARM processors, in ensuring service performance isn't degraded for foreground processes.
But all the fools' gallery of HN can muster up is whining about SKUs, mumbling about the cost of licences, complaining about the Windows 10 UI, fantasizing about Linux, or making irrelevant wisecracks.
For a community that prides itself on the hacker mentality and the curiosity that comes with it, you lot certainly don't show it. Idiots.