<story><title>One Windows Kernel</title><url>https://techcommunity.microsoft.com/t5/Windows-Kernel-Internals/One-Windows-Kernel/ba-p/267142</url></story><parent_chain></parent_chain><comment><author>detuur</author><text>&amp;gt;The most amazing aspect of all this is that the core of Windows, its kernel, remains virtually unchanged on all these architectures and SKUs.&lt;p&gt;Is that really such an exciting concept? Maybe I have a poor understanding, but I&amp;#x27;ve been under the impression that nearly every competing kernel (Linux, Darwin, *BSD) is exactly like that. The only situation where I can imagine a slight departure is Solaris and its SPARC architecture, where SPARC had certain features to specifically to tie in with the kernel but I&amp;#x27;m sure it still compiled to foreign architectures from the same codebase.</text></comment>
<story><title>One Windows Kernel</title><url>https://techcommunity.microsoft.com/t5/Windows-Kernel-Internals/One-Windows-Kernel/ba-p/267142</url></story><parent_chain></parent_chain><comment><author>tialaramex</author><text>This seems like it&amp;#x27;s essentially confessing to something we already knew. Back at the turn of the century Microsoft liked to claim that Windows Server and the ordinary client NT were different in some important way beyond just the branding and price. People would even try to argue that Linux couldn&amp;#x27;t be a &amp;quot;real&amp;quot; desktop OS because it lacked some kind of secret sauce not found in a server OS... Hackers eventually found out how to tell a client NT kernel to behave exactly like Server, because of course they are the same kernel, duh.&lt;p&gt;Microsoft&amp;#x27;s reaction was to stop selling the two next to each other. There is no Windows 10 Server and Windows Server 2019 doesn&amp;#x27;t have a client version. So the exact same thing continues, but now there IS no equivalent product to prove the point that they&amp;#x27;re identical bar branding and price.</text></comment>