edit: I'm going to get downvoted to oblivion for this comment and I could not care less, I'm tired of Apple fanboys on hn
edit: I'm going to get downvoted to oblivion for this comment and I could not care less, I'm tired of Apple fanboys on hn
A separate anecdote: My company requires the same thing for on-prem installs - you can't downgrade. Data/schema migrations for our single application become a pain in the butt if we allow downgrades. For an OS and lots of applications, I can see it being a UX/support nightmare. We disallow downgrades for this reason because we don't wish to tackle the technical challenge of enabling it, but primarily we disallow downgrades because of the security liability.
Ah but then when there is a bug that is exploited (e.g.SMS resetting phone) or a flaw that needs to be fixed (e.g. unexpected shutdown) then everyone is angry and pissed off because they haven't fixed it. It's damaging to their brand, and damaging for users who don't know/understand/care.
It's kind of a damned if they do, damned if they don't situation.
That said, they could just roll out security patches independently of new features - I believe Google is planning to do this in future Android releases via Project Treble - 1? Apps would rot though, as they update to use newer API features not available in the base OS.
Edit: I think project treble is just about easier OS updates and not modular security updates for older platforms
1 - https://android-developers.googleblog.com/2017/05/here-comes...
Possibly adopting a less strident tone will find a more favorable audience for what are admittedly good points.
The one app that I use that only targets iOS 12 with it's latest version is OverCast. Why bother targeting older OS's when every device that can run iOS 11 can also run iOS 12?
By disallowing downgrades you can't get back to a version with older exploitable bugs.
Unless you believe they use s separate DRM scheme to download apps on iOS 5 than iOS 12.