I'm probably going to buck how HN feels about it but I'm somewhat disappointed in this news. I get there's often valid use cases for this such as kiosks that ne

I'm probably going to buck how HN feels about it but I'm somewhat disappointed in this news. I get there's often valid use cases for this such as kiosks that need current version stability without sacrificing security. New APIs are something all iOS devs look forward to. Most companies have a current version -1 or a -2 policy. Those on a -2 policy are finally able to start using SwiftUI and Combine throughout their projects come this fall. However, if there's enough people out there who resist upgrading, it'll leave a sizable cohort on ever-older OS versions. This will make management decisions on dropping older iOS versions (which also means availability of newer APIs) harder. I don't believe a there will be many personal devices that will have this setting enabled. It'll likely happen in these sectors: 1. Kiosks and public-facing usage. 2. Corporate/Enterprise world with company-owned devices. 3. Cultures that resist upgrading (I'm looking at you, Japan).