Using market forces to encourage more consolidation into a single engine is *bad*.
Safari is missing many performance and device-related features that would allow you to create a compelling web application and bypass the App store.
I tried once, you run into the most unexpected roadblocks and come to the conclusion "I have to release this as an App." Well... guess why.
That said, about half the list appears to be stuff I don't care about one way or the other. At least not without spending way more time researching those CSS elements than I care to invest.
And I'd be totally fine with an "Allow Alternate Browser Features: Y/N" setting or similar, as long as it defaulted to the current behavior (locked down Safari only).
Yeah, looks like a nice checklist of things to turn off to me…
Safari is often the hold-out on implementing features[1] that would be useful to users - presumably because it would make web apps viable on iOS, and compete with App store apps where Apple takes a 30% cut
> Using market forces to encourage more consolidation into a single engine is bad.
Competition on a level playing-field is not bad, even if you dislike the superior product (as determined by the free hand of the market.)
1. If memory serves: various APIs useful for PWAs were delayed or kneecapped on Safari
It doesn't support Ublock Origin.
