11–20 of 67 posts
> "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?
Especially many tools out there for DevOps have *nix first flavor to them.
Earlier quoted context omitted.
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".
> "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?
The majority of web applications use languages with runtimes that hide any Linux specific features.
Given that the majority of enterprises allow only for Windows desktops, and won't pay for OS X machines, this is an appealing path to Ruby, Python, Erlang, Java, .NET Core, ... server based applications on azure cloud deployments.
I am not even joking. In the next few years we are going to see Linux on the desktop!
Google is busy with ChromeOS/Linux and Android/Linux.
Apple keeps developing their NeXTSTEP/BSD derivative.
> "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?
If you imagine WSL for Windows Server not as competition for CentOS and Debian, but as competition for "enterprise Linux", then you can have a compelling sales case for enterprises which are already heavily invested in Microsoft, i.e. with extensive Active Directory and Office 365 deployments. Why purchase two support contracts, one from Microsoft and one from Enterpise Linux Vendor X, when you can buy just one support contract from Microsoft and still run everything you need?
Earlier quoted context omitted.
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.
I am not even joking. In the next few years we are going to see Linux on the desktop!
Not really because what Microsoft is doing is actually GNU/Windows. Google is busy with ChromeOS/Linux and Android/Linux. Apple keeps developing their NeXTSTEP/BSD derivative.
I'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…
I'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.
I'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.