Accelerated Mobile Pages
The PR was subsequently closed with the comment "We decided to remove metadata requirements from AMP." See: https://github.com/ampproject/amphtml/pull/593
XML like fragility
It appears that initial implementation(s) of AMP HTML consuming code treat it similarly to old XML consuming code, which is to fail in a fragile way, e.g. as noted in https://twitter.com/bryanrieger/status/651782717676216320
Sorry, this page is not valid AMP HTMLfollowed by a footer link to continue to www.nydailynews.com.
- iOS screenshot of problem: https://twitter.com/shinypb/status/733302396995010561
When developers turn their problems into users' problems: AMP, following in XHTML's proud footsteps.
- 2017-06-26 : I decided to disable AMP on my site (archived)
- 2017-05-19 : Kill Google AMP before it KILLS the web (archived)
- 2017-01-19 : Google AMP is Not a Good Thing via @jevdemon:
- 2016-11-27 : Google's AMP is a gilded cage
- 2016-10-15 : Google May Be Stealing Your Mobile Traffic
More: (to be put into citation template, and inserted into the above list)
- 2017-08-31 Ethan Marcotte: AMPersand
- 2017-08-16 Google AMP is bad for E-commerce
- 2017-03-13 Jeremy Keith In AMP we trust
- 2017-02-06 https://amphtml.wordpress.com/2017/02/06/whats-in-an-amp-url/amp/
- 2015-10-10 Jeremy Keith: AMPed up
- 2016-04-06 Accelerated Mobile Pages (AMP): Open or closed?
- 2016-02-24 CPP: A Standardized Alternative to AMP (Related: HN comments on, WICG Content Performance Policy draft)