> But that's exactly what amp is. An opt-in set of standards for creating fast-loading, cach-able pages Not exactly. For one, you could introduce opt in for Go

> But that's exactly what amp is. An opt-in set of standards for creating fast-loading, cach-able pages Not exactly. For one, you could introduce opt in for Google to cache your page through a meta tag. No need for entirely new markup and tools. I have no problem with amp as a concept but the implementation leaves me sour. Amp specification has been growing in complexity that I don't notice speed differences on many sites anymore. They also inject their own js which I don't find amusing. Many sites are abusing amp to rank on Google. Reddit, pinterest, etc. It's a terrible experience as a user. They also didn't fix url and domain problem until recently. It's a usability problem. I can't search for the specific tab by the domain name of the site on my browser. They default opt-in to downloading content in the background for amp feed on chrome android. There are many little annoyances like this one that make me dislike amp. Plus, amp isn't heuristic based. If my network speed is fast enough, I don't need the stripped out page. See: https://news.ycombinator.com/item?id=24327292 https://news.ycombinator.com/item?id=24327292