> Keeping up with API changes from a decade ago doesn't qualify as unnecessary. The API didn't change, it worked until Apple decided to break it in a subsequen

> Keeping up with API changes from a decade ago doesn't qualify as unnecessary. The API didn't change, it worked until Apple decided to break it in a subsequent version of macOS. > Here's the point. Apple isn't doing that. Apple don't visit customers with old macs to push breaking patches. They broke the API in new macOS. > What happened is the developers made something that worked on old macs, didn't put in the effort to keep it up to date and are now complaining that Apple won't put in the efforts to support the old APIs on new systems anymore. Yes, that is exactly the issue: Apple shouldn't have broken the API in the new macOS. The developers are perfectly in their right to complain about Apple breaking their applications and forcing them to waste time rewriting code that already worked to do the exact same thing only now in a different way because Apple doesn't care about the developers' time. And yes, it is all on Apple - the breakage wasn't forced on Apple, it was something Apple decided to do.