Hacker News Reader

Comment by lern_too_spel | Hacker News Reader

I think you read too quickly, or skipped over a few key parts.

Yes, AMP can cause some pages/content to load more slowly. This was stated in the write-up, and supported a link to Google's own DOJ disclosures. In that source we read that Google knew that some publishers avoided AMP because their own pages were shown to load more quickly without it, especially considering 1-second throttling on Google's part for non-AMP pages, aimed to give AMP a "nice comparative boost".

I think you didn't read that report at all. The nice comparative boost was for ads. AMP pages loaded from an aggregator are rendered before you click on them, and the DOJ disclosures did not dispute that this would cause them to load faster for users as it obviously would.

Nobody complained about Google's RSS monopolizing because the search engine doesn't provide RSS URLs in the top results, unlike they do for AMP links, at least nearly as frequently. RSS is also far from a similar case study to AMP in how web content is delivered. RSS optional, AMP was a lazy web dev's means to presenting pages over mobile without having to think about layout. At least that's what if felt like to me as a web user.

And how is showing AMP in top results monopolizing the web? Bing does the same thing. A social news aggregator could do the same thing if it thinks people could read the article and go back to scrolling the feed faster.

AMP loads instantly. There is nothing lazy about supporting it. Just like RSS, it requires extra work for the publisher to get the user the instant-loading behavior they desire.

Reply on news.ycombinator.com