corysama, I agree. Windows was really lacking in any type of native unix connectivity. No native ssh, sftp support is a big one. You can get free third party programs for that, but nothing beats opening a terminal and having all of it, especially if that's what you are accustomed to.
I really love the new shell in Windows. I'm so glad they broke away from their old mindset.
The target demographic is developers of Linux server software. A lot of those devs today run macOS
That's a huge pain in the ass for those of us who work in things that are tied to win32(graphics, gamedev tools, etc) we happily contribute back but ripping out a working port just seems petty.
I have to maintain a separate build system for Windows, all the win32 specific code, and also test under Windows... and most of this requires a Windows license
if I can rip all of that out by outsourcing the compatibility testing to Microsoft: all the better, even if I have to add a line to the documentation requiring users to check a checkbox once in some control panel somewhere
Shouldn't you be happy that WSL will enable F/OSS devs to write cross-platform software much easier by not having to keep two sets of code?
However if you're goal is to have an impact with your software then supporting win32 is a good bet since you're going to find an order of magnitude more users on win32. You'll also probably want iOS, Android and other platforms that aren't drop-in ports for POSIX if you want to provide a reasonable interface.
Maybe OP is talking about tools installed on his/her own system only?
(I'm curious if you've used it or you're just commenting based on the headline?)
They explicitly don't support that. From the article:
> Linux distro's [sic] running atop WSL are for interactive user scenarios, NOT for running production workloads on Apache/nginx/MySQL/MongoDB/etc.
And the last time I checked, it's not suitable for services. The moment I closed the bash terminal, all the processes I had running through WSL terminated - including nginx and tomcat.
It really seems like the primary use case is supporting Docker/OCI containers for local dev, so you can keep using a Windows desktop instead of switching to a Linux one.
In addition to the feature needing to be manually installed, developer-mode must be enabled. WSL leaving beta does not appear to change that.
If the feature was installed by default, and an X server was bundled, it would risk the Windows platform. WSL allows developers to be placated without affecting the business side of the platform.
not sure that was what Microsoft was going for though...