Scott Gilbertson, writing for The Register:
Quite a few high-profile web developers have this year weighted in
with criticism and some, following a Google conference dedicated
to AMP, have cautioned users about diving in with both feet.
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.
It’s time for developers to wake up and, as Jason Scott once said
of Facebook, stop: “Shoveling down the shit sherbet” Google is now
serving with AMP.
I’m on the record as being strongly opposed to AMP simply on the grounds of publication independence. I’d stand by that even if the implementation were great. But the implementation is not great — it’s terrible. Yes, AMP pages load fast, but you don’t need AMP for fast-loading web pages. If you are a publisher and your web pages don’t load fast, the sane solution is to fix your fucking website so that pages load fast, not to throw your hands up in the air and implement AMP.
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. AMP also completely breaks Safari’s ability to search for text on a page (via the “Find on Page” action in the sharing sheet). Google has no respect for the platform. If I had my way, Mobile Safari would refuse to render AMP pages. It’s a deliberate effort by Google to break the open web.
★ Saturday, 20 May 2017