I'm seriously considering getting a PC instead, even though I've written http://taoofmac.com for 14 years.
(I do happen to work for Microsoft, by the way, but would very much prefer to keep my home setup on a separate tech stack for the sake of keeping an open view. I'm now ogling the Skullcandy NUC and wondering how well it will run Elementary OS)
I would guess that just here on HN there are tens of thousands of us who could describe ourselves as "Unix-centric pros", who want powerful unixy client machines that match our unixy servers and who also want all the client-side stuff everyone needs (excellent video, audio, wifi, battery mgt., etc., drivers perfectly matched to hardware and working out of the box) plus a full range of apps. We can get the unixy client from Linux, BSD, or Mac. We can get the reliable, everything works consumer client stuff from Windows or Mac. The only overlap is Mac.
Unfortunately for us, this power user unix workstation stuff is just a historical accident for Apple, not a corporate objective. They're trying to get out of the computer business so they can focus on fashionable, high-margin, designer "lifestyle" products and services for the hip ones who consume stuff, not the old drudges in the back room who make stuff.
Microsoft holds their Windows legacy so dear that they'll slap more layers on the papier-mache balloon that is Windows but never put unix at its core, and all the nifty client-side Linux systems out there seem to have the motto "before you complain, realize that how much of it ends up working depends on how smart you are".
I would wish for Google to develop a line of powerful Linux-based workstations, but they would just spy on me until Google canceled the project altogether.
I wish Apple would create a wholly-owned subsidiary called "Apple Computer, Inc." that would have access to Apple's manufacturing expertise but would build a line of computers for power users who produce stuff--computers that weren't "thinner".
Look into it, Microsoft released it earlier this year specifically for unix developers.
But they just did, with Bash on Windows.
I do appreciate that they are trying to do as much as they think they can without throwing away the thing that they believe is the most valuable corporate asset they have: the mountain of stuff built over the years for Windows. They have carefully preserved this asset by making huge efforts to ensure than anything that worked on Windows in the past will keep working forever.
The thing is, what I wish they would do for me (which might not be what they need to do for themselves) is to take the equivalent of my Linux server and wrap a Windows API around it, the way a Mac is like a Linux server inside with a Mac API wrapped around it for client software usefulness. I'd be just as happy with a Windows GUI/API as a Mac GUI/API, but what I want is for it to resemble my servers under the GUI, so I can leverage whatever unixy skills and tools I may have.
Having a simulation of a unix shell on top of an NT core makes Windows more useful than it would otherwise be, but it's not the same as a Windows shell on a Linux kernel.
No, Darwin is Mach with BSD welded to it; it is not a pure Unix design. Likewise, WSL is the NT kernel with the Linux syscall interface on top, via the Pico Process interface. The NT kernel was designed for portability; in fact, POSIX compatibility was a design goal from the early days, in contrast to Mach where the idea of mashing together Mach and BSD was never considered.
In many ways, WSL is a much cleaner design than Darwin is.
Many that went Apple when they showed OS X to the world, never really understood Apple, or for that matter, NeXT culture.
The POSIX layer never mattered, what mattered were the Objective-C frameworks on top and a workflow based on Xerox PARC ideas, that Steve Jobs brought to Apple and NeXT.
The UNIX compatibility was there, because NeXT was competing against Sun and Irix workstations, so it needed to be compatible to a certain extent.
Later Apple trying to promote the same compatibility because after the Copland failure, they needed to sell computers or close shop, so the UNIX with nice GUI was a way of doing it.
For those of us that develop native applications, it never really mattered.
As long as you have no plans to play games, it's a wonderful machine for development. It's really fast for its small size, noticeably faster than the Macs I'd been using before. I spend most of my time with the NUC doing Ruby development in Fedora, with some Clojure and Node.js on the side. I've done some office type stuff with LibreOffice. I've dabbled in OpenSCAD while working on a 3D print. The NUC is more than enough power for all of that. I haven't played with Windows 10 too much, but it's also snappy when I need to boot into it.
It's a very quiet machine. On full blast, you might get a blowing sound similar to a stressed MBP. But usually in normal usage it's no more than a low hum; I can't even hear it unless I listen for it. You can throttle down the processors in the BIOS to make it nearly (totally?) silent if you like.
The most annoying thing about the NUC was installing the BIOS updates before getting started. The NUC6i5SYH had a lot of problems at launch that needed to be patched. Once I got beyond that, everything was smooth. The NUC is basically a laptop board shoved into a small box instead. If the things you want to do are possible on a laptop, they'll be possible on the NUC no problem.
I mostly access the NUC via SSH (and rsync my codebase between the two computers). The NUC is also connected to a monitor and I use the MacBook keyboard and mouse to drive both computers with Symless Synergy.