That's exactly it for me as well. Several times I got prompted by articles like this to evaluate AMP, because I like the core idea – a defined subset of HTML ta

That's exactly it for me as well. Several times I got prompted by articles like this to evaluate AMP, because I like the core idea – a defined subset of HTML tags for static content that can then be cached. And then I have to realize that this is not the core idea at all. Replacement of HTMl-Tags with AMP-tags, converting a static site to a site only working with javascript, javascript that can't be self-hosted – that is just an ugly and bad solution far from the claimed core idea. How AMP should be: Define a subset of allowed HTML and best practices fit for static pages. Verify and cache the result. If doing crazy js-hacks, do that on the cache-layer as an add-on, like the image resizing.