Now, you still need virtualization for a ServerOS - WSL is all running under Bash.exe, so when that exits - everything is gone.
But, for client OS - It's the bomb.
And now that they are planning on supporting Fedora, Suse, and Ubuntu environments, I can yum install, or just drop in-place any of the Redhat binaries as well.
That's the big difference - I don't need cygwin compiled apps anymore - I just drop in the Linux variants and I am good to go.
I word: laptops.
I've used a laptop as my primary dev environment for years. During that time I ran Debian on ThinkPads. Compared to Windows you paid a price in terms of higher power consumption and randomly breaking sleep and hibernate, not to mention poorer plug-and-play multi monitor/dock support. Add in unpredictable driver support and my newest laptop just runs Windows 10. If I need to use Linux I'll do so via WSL or VMs.
On the other hand how often you do real work without AC ?
Aircraft and buses are common locations, but even when I'm coding on the couch I appreciate not being tethered to an outlet.
And the sleep/hibernate problems are equally if not more important. I need to be able to close my laptop and reopen it without it consistently crashing. Debian Sid had a good stretch for a while there but right around the move to systemd things destabilized again and I'm just done with it.
More generally, Linux just fails on a laptop. See the comments here:
https://www.reddit.com/r/linux/comments/48y2db/system76_lapt...
And that's for a laptop designed to work with Linux.
Again, I have deep familiarity with running Linux on a laptop, having done so for over 10 years. Debian running on my old Lenovo T410 worked okay. Most of the time. Well, for a while, anyway. Assuming I could live with 2-3 hours of battery life and apt-get update resulting in random hardware breakage.
Heard lot of good about using better laptop with this https://www.neverware.com/ - still it's unclear how reliable it's