If it's the last of the three, then that's just a decision on Apple's part to not waste resources trying to support every possible combination of OS X version and iOS version. Yes, that leaves people like you unhappy, but leaves the majority of users happy, with better software.
Yes, the upgrade was free (monetarily). It was not free timewise, and it took a few weeks to sort out as it completely broke my workflow (it broke the running version of Synergy http://synergy-project.org/ and to upgrade that would have required an upgrade of my Linux system (yes, it's an older system---again, it ain't broke so I'm not fixing it and lose even more time and effort).
I was able to fix the Synergy issue (http://boston.conman.org/2015/10/15.2) but the point remains---Apple forcing updates. I know most here just live with the constant upgrade treadmill ("OH MY GOD! YOU HAVEN'T UPDATED IN 20 MINUTES? HERETIC!") but having been burned oh so many times in the past thirty years I've grown to dread it. It gets tiresome relearning how to use something I've already learned how to use yet again. For the tenth time. Because we in the industry have deemed that if a program hasn't been changed in the past twenty minutes, it therefore must be unmaintained and a piece of garbage (with the sole exception of zlib I think).
Me, bitter?
It seems like this "if it ain't broke not fix it" strategy doesn't work out that great for you.
It only postpones problems for the future, when inevitably something will be broke (software rots too, not just food, especially in 2016, where it depends on tons of staff that can change/be deprecated/obsolete/hard to replace/taken down etc over time, from the hardware to the network to web services).
"If it ain't broken don't fix it" is only short term advice. It doesn't eliminate the need to keep software systems reasonably up to date (and a 5 years old OS is like a 20 year old car in IT years).
In any case, one thing that jumped out at me reading your blog post is how interdependent software has become — everything depends on everything else, the apps on the OS, the OS on one device with the OS on another (iPhone sync), and so on. Many decisions may have been individually right, but it sets off a domino effect of upgrades and disruptions to your workflow.
I agree with you that if you bothered to read the iOS release notes, it should have warned you that it will require an OS X upgrade. But again the larger lesson is not to get your software into such a fragile state where one update causes a domino effect.
My solution is to always say yes when I'm prompted for an upgrade. That way, a single upgrade causes little trouble. When I use a product or service, I'm buying into the developer's vision, not making a decision as to whether to use version 3.5.638 of an app. And if that developer's vision no longer works for me, I switch to another developer, rather than micromanaging every version of every app.
And if an app doesn't work with an updated OS, that's the app developer's fault as far as I'm concerned. Or if one app doesn't work with an upgraded version of another app, then the first app developer is at fault. I'll stop using the defective app if I have to.
Now? Maximizing the screen causes the window to cover the entire screen, hiding the menu bar, and giving that window its own desktop (or space, or screen or whatever it's called these days) and preventing Mission Control from showing that window (or other windows, depending on which desktop/place/screen you're on). That breaks a workflow I've developed over the past few years, just because some engineers at Apple thought this behavior is what we needed.
THAT'S what I'm ranting against. Arbitrary (to me) changes that break things (work flows, other programs, whatever).
As far as cars go, about the only controls that tend to move about the cabin are the gear shift (either right side of steering column, or just right of the driver), head light controls and wind shield wipers, but there's generally only a few places they'll migrate to. You will never find the break and gas pedals swapped though.
As for the analogy with the car, that actually is a downside of my car — it doesn't improve over time the way OS X does. And I'm happy OS X is improving, as opposed to giving in to change-averse users.
So clearly an outlier who shouldn't suppose mass market OSs (and their update/release philosophy) targeted at regular users would work well for them?