3 ms·
Just yesterday an HNer was saying they are in Puerto Rico and the vast majority of pages won't load due to bandwidth restrictions - except for HN and one other
by sangnoir 9y ago
Just yesterday an HNer was saying they are in Puerto Rico and the vast majority of pages won't load due to bandwidth restrictions - except for HN and one other site I'm forgetting. I would bet you AMP pages would load fine for them. HN loves to hate on page bloat and AMP, confusingly.
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.
- mattmanser 9y agoHow is it confusing? I hate page bloat because it's slow. I hate AMP as it's an obvious, extremely damaging, land grab.
- sangnoir 9y agoI went on to differentiate between AMP the standard and Google's search result and serving from Google's cache (the "land grab" aspect). Dismissing both is throwing the baby out with the bathwater IMO - I'll get behind anyone who's encouraging trim pages - such as adhering to the AMP standard.
- pwinnski 9y agoI haven't seen anybody hating on making pages "adhere to the AMP standard." When people express loathing of AMP, we're objecting to exactly what this article describes: an expansive and dishonest land grab by Google. It is reasonable and correct to hate both web page bloat and Google's so-called "solution" that breaks the web.
- bhauer 9y ago> HN loves to hate on page bloat and AMP, confusingly. 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.
- 659087 9y ago> Just yesterday an HNer was saying they are in Puerto Rico and the vast majority of pages won't load due to bandwidth restrictions - except for HN and one other site I'm forgetting. I would bet you AMP pages would load fine for them. HN loves to hate on page bloat and AMP, confusingly. Using hurricane victims to try to trigger an emotional response to aid in the defense of Google's attempts to lock down the web? Bravo.
- dang 9y agoIf you continue to violate the HN guidelines we are going to ban you. Please read https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html and clean up your act when commenting here.
- 659087 9y agoIf calling out attempts to use those suffering the after effects of a natural disaster as props in the defense of Google's shady attempts to lock down the web "violates HN guidelines", maybe it's your guidelines that are the problem.
- danso 9y agoTo be fair, the person you were critiquing was referring to a comment by someone else who had observed the problem from Puerto Rico. Bigger picture implications aside, do we have any reason to believe AMP wouldn’t work as a CDN for folks in such situations?