You talk like developing on Linux means doing everything in the command line. *nix UX is nothing to be ashamed of, and I personally prefer it over Windows and OS X (especially OS X).
From an IT and "just works" perspective, Linux was a no-go for us.
It wasn't particularly about the UX on Linux desktops, but rather they don't fit in our company culture when it comes to how assets and IT are managed.
Which is why I wrote it from my own perspective as an anecdote.
Personally, the reason I like OS X over a random linux distribution is the sane keyboard shortcut defaults - CMD+C and CMD+V just work everywhere, as well as things like CMD+W.
Well, almost everywhere. And CTRL+F is still a little wonky depending on the app you're in.
Where on Linux do Ctrl-c, v, and x not work? I haven't had a problem with them anywhere in a decade. I have largely stuck to Gnome2, MATE, and XFCE, though.
The problem with Ctrl C is that it is also the shortcut for SIGINT when the terminal is focused.
Also most terminal emulators will forward all Ctrl combinations directly over the TTY rather than capturing them in the windowing system, so in practice Ctrl-V rarely works in a terminal either. Likewise for Ctrl-W, which is typically bound to backwards-kill-word, etc.
The way it ends up in practice, shortcuts involving the Command key on OSX end up being clearly defined and consistent, because apps typically can't override them.
It wasn't particularly about the UX on Linux desktops, but rather they don't fit in our company culture when it comes to how assets and IT are managed.
Which is why I wrote it from my own perspective as an anecdote.
As usual, YMMV