> Barriers to entry for self hosted sites. Easier to host with Google now.

Let's Encrypt (which Google helped fund) is the opposite of a barrier to entry. Free domain-validated fully automated HTTPS cert distribution wasn't a thing, and now it is. It makes it way easier to self host in a post-PRISM world.

Also, Google does a tiny fraction of overall web hosting.

> HTTP/whatever was done only for Google's benefit.

Your claim is that everything Google has done has been worse for the web, so you don't get to pick individual tech that's clearly good (ex: V8) and ignore it. And whether things were done for Google's benefit is also irrelevant: the claim is about outcomes.

On the specific question of HTTP/2 and HTTP/3, these have made large improvements in end-to-end loading times across the web, including when Google is at neither end of the connection, and especially for high latency connections like mobile.

> If they're so standard why do people develop for Chrome and ignore other browsers?

All of the things I listed are widely supported and fully standardized.

There are other parts of the web platform that aren't, and that does push people to Chrome, but that's not what we're talking about.

Again, if you'd like to claim Google's impact has been bad on net that's much more arguable, but your claim is way stronger than that.

> Free domain-validated fully automated HTTPS cert distribution wasn't a thing, and now it is.

Free compulsory ...