I wrote a blog post about these proposals a couple of weeks ago and a nice HN thread formed around it.
https://news.ycombinator.com/item?id=16424445But as I said in my post, the problem with posts like today's AMP blog post is that they're too full of jargon to be comprehensible to a general audience. The Web Packaging standard is really cool, but today's blog post just linked out to a ton of web standards without defining them or explaining how they'll work in the future.
If you've got your head deep in AMP's community, this post is quite meaningful, but to everyone else, and especially to the huge community of developers who hate AMP, it reads like Greek.
It reflects a core problem with AMP's developer outreach strategy: a refusal to accept and acknowledge criticism. There are overwhelmingly more AMP detractors than AMP promoters, and the detractors have good arguments, arguments that the AMP team even kinda sorta accepts (which is why they're trying to push through these browser standards, to address the bugs).
But you'll never hear AMP technical leaders like Malte Ubl or Paul Bakaus saying, "Yes, we accept that criticism, and the problems with AMP are really serious, and here's what we're doing to fix this. In the meanwhile, for many sites the tradeoff is worth it anyway."
The top thread in the HN thread was not whether the AMP brand was toxic but why the AMP brand is toxic. I think that if the AMP team had somebody focused on telling AMP's story, humbly and honestly, with a focus on the web developer community on HN, Reddit, Smashing, etc. it could have really helped.
Now, I think it's too late. The new Web Packaging thing shouldn't be called "AMP." The new "AMP for email" thing shouldn't be called AMP, either, because everybody knows that AMP sucks, and there's really no way to claw your way back from that.