I have noticed HNers conflate AMP the standard and Google Search's caching behaviour and/or ranking of AMP pages. I love the former, and not the latter. They really ought to make it possible for mobile search users to opt-out of getting AMP results.
I have noticed HNers conflate AMP the standard and Google Search's caching behaviour and/or ranking of AMP pages. I love the former, and not the latter. They really ought to make it possible for mobile search users to opt-out of getting AMP results.
I'm not one to write much about AMP, but I don't see why simultaneously disliking page bloat and AMP is confusing. I simultaneously dislike (or like) many pairs of things that are apparently at odds with one another.
The charitable reading of those of us who dislike AMP and page bloat simultaneously is that we want developers (and, importantly, the people who give direction to those developers) to economize on their own. Stop adding every hip third-party script, social sharing widget, tracking library, and framework to your otherwise simple webapp. It's quite easy to trim the fat from a webapp; you just need the organizational conviction to do so.
AMP is a trojan horse, in more ways than one. One good: It uses a compelling marketing message to deliver much-needed trimming. But two things are obvious to most developers: (a) it's not necessary to adopt AMP to make your app trim and (b) AMP comes with a lot of baggage. So the message from HN is: there are better options, and they're not even technically difficult.
I hate page bloat because it's slow.
I hate AMP as it's an obvious, extremely damaging, land grab.
It is reasonable and correct to hate both web page bloat and Google's so-called "solution" that breaks the web.