Two weeks ago, I published an article in which I explained what was wrong about Randall Kennedy’s “Windows 7 Unmasked” article. This was noted by Infoworld’s editor-in-chief Eric Knorr, who suggested that Randall and I enter into an email debate regarding the various points made in our articles. We agreed upon publishing this email thread as-is, unedited (I didn’t even fix the spelling errors), on both Infoworld and OSNews. We agreed that Randall would start the debate, and that I had the final word. Read on for the entertaining email debate (I figured it would be best to give each email its own page, for clarity’s sake. My apologies if this makes each individual page much shorter than what you’re used to from OSNews).
As a software developer I am fully agree from the functionality that kernel thread count means a new functionality. Windows have a huge legacy and every subsystem that exists will have an impact on performance. Adding new subsystems to Windows will increase the thread count, so adding any functionality/services, major revamp to Windows will introduce new threads. Optimizations in algorithms and fixes will not justify enough to increase the version number.
Thom seems for me wrong (again as a devel) because the services of Windows cannot be removed without making some other to complain.
Thom shows anyway a logic that may be possible in Linux for instance (that’s why it scales from mobile phones to super-computers) that you can remove functionality from kernel as much as you need to fit on your machine.
Probably the Windows Server 2008+1 will have the possibility to strip down the installations and the kernel, but I think is unlikely that persons wants to deploy one OS that will not give to you the guarantee that all you had yesterday you cannot run tomorrow.
Randall have right as much it knows the back of the development of NT kernel. Changing the policy of developing the NT kernel may lead that the thread measure is not right, but for now is really valid.