[bad_user]

All the features that Google ships are necessary for web apps. E.g., open this webpage in different browsers: https://howfuguismybrowser.dev/ — Note that Firefox was once on top of this development, during the days when they also had an interest in developing FirefoxOS. Those days are long gone.

As for what Google has done historically with Chrome, it's trivially easy to point to developments that have improved the web.

You can start with the fact that it's the most secure browser, see for instance: https://madaidans-insecurities.github.io/firefox-chromium.ht...

You can also read their original marketing material, in which they describe the isolation of plugins, extensions, or tabs, i.e., a crashing Flash movie or a crashing website no longer crashed the browser — then count the years it took for their competition to catch up: https://www.google.com/googlebooks/chrome/

On “speed”, not sure what you mean, but Chrome has been demonstrably the fastest browser. It always was, with V8 being the fastest JS engine since launch, but also in benchmarks testing more “real” experiences, like Speedometer 3. The only area where it needs improvement is battery efficiency on macOS machines, where Safari has the lead, but even there it made great strides.

Speaking of PWAs, Chrome was also the first to deliver a good PWA experience on mobile devices and on the desktop. For mobile devices, the first one was Apple's Safari, but then Apple crippled the experience by not implementing much needed functionality, such as notifications. Firefox, BTW, still has unfixed bugs on Android and provides no SSB support for the desktop.

[troupo]

> E.g., open this webpage in different browsers: https://howfuguismybrowser.dev/

... and see a bunch of Chrome-only non-standards

> On “speed”, not sure what you mean, but Chrome has been demonstrably the fastest browser.

Re-read what I wrote. I was talking about the speed of releasing new features and APIs. They ship ~1000 new APIs a year

> Speaking of PWAs, Chrome was also the first to deliver a good PWA experience on mobile devices and on the desktop.

There's no such thing as PWA. It's a marketing term used extremely loosely to prove anything, and nothing. It's a random collection of 20 or so standards, and everyone choses their own favorite subset to say ah yes, this is crucial for PWA support".

---

On the other hand we have documented cases of Google sabotaging competitors (https://archive.is/tgIH9), forcing their tech decisions on competitors under the threat of retaliation (https://www.flatpanelshd.com/news.php?subaction=showfull&id=...), selling user data to advertisers (from FLOC to current plans to sell first-party cookie data: https://bsky.app/profile/thezedwards.bsky.social/post/3las7o...) and so on

[bad_user]

> ... and see a bunch of Chrome-only non-standards

That's one way of putting it. The other perspective is that those are necessary features and that Safari and Firefox are now holding the web back. When IExplorer 6 was the most popular browser, with Firefox being the underdog, I don't remember people complaining that Firefox was implementing non-standard features.

Let's also remember that by standards, we mean W3C standards, that organization that was once deemed so slow and irrelevant that Mozilla, Apple, and Opera decided to just initiate WHATWG (back when Opera still existed and Apple still wanted a better web).

The irony of the backlash against Chrome's Privacy Sandbox is that Firefox has started shipping similar features, too: https://blog.mozilla.org/netpolicy/2024/08/22/ppa-update/

And it's understandable why because the alternative is a web centralized in closed gardens (Facebook), locked behind paywalls, or a dead web.

---

I mean no disrespect, but the people advocating for a slower web progress sound just like the people advocating for degrowth, all being a bunch of nonsense that only a tiny elite minority actually wants.