These, in my view, don’t go far enough in stating the problem and I feel this needs to be said very clearly: Google’s AMP is bad – bad in a potentially web-destroying way. Google AMP is bad news for how the web is built, it’s bad news for publishers of credible online content, and it’s bad news for consumers of that content. Google AMP is only good for one party: Google. Google, and possibly, purveyors of fake news.I haven’t encountered enough AMP pages in my browsing time to really form an informed opinion on it, but as a matter of principle, I’m against it. At the same time, however, all of us know that modern websites are really, really terrible. It’s why so many of us use ad blockers (on top of privacy concerns, of course) – to make the modern web browsing experience bearable. In that sense, AMP serves a similar role.Simply put: if everyone created news websites and blogs as fast and light as, say, OSNews, we wouldn’t need AMP or ad blockers for speed purposes (you might still want an ad blocker for privacy reasons, of course).On a related note, something funny happened regarding this specific article. Yesterday, John Gruber wrote:But other than loading fast, AMP sucks. It implements its own scrolling behavior on iOS, which feels unnatural, and even worse, it breaks the decade-old system-wide iOS behavior of being able to tap the status bar to scroll to the top of any scrollable view.
“Kill Google AMP before it kills the web”