Personally I use OSX (still Mavericks, for now) for development, but almost all of the code that I write gets executed in Linux VMs (often through Vagrant). For me, this eliminates most of the headaches that come from developing using open source technologies in a non-free environment. I'm sure it creates some headaches of its own, but I find it works well for me.
Don't get me wrong, I like Arch a lot, and I've been using it as my main Linux distribution for the past five years at least. But if don't do a full "pacman -Su" at least once a week, it's absolutely going to shit the bed at some point.
Now I'm curious, so I guess I'm trying it for a month [1].
[0] https://arguggi.co.uk/blog/list.html [1] https://arguggi.co.uk/blog/Not-Updating/
I usually don't want new features. I'd often rather have what's already there fully working. The lack of finished software available (e.g. TeX) is astounding.
Most of the time, I come back, do an "Syu", and it's fine. Occasionally though, things go pear-shaped. Once or twice I've needed to manually fetch packages from one of the archive sites and manually copy it into pacman's cache directory to get things up and going again.
The only Linux distro I can stand is Arch Linux. It will require you to become a sysadmin (comfortable with a shell, editing a few config files here and there, and following instructions from the wiki), but you sound comfortable with that. Arch will never break beyond recovery for you. It's a very simple distro that doesn't try to "do everything" on your behalf. Other distros like Ubuntu, Mint, and Fedora all seem to have a significant chance of self-destructing when I update them. Arch just keeps working. I've been using it exclusively for over 7 years.