Google is taking the content and serving it themselves.
The problem is sites being slow in the first place, but Apple isn't commandeering the content itself like Google is by creating a mode where the browser can enhance legibility of any article.
Google is taking the content and serving it themselves.
The problem is sites being slow in the first place, but Apple isn't commandeering the content itself like Google is by creating a mode where the browser can enhance legibility of any article.
Content authors voluntarily publish their content in AMP form, so it doesn't seem fair to say that they commandeer anything: AMP is a subset of HTML intended for a fast mobile experience, and if you decide to take part you publish flags allowing Google to cache it. Google isn't unilaterally converting content to AMP.
The core argument against AMP primarily seems to be a fear that users will actually prefer AMP content. Which is ultimately rather anti-user.
How on earth did you arrive to that conclusion?
How is Google taking the content? Isn't it the creator that is publishing their content using AMP?
AMP is garbage, and honestly whoever signed off on it shouldn't have a position at Google or wider tech community.
https://developers.google.com/amp/cache/faq#can-i-stop-conte...
None of that requires being hosted by google.
AMP is a subset because in addition to the elements, they provide a set of restrictions that would make your page "valid AMP" and cached by Google's creepy CDN thingy.
Caching is a part of the platform and is entirely coherent with the goals, and if you want analytics or ads, you approach those in a different way. AMP caching isn't limited to Google - Bing, for instance, caches and serves AMP as well. Ultimately anyone could, and HN could cache and quick-serve AMP content for supporting sources. AMP is open source and any one can take part.
I should add a side note that many of the comments on here have taken the predictable turn of claiming that people who defend AMP are "over invested" or must work at Google. I have nothing to do with Google, and have a reasoned, fact-based opinion on AMP. I think it's a last-ditch salvation for a web where sites are demonstrating a tragedy of the commons. Nor do I think everyone denouncing AMP works for Apple or some competitor.
What I dislike is not being able to choose simply to make and host an AMP content myself without google taking it and hosting it on their own servers. I cannot opt-in to this, nor can I opt-out. My only choice is to not do anything with AMP.
What is the way to host your own AMP cache? The AMP project under caching just shows the google cache and links to a google page.
As a side note, what if what I publish is not acceptable by google? Will they remove my content, despite having already taken it and given it to people under that URL? If AMP content must be loaded from the caches, is my content only valid AMP if google and the jurisdictions they operate under approve?