How the Windows Subsystem for Linux Redirects Syscalls
I use to run Linux in a VM on windows and use Chocolatey for package management and cygwin and powershell etc, then I realized I was just trying to make Windows into Linux. Seems to be the way things are going and with the addition of the linux subsystem it kind of proves that Windows really isn&#x27;t a good OS on it&#x27;s own, especially not for developers.<p>I wish Windows&#x2F;MS would abandon NT and just create a Linux distro. I don&#x27;t know anyone who particularly likes NT and jamming multiple systems together seems like an awful idea.<p>Windows services and Linux services likely won&#x27;t play nice together (think long file paths created by Linux services and other incompatibilities), for them to be 100% backward compatible they need to not only make Windows compatible with the things Linux outputs, but Linux compatible with the things windows services output, and to keep the Linux people from figuring out how to use Windows on Linux systems they&#x27;d need to make a lot of what they do closed source.<p>So I don&#x27;t see a Linux+Windows setup being deployed for production. It&#x27;s cool for developers, but even then you can&#x27;t do much real world stuff that utilizes both windows and Linux. If you&#x27;re only taking advantage of one system then whats the point of having two?<p>I went ahead and made the switch to Linux since I was trying to make Windows behave just like Linux.