Like it or not, at least Google blazes ahead and brings new features to the browser sphere. It's not like innovation can be expected from Firefox any more, not with them cutting costs on the development team.
If someone says it's bad because corporate interests shouldn't push innovation... well, I'd like to understand why they're okay with the explicitly bought and paid for OpenJS board seats, or the permanent corporate tetrarchy for HTML. A lot of developers seem to have unrealistic expectations about how software governance works.
At least for AMP, I indeed am glad because it finally forced the big media houses to provide pages that didn't suck ten freakin' megabytes off my 50€/2GB data plan (yeah, that were German mobile data prices until not too long ago!) for a single page load with under 10KB of actual content.
I'm not particularly liking the situation, but the fact is that the only entity able to actually force change is Google.
ETA: Sorry, I forgot Apple who managed to get the Web rid of the proprietary, expensive (for authors) and insecure scourge that was Adobe Flash, but that was about the only progress that came from Apple. I'm not counting PWAs because Apple utterly failed to make web apps actually competitive with App Store apps for profit reasons!
The end effect is a broken, incompatible web.
Yes, some of that, e.g. srcset, animations and media queries, was possible using Javascript... but god, it was awful to use, even more awful to debug (especially "stuttering" issues or unresponsive pages due to some animation locking the render thread) and, worst of all, a couple tabs with JS animations open and you could watch your battery go empty faster than the gas needle of a BMW X7 on a German Autobahn!
The only thing that is still, for now over than thirty years, needing massive effort is HTTPS client certificates.
ETA: And... best of all, Chrome and FF forced people to regularly update, meaning the days of supporting a browser that hadn't seen an update in a decade (IE6) are gone. Mobile devices aside, you only need to take about half a year worth of browser versions to test, and cross-browser compatibility issues have all but vanished for standard stuff (with the notable exception of Apple).
The majority of these things are not from Google/Chrome and not from this past decade.
<img srcset> was first introduced by Safari and proposed by Apple to the WhatWG in 2012; I believe for their iPhone 4 with the 2× Retina display. But Webkit was already thinking in 2006 about High DPI.
https://lists.w3.org/Archives/Public/public-whatwg-archive/2...
https://webkit.org/blog/55/high-dpi-web-sites/
The <video> element was first proposed by Opera to the WhatWG and standardised there. I believe the first big adopter was Safari on iPhone, because of no Flash, of course.
https://lists.whatwg.org/pipermail/whatwg-whatwg.org/2007-Fe...
Media Queries were first proposed and specced by Håkon Wium Lie of Opera in 2001. (Good) Browsers for the first years implemented just a subset of that feature (the media types). In 2007 Apple released the first iPhone and adopted the media queries syntax, especially the viewport width and height which made the former mostly unknown specification more popular.
https://www.w3.org/TR/2001/WD-css3-mediaqueries-20010404/Ove... https://developer.apple.com/library/archive/documentation/Ap...
CSS animations (and transitions and transforms) were proposed by Apple in late 2007 after implementation in Safari:
https://lists.w3.org/Archives/Public/www-style/2007Nov/0090....
https://lists.w3.org/Archives/Public/www-style/2007Nov/0080....
I thought I remember that Apple first used these technologies for Mac OS X‘ web-based Dashboard widgets but in retrospect that must have been <canvas>.
WebRTC and WebASM seem to be more Chrome things, yes, and from the past decade.
(I don't have a big point; just some annoying memories of following web standards in that decade more closely than now.)
Sounds like you're in the business of making that crappy web bloat the rest of us despise. Which makes your whining about "download ten megabyte for ten kilobytes of content" doubly ironic.
From what I remember, web developers (including me) were so utterly pissed about IE6 being in a state of a years-long feature freeze that Firefox and later Chrome actually had their chance to rise.