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.
C# has had Linq and lambdas since 2007 so there's a decent chance the code would be decently pleasant to work with, too.
Some devs might find 2008 Web Forms apps a bit crufty in 2018 but if you squint and pretend your .aspx is inside a render method issued of a separate file, the mental model isn't all that different from a SPA.
Things that have happened in the last 11 years include the death of PowerPC support, the introduction of GateKeeper, the introduction and apparent temporary neglect of the Mac Apple Store, the switch to make codesigning effectively required, and the end of life of Apple’s own Java distribution (which was bundled with macOS until a few years ago).
Dealing with these takes time but doesn’t really make my product better. I typically need to have an update ready by the time Apple releases a major OS update, or I’ll have frustrated customers.
This is something I didn’t realise I was committing to when I created version 1 back in 2008.