Windows Subsystem for Linux on Windows Server
blogs.windows.com
Windows Subsystem for Linux on Windows Server
1–10 of 67 posts
Re: Windows Subsystem for Linux on Windows Server
#2> "you cannot currently use WSL to run persistent Linux services, daemons, jobs, etc. as background tasks."
Still, this has me wondering if that's the ultimate goal here. Is Microsoft trying to position Windows 10 as a high quality Linux server in the long-term?
Re: Windows Subsystem for Linux on Windows Server
#3I've been using WSL on Windows 10 since it's release. I'd love to know the inside story of how it came to be. A lot of companies would never try something like this.
For me WSL has worked as perfect as could be expected, nothing failed to run that I need yet. The gaps are being slowly closed (e.g. executing between WSL/Windows). I no longer have to develop in a VM, nor be forced to use a Mac just because it has "unix" under the hood.
Re: Windows Subsystem for Linux on Windows Server
#4> "you cannot currently use WSL to run persistent Linux services, daemons, jobs, etc. as background tasks." Still, this has me wondering if that's the ultimate goal here. Is Microsoft trying to position Windows 10 as a high quality Linux server in the long-term?
this is not the first time microsoft has done this.
https://en.wikipedia.org/wiki/Windows_Services_for_UNIX
one could even argue they are somewhere between the embrace and extend phase.
Re: Windows Subsystem for Linux on Windows Server
#5> "you cannot currently use WSL to run persistent Linux services, daemons, jobs, etc. as background tasks." Still, this has me wondering if that's the ultimate goal here. Is Microsoft trying to position Windows 10 as a high quality Linux server in the long-term?
I came here to wonder the same. Is the key word in this sentence "cannot" or "currently"?
Do they to force win32 to continue to be a viable server platform, by forever restricting reliable Linux daemons, or do they eventually want to allow Windows to be a viable Linux server?
Re: Windows Subsystem for Linux on Windows Server
#6> "you cannot currently use WSL to run persistent Linux services, daemons, jobs, etc. as background tasks." Still, this has me wondering if that's the ultimate goal here. Is Microsoft trying to position Windows 10 as a high quality Linux server in the long-term?
I only see value for Windows as a desktop OS, and I think the intent of WSL is improving the dev experience on Windows.
If you need a high quality Linux server, why not just run Linux?
Re: Windows Subsystem for Linux on Windows Server
#7> "you cannot currently use WSL to run persistent Linux services, daemons, jobs, etc. as background tasks." Still, this has me wondering if that's the ultimate goal here. Is Microsoft trying to position Windows 10 as a high quality Linux server in the long-term?
I only see value for Windows as a desktop OS, and I think the intent of WSL is improving the dev experience on Windows. If you need a high quality Linux server, why not just run Linux?
For the same reason people use OS X to actually develop applications that will actually run on GNU/Linux.
Re: Windows Subsystem for Linux on Windows Server
#8I am not even joking. In the next few years we are going to see Linux on the desktop!
Re: Windows Subsystem for Linux on Windows Server
#9> "you cannot currently use WSL to run persistent Linux services, daemons, jobs, etc. as background tasks." Still, this has me wondering if that's the ultimate goal here. Is Microsoft trying to position Windows 10 as a high quality Linux server in the long-term?
this is not the first time microsoft has done this. https://en.wikipedia.org/wiki/Windows_Services_for_UNIX one could even argue they are somewhere between the embrace and extend phase.
> one could even argue they are somewhere between the embrace and extend phase.
I see it more as grasping at straws to stay relevant. The Ballmer-era FUD campaign was mostly a failure (and bad PR). "If you can't beat 'em, join 'em".
Re: Windows Subsystem for Linux on Windows Server
#10I've been using WSL on Windows 10 since it's release. I'd love to know the inside story of how it came to be. A lot of companies would never try something like this. For me WSL has worked as perfect as could be expected, nothing failed to run that I need yet. The gaps are being slowly closed (e.g. executing between WSL/Windows). I no longer have to develop in a VM, nor be forced to use a Mac just because it has "unix…
NT has had support for "personalities" since its inception. This is not even the first *NIX one it has had :)
Still, I agree that it's an impressive achievement.