And “unbelievably bad” is how I feel when trying to get various projects built from source on any platform all too often. If I’m lucky the maintainer has made a point of getting up and running a matter of running a couple commands but all too often there’s a mountain of assumptions about the user’s environment that cause the build to fail, sending me down rabbitholes. At least with SwiftPM Xcode projects, building is usually as simple as opening the project and hitting ⌘R and doesn’t involve a side trek to Mordor.
The IDE itself is pretty good and personally I prefer it over Android Studio.
If it's my reaction to the use of Xcode then I've associated a stress response and get anxious which is partially why I left my job. The tool was also, in my experience, not a smooth or enjoyable developer experience.
Just the BIOS settings nightmare I had to get through for it install Windows properly was beyond belief. I guess OEM installs have won. But building your own hardware like "back in the days", oh the sweet sweet old days, what a nightmare.
My BIOS even has AI in it (WTF).
Even Microsoft holds its own debloating list [1]! How bad is that?
I tried to clean windows right after install and that took much longer than setting a brand new mac. And the macOS doesn't cost $150, for ad-riddled cortana/AI nightmare feeding my clicks to random houses and shipping with minecraft and king.com games!
At some point, "both camps" have to agree to disagree but there are lot of rose tinted glasses everywhere.
[1] https://github.com/microsoft/windows-dev-box-setup-scripts/b...
Because you can't debloat a Mac since bloat is part of a protected system partition, so time saved?
Second, Windows doesn't have it in the same crypto-protected-risk-breaking-boot way, there are well documented ways on debloating Windows both before and after an install.