I bought a laptop with W10, mainly to use WSfL on it. Only after updating to the insider preview and then scratching my head for a bit, did I learn that WSfL is only available for 64-bit Windows. The laptop, however (Bay Trail-based), has a 32-bit UEFI, with which 64-bit Windows refuses to install.
I'm dual-booting (amd64) Arch for now; the first distro whose installer played nicely with the funky UEFI setup _and_ F2FS. But I'm really impressed with the W10 on this laptop. If only it could provide a native UNIX experience...
1. http://www.infoworld.com/article/3120888/open-source-tools/n...
I've been using Linux for > 15 years and my emacs config is older than git. (Repo was converted from svn to darcs to hg to git over many years.) Now windows purports to run Linux binaries, has a tiling window manager and good command lines. Is it worth considering as a primary os?
For most technical work, hacking, most coding, Linux is the way to go. .NET being a notable exception. I don't have experience of powershell but it doesn't make much sense to me to use anything but *NIX if you're hacking, eg bash is the de facto standard shell.
If you're using a laptop, Windows still has big advantages in terms of drivers, "just working" etc. But then I'd buy a MacBook anyway.
The general UI is fine with Windows 10. I actually prefer the task bar to OS X's dock and definitely to Unity.
But overall I find things still don't work here and there. Stuff randomly crashes still, you do find yourself restarting and reinstalling things. And I've only been using it rarely (colleague insist on using Windows).
In a word, I guess, "no".
If you just focus on the LXSS, windows 10 isn't bad[0]. It's still effectively beta, so there are things it can't do, like list running windows processes and kill them from the command line or launching a windows app[1].
Development is identical between my ubuntu machine and my windows machine. I use ack, vim and other command line tools as my IDE and I haven't noticed much difference between the systems. I do occasionally run into an issue with live code reloading systems (like middleman-livereload). It looks for a valid ip address to use instead of just using 127.0.0.1, but the networking subsystem hasn't been exposed to LXSS yet, so it errors out. webpack-livereload works fine though as does apache and mysql.
[0]: there are many, many other complaints I have about the OS. I use it right now because of the better driver support and video games.
[1]: I think they added that just recently, as per https://msdn.microsoft.com/en-us/commandline/wsl/interop?f=2...
https://wpdev.uservoice.com/forums/266908-command-prompt-con...
the second is to get their .NET stuff into the cloud.
MS have always been about controlling the stack under their "total cost of ownership" pitch.