[1] https://www.ampproject.org/docs/get_started/create/basic_mar...
Additionally, AMP wants to become the arbiter of the mobile web. Just look at their list of "Supported ad networks." [1]
Who gave them the authority?
AMP worries me greatly.
[1] https://github.com/ampproject/amphtml/blob/master/builtins/a...
NEVER give this power to a central authority that's not democratically controlled.
And yet, some people still do that mistake.
But you can fork them, so it should be okay, right?
Another way to do that is to strip your page down to core, performant components without loading a JS library from Google. But Google dangles the carrot of improved SEO with AMP, so everyone has to do it anyway.
(note: they don't actually prioritise AMP pages, they prioritise page load speed. But AMP pages are put inside a Google CDN, so, what do you know, they load fastest)
AMP is not meant for page authors — usually, they are painfully aware of how much bloat they add. They don't have a choice when sustainability is in the balance.
AMP is for the ad networks. It draws sane restrictions to what they can do. On their end, ad networks agree to that because Google is a large partner of them and because the worst possible outcome would be having everybody use ad blockers.
This is not solved by AMP, it's absolutely the choice of publishers.
> AMP is for the ad networks.
Not really, you can see their official roadmap. Many of the original principles have already changed and many of the intrusive ad formats are already back in (like autoplay outstream video units). The only real optimization is better async loading which could already be done with proper coding by publishers and ad networks.
This isn't really a solution when many authors use a CMS, like WordPress and others, where the bloat is built-in. Sure you can write a custom theme etc, but not everyone (1) has the ability to do that, and (2) wants to dedicate the time to do that.