AMP needs to be killed with fire

[fnordius]

I never noticed Google’s AMP until BoingBoing implemented it, and it is not good. It has crappy layout, weird behaviour on my iPad and on my Nexus phone, and doesn’t even take effect consistently. It makes me less likely to click on a link.

It’s less happy mutation, and more unhappy cancer. And I am not alone in my opinion. I see John Gruber over at Daring Fireball feels as I do, so I will let him say what I feel and recommend reading the article he linked to: https://daringfireball.net/linked/2017/05/20/gilbertson-amp

[ficuswhisperer]

See also:

What's this "amp" crap?

[image] When I click on BB links from my RSS feed on my phone, some of the time the URL has /amp appended, and I see this broken, reduced content page. Anyone know what this is?

It’s a fucking scourge and it’s the only reason I suffer with Bing as my primary search engine on my phone. AMP search results suck. They don’t look right, they don’t work right, and they aren’t shareable without extra effort. This isn’t 1998 where we need special WAP wrappers for sites.

Fuck AMP.

[ActuallyARegular]

Agree. The Facebook version also needs to die.

And for good measure, fuck daringfireball!

[Daaksyde]

If only there were some modern way to transmit content that that was nearly as fast as an old dial-up modem.

I liked this article: http://idlewords.com/talks/website_obesity.htm which is quite amusing and well-written:

Jeremy Keith pointed out to me that the page describing AMP is technically infinite in size. If you open it in Chrome, it will keep downloading the same 3.4 megabyte carousel video forever.

If you open it in Safari, where the carousel is broken, the page still manages to fill 4 megabytes.

These comically huge homepages for projects designed to make the web faster are the equivalent of watching a fitness video where the presenter is just standing there, eating pizza and cookies.

[system]

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.