3 ms·
Microsoft could still open source some or all of the NT kernel and try to compete for mindset. It's still incredible how much work they put into porting the NT
by WorldMaker 3y ago
Microsoft could still open source some or all of the NT kernel and try to compete for mindset. It's still incredible how much work they put into porting the NT Kernel for some embedded scenarios (you can run it on a Raspberry Pi or things smaller than it) in the Windows 10 lifetime but couldn't seem to understand why more people weren't licensing it more when Linux is cheap as free for embedding. Even when Microsoft went to "free licenses" (still with too many caveats such as type and size of screen attached) the open source appeal was hard to get past.
I'm still somewhat surprised with all of Microsoft's cloud focus and how much of Windows is getting open sourced that the NT Kernel itself hasn't been a priority to win back embedded applications that Microsoft has lost to Linux especially. I certainly understand the massive sunk costs in the NT Kernel that some accountants would see it as too much very expensive proprietary R&D, but it's still interesting to imagine what would happen if Microsoft got over that hump, even if they kept the Win32 userspace and most of the rest of Windows proprietary.
- floating-io 3y agoIt may be that they can't release it open source. How much of other peoples' proprietary code is in that kernel? To be clear, I'm not talking illegal theft or anything of the sort -- but it's quite possible that they've licensed things over the years (code, patents, ...) and thus cannot open source it. Not saying this is or isn't true, just something to consider when trying to figure out the why of things.
- chasil 3y agoActually, a lot of the kernel code has leaked in the past, so this question can be independently answered. I know that there were a few leaks at different times. Some of it appears to be here: https://github.com/0x5bfa/NT5.1 https://github.com/0x5bfa/NT5.1
- WorldMaker 3y agoThey did finally kick their fork of Adobe's Type 1 Font Manager out of the Kernel in recent years (somewhere in the middle of Windows 10 as I recall), so that's definitely a complication to expect.