4 ms·
Are those final two steps (next, final) pure speculation on your part? I'd be surprised if Windows threw out NT and moved to Linux kernel, and yet at the same t
by noveltyaccount 4y ago
Are those final two steps (next, final) pure speculation on your part? I'd be surprised if Windows threw out NT and moved to Linux kernel, and yet at the same time, it sounds like a great idea IMO (WSL2 + Docker is already a great experience for software development).
- stevewatson301 4y agoNot the parent commenter but this isn’t as far fetched as it seems. Since much is abstracted by the Win32 and other APIs, they could write something to do exactly this.
- layer8 4y agoThis seems unlikely to me. For example, the threading model (non-forking) and file system semantics (locking, permissions, etc.) are wildly different. You’d need a complex compatibility layer and effectively two classes of applications (legacy and linux-y).
- yazaddaruvala 4y agoIf they can build WSL2, and WINE can be built without MSFTs help, I’m not sure what is left to doubt. At that point the only question is “Is the one time cost of building the compat layer less than the ongoing cost of improving NT? Building windows specific drivers? Etc”. “One time cost” is always going to win the negotiation in the long run.
- yazaddaruvala 4y agoPure speculation! but the more I write about it, the more it’s likely to get read by a Microsoft VP, and the more it’s likely to happen :) That said, truly it’s a no brainer. For the future of Microsoft, all paths lead to windows/linux (maybe windows/bsd but way way less likely).