> There are just too many open source projects that stupidly hard core path seperators or rely on UNIX binaries.

I wouldn't say stupidly. Open source projects just don't prioritize Windows development.

I recently bought a Thinkpad to try if another platform would work. I first ran Windows 10 and found it unworkable and then installed Ubuntu, did some battery tweaking. It is great; have not touched my Mac since. Especially long battery life, swappable batteries and, for my taste, a better keyboard next to more ports is just better over all for my (full stack) dev.

How did you get great battery life from Ubuntu? I've never been able to get anything close to the runtime I get on OSX. In my experience, OSX gives me the longest batter life, second is Windows and any flavor of Linux is terrible (maybe 3-4 hours on a machine that Windows gives 5-6 hours).

I get 16 hours under my Lenovo with ubuntu with tlp default settings. I have to be careful a bit with browsers (they use most in my workflow) but usually I just use lynx for programming searches. OS X on my MBP is ghastly: Apple replaced the battery and I use the same software as under Ubuntu but I struggle to get 3 hrs. On my Air it was wonderful. Windows I have not used for anything serious in 20 years.

True you need a VM but performance doesn't have to be crippled. My out of office/at home machine is a Dell Inspiron 5558 (Core i7, 16GB RAM). I stuck an intel 256GB SSD in it, took the free upgrade to Windows 10 and do all my dev work in a few Virtualbox VMs (leaning heavily on mRemoteNG for lots of tabbed PuTTy instances!).

Total cost (including the Intel SSD) was £726 or $1049 at today's rate (exc. VAT). So didn't cost a bomb and gives me a lightening fast machine, windows for desktop duties, debian for dev, a 1920x1080 display, easily replaceable battery/ram/disk and no issue driving multiple monitors.

I also think Windows + Putty is better than Desktop Linux. I'm actually going to sell the Mac (can't get used to shortcuts, don't have money to an upgrade here in Brazil) and buy a Windows PC + Intel NUC for HTPC + Linux box.

> projects that stupidly hard core path seperators

It's also stupid to assume that your application will work seamlessly between Windows and Unix-like systems just by making sure that the path separators are OS-agnostic.

Most of the windows APIs support unix-style path separators, I actually get annoyed when I see separator injection needlessly... the bigger differences are default system paths and environment variables as such. (Also, windows-style "drive" letters" of course).

You have some point there, but a lot seems to work fine. The hardest problem i had was with a x64 binary for SQLLite ( Ruby On Rails), which i couldn't fix. Cygwin would be a recommender for anyone using Windows and programming languages other then .Net.

And once you know how the C++ compilation works with VC++, the problems are minimized. ( i mostly come this accross with Python)

It isn't a hassle free road though

This is why most of my *nix work is done on my server at home (since I work from home). PyCharm pretty handily supports remote Python installations, so I can just use my work-supplied Windows laptop to type the code and have it run on a VM in the other room (or across the country if they insisted I use one in the datacenter).