Of every platform I've used, macOS makes this the toughest. I appreciate that I have to put in work to add features, fix bugs, and support new OS functionality

Of every platform I've used, macOS makes this the toughest. I appreciate that I have to put in work to add features, fix bugs, and support new OS functionality. But Macintosh is the only one I use where a new OS release means a method call that worked fine with a default param value for the past 8 years causes an instant crash with the latest major OS (with no indication of any change in the documentation or release notes). I'm not even at the point where I can support the latest macOS functionality, because I'm still working around the previous round of deprecations. There are big sections I simply have to rewrite because the old way is going away, and the new way has a completely different structure. It's also the only system where I basically need to upgrade my (OS, IDE, compiler, language) tuple all at once -- which means this is all tied to the hardware, too. Never before have I had to do a firmware upgrade in order to use the latest syntax in a programming language. My graphics card won't be powerful enough to run the next version of the compiler, even though the software generally gets more efficient with every release. Zany. It really does seem strange when a new CPU architecture is the least significant change I've ever had to deal with as a developer.