[IggleSniggle]

They don’t all implement the same set of standards equally. The one that comes immediately to mind is one that comes up frequently as “hey do you know your website is broken on iOS” on HN is when someone is demoing some really interesting web-tech that requires SharedArrayBuffer (since it enables thread-like behavior in JavaScript and is super useful also for performant interaction with the GPU).

Browsers can of course be non-conformant on other interesting issues. Imagine if a browser came out that allowed the Unity Web Player to work. Instantly, people wouldn’t need to use the App Store to purchase games. Instead, they could just use the browser.

[enos_feedler]

For the first point, that sounds like a standards problem and an ecosystem challenge. The association/consortium or whatever it is needs to protect and fight for this.

For the 2nd, it sounds like there needs to be a way for the web platform to evolve for things that require engine modification. I wonder if the web will break down into smaller standard components and new browsers can be built from those.

[millstone]

It's not useful to cast this in terms of standards. If your users use a non-standards compliant browser, you fix your website, not the browser.

With regard to your second paragraph, I believe you have made a category error between "the App Store" and "the browser." The browser is not a store.

[IggleSniggle]

The browser contains stores, and the browser can contain fully working applications. The point wasn’t that the browser is a store, but rather that allowing certain features to work on the web would destroy the walled garden of the App Store by enabling certain kinds of stores that circumvent the App Store.

[dwaite]

A bit of an aside, but SharedArrayBuffer is likely not the best example It was disabled by default in Chrome and Firefox until recently due to Spectre. Chrome is still working on improving their security around this feature, and does not yet enable the feature for Chrome on Android.