Do you hate AMP as much as I do?

View other answers to this thread
Start a personal dev blog on your domain for free and grow your readership.

3.4K+ developers have started their personal blogs on Hashnode in the last one month.

Write in Markdown · Publish articles on custom domain · Gain readership on day zero · Automatic GitHub backup and more

Trent Haynes's photo

AMP is trying to solve a problem that "we" created - too much dependence on JS at the outset. We really need to invert that dependency. Your page should work even if the browser/device doesn't support JS - i.e. Progressive Enhancement. The subject has been discussed and recognized as a problem for many years (I've found articles from 2007 on the subject of too much JS).

A couple of good articles on the issue as it stands today: Both of these are from Addy Osmani:

A discussion on Hacker News about the above articles:

Maybe some other discussions/articles:

My point is, AMP was created to solve the problem of poor mobile performance. Poor mobile performance is directly attributable to the dependence on JS for basic site functionality.