For an individual user, what is the point of browser choice when developers stop testing in Safari and instead say "if it doesn't work, install Chrome". That's not giving the consumer a choice.
Though an interesting consequence is that allowing iOS users to install firefox but not chrome would be a strict improvement over the current situation.
If diversity fails to occur naturally, some amount of forced diversity helps to keep the ecosystem healthy.
There's no reason for Safari to have a sub-par experience except for the laziness of some web developers.
How about a browser with a captive userbase that has less incentive to stay up to date with web standards?
Your argument is that we should expect developers to target/test their app on many different browsers where any random CSS property behaves differently. They will have to buy a device just for this purpose. Because it is obviously developers who should have to pick up the slack here, not Apple.
Safari is a better browser because it doesn’t support them.
> Safari is a better browser because it doesn’t support them.
It has supported them since iOS 16.4. The issue is they made enabling them so high friction for users that you're better off publishing a WebView wrapper to the App Store instead. More work for app devs, worse experience for users, but great for Apple because it's still on the App Store.