For more details, you can read the (very readable) AMP docs: https://www.ampproject.org/docs/guides/how_cached
Here’s the section on guidelines for implementing an AMP cache: https://github.com/ampproject/amphtml/blob/master/spec/amp-c...
Google engineers seem to have a hard time differentiating between a platform and a framework. PWAs and suffer from the exact same problem. They’re great if you build a greenfield product to their exact specs, but difficult to use otherwise.
How is limiting size and server round-trips of CSS not related to the problem being solved by AMP?
I take a look at the average mobile web page and thank Google that AMP brings sone restrictions.
From a technical standpoint it wouldn't surprise me if people start proposing binary formats that beat text/plain + gzip in size and speed.
Webassembly
That's exactly what they are doing with Instant Apps, they just try different strategies to control the web more at the same time.
"We could do that, but then we'd lose the special AMP placement on Google SERPs" is a much more compelling argument, and preferable to starting a proxy war between the CMO and the CTO.
Google has done a hell of a job flexing their Search muscles to encourage the behavior they want, here. All the while somehow open-washing the project so that SEO-types make the ridiculous statements you quoted, implying that AMP isn't a Google owned-and-run project.
On an engineering level, I respect AMP. From an anti-competitive / social engineering perspective, it's absolutely terrifying.