I think the statement really is "development in a unix/linux style on windows is really painful". If you like doing development with text editors and shells and have any tools that are command-line only then yes - it sucks on windows.
Windows development in an IDE is usually just fine, not to mention that it's often exactly the same as running the same IDE on linux.
- it was Unix (I'm a vi/command line guy) and you could run all the backend software (Apache, Oracle, WebLogic/JBoss and other Java stuff such as Ecplise)
- yet you also could use commercial desktop apps (Adobe, MS Office, other graphics apps, the occasional game)
- great out of the box experience with optimal hardware support and no time consuming tinkering required; practical innovations like Expose, Spotlight, later also TimeMachine
Basically "Linux with QA and taste". And because using MacOS put a smile on your face.
Now Mac OS and Apple's latest computers only serve to demonstrate a lack of vision for the platform. Apple seems focused to integrate/unify iOS and MacOS, which might make sense in a beancounter way of thinking (eg. seeing MacOS as a cost center), but sends out the message that Apple is willing to loose "Pro" users as collateral damage.
I certainly hate to loose the ability to buy Apple equipment for my work, but without Apple taking really bold measures, Apple is a lost cause in the Pro market as it stands.
Price itself isn't so much an issue as is the feeling that you're being ripped off for rigs that lack any "pro" features, yet are as expensive or even more expensive than the "pro" stuff Apple used to make.
I like the polished look of macOS, and its Unix roots which make it fairly easy to follow instructions for Linux on macOS.
Because EVERYONE used Windows. That changed mid-00s (Ubuntu and x86 Macs).
Personally Firefox stoked a lot of interest in FOSS for me, and the mature version (2.0 was a big deal) came out around then too.
None of these things were problems with OSX.
Are things different in the Windows world?