Part of the 'pride' behind being a Linux hacker came from heavily customizing, breaking, fixing, and generally maintaining your dev kit. I have a friend who's taken on a motorcycle rebuild project and I can see a lot of analogs there.
For me, personally, I realized that having a system which I can take from zero to 'dev ready' in less than an afternoon (which I did recently with a freshly shipped MacBook) is the main 'feature' I want from my dev software stack. I don't love all of OS X's defaults, but I customize very few things.
The bigger issue for me, though, is hardware. I know this varies dramatically from developer to developer, but weight, size, battery life, and display quality (in roughly that order) are my primary concerns with laptop hardware. I recently switched my work laptop from a Chromebook Pixel (first gen) to an 11" MacBook Air and I've been thrilled with the change. That said, the leap in display quality and general machine 'feel' from the Air to the MacBook I use for personal developer is almost as big, for me, as the leap from the Pixel to the Air. Apple builds hardware that feels 'right' to me in a way that other manufacturers that I've encountered don't.
So, I can't speak for others, but there's why I'm a proud OS X user instead of a proud Linux user.
The hardware is very nice. I'm typing this into a Macbook running Arch Linux. However, I don't know if it's fair to say you can't get up and running in an afternoon these days, even if you have a heavily customized system like I do (https://sr.ht/-77r.png). I expect that the sort of people who invest heavily in making their Linux setup their own are people who have the hardest time with OS X - everything just felt wrong for me, and it was very difficult to use because of this.
Personal preferences will naturally remain personal. There were a bunch of things that felt unfamiliar to me on OS X, but few that felt 'wrong'. Then again, I made the switch back in 2005 or so to a PowerBook G4. Linux was a very different beast then, and just having it run on a laptop was a bit of an effort. Expecting decent battery life (or all of your hardware to be functional) was more or less out of the question.
Another factor is that there a bunch of things people want/expect from a window manager that I never took advantage of, the biggest two being virtual desktops and focus-follows-mouse. I imagine if I had a strong dependency on either of those, the switch to a Mac would've been considerably more painful. On the other hand, features like Expose felt very natural to me (and at the time Linux equivalents were... poor).
These days my life consists almost entirely of running full-screen apps and trackpad swiping between them, which would probably drive most X11 users batty :)
For me, personally, I realized that having a system which I can take from zero to 'dev ready' in less than an afternoon (which I did recently with a freshly shipped MacBook) is the main 'feature' I want from my dev software stack. I don't love all of OS X's defaults, but I customize very few things.
The bigger issue for me, though, is hardware. I know this varies dramatically from developer to developer, but weight, size, battery life, and display quality (in roughly that order) are my primary concerns with laptop hardware. I recently switched my work laptop from a Chromebook Pixel (first gen) to an 11" MacBook Air and I've been thrilled with the change. That said, the leap in display quality and general machine 'feel' from the Air to the MacBook I use for personal developer is almost as big, for me, as the leap from the Pixel to the Air. Apple builds hardware that feels 'right' to me in a way that other manufacturers that I've encountered don't.
So, I can't speak for others, but there's why I'm a proud OS X user instead of a proud Linux user.