zlacker

>>dochtm+(OP)
We don't have to speculate, we've been through this already during the IE4 to IE6 era.

Microsoft just did whatever they wanted with the web "platform", and so will Google.

In Microsoft's case what they wanted was nothing. They weren't a web business, saw it as a threat to their platform leverage, and so just left it abandoned and stagnant for years.

Google is simultaneously better and worse: they won't leave it stagnant because the web is their platform, but on the other hand they have a lot more to gain by abusing control of it.

>>paol+B6
Personally, I think Google already does whatever it wants similar to what Microsoft did. They do offer standards for discussion but it will implemented and expect other vendors to follow suit.

>>wdb+y9
> They do offer standards for discussion but it will implemented and expect other vendors to follow suit.

Safari definitely does not just follow suit (see https://caniuse.com/?compare=chrome+102,safari+15.5&compareC... for example).

>>remus+Dm
Can you explain you explain what I'm looking at in your link? I only sort of understand, but I'm not confident I'm understanding it correctly. (sorry, this is probably a stupid question)

>>nimajn+9y
It is a website that compares which features are available in which browsers. On the linked page it's comparing the availability of web APIs in the latest versions of chrome and safari to demonstrate that safari has not implemented many of the web APIs chrome has implemented.

These APIs are one of the big areas where chrome/google have tried to expand the remit of what's possible with web apps, for example the file system api can be used by a web app to access files directly on a users machine.