The entire pbxproj format is horrible, but at least you have stuff like BUCK (https://buckbuild.com/) that can mitigate some of that.
Another thing I would add to that letter are good build boxes. Bring back xserve, so we have CI that is not based on mac pros or mac minis.
Android devs, even though they have build tooling options with java, have other problems that make developing on their platform painful. Their simulators are bad compared to iOS, the fragmentation / lack of updates is pretty annoying and overall it's harder to deliver good equivalent android apps than it is for iOS. iOS as a software platform is actually pretty solid.
What do you use to develop on? Any specific laptop or is it a desktop?
FWIW I'm still not sure what the BUCK workflow is suppose to look like for most teams. It seems like if you use BUCK you're expected to not use Xcode even as an editor, yet there isn't another editor to pick up the slack (assuming you want autocompletion and decent highlighting). I think there's still a lot of work to be done for it to be a viable replacement, even for Objective-C, for Swift it's even further away.
Shit like this is why I do all my development in a VirtualBox with Arch Linux. While my co-workers argue about the best way to install Docker on their Macs, I just `pacman -S docker && systemctl start docker` and get on with my life.
You could probably run vanilla macOS in a VM without running into any problems.
He only ever used Homebrew as far as I know.
> Would Linux be immune to that, if you had 2 concurrent pkg managers?
How would that ever happen?
However, as of fairly recently, IIUC Docker for Mac uses macOS's native hypervisor framework rather than relying on VirtualBox as it used to.
my dev machine is a VM, which gives me a ton of other benefits, like portability, resizability, backups, versioning, and overall stability. I can (and have) given devs my VM to get up and running immediately on a complex project, without having to do a lot of setup.
With each OSX update, usually stuff broke, needed to be reinstalled, or performed differently. With Linux, that is not the case. And with a linux VM, I can ride out host upgrades and keep plugging away with a machine i know works - or attempt an upgrade on a cloned VM and have a trivial way to backtrack if it fails.
I've also found that homebrew packages sometimes don't contain the necessary header files for development, (i.e. imagemagick), so you're forced to switch to MacPorts just for that and it's altogether more painful than on Linux.
It also simply just doesn't feel like a lot of the tools target macOS, there's an outdated bash shipped by default and Apple even broke curl recently[1].
1 - https://daniel.haxx.se/blog/2016/10/11/poll-on-mac-10-12-is-...
But I was under the impression Apple at least took care of the devs who work on their platforms.
As someone else has noted: vote with your keyboard. I do ROR web development in part because I am free of many of the constraints other devs must face on custom platforms.
If you don't like doing dev with Apple, don't do dev with Apple. Either pick better tooling (if available) or ditch the platform (if possible).