|
|
|
|
|
by IanCal
3301 days ago
|
|
Restricting what you use to the AMP subset would make your page quite fast, with a dependency on a javascript file that most mobile browsers should have cached, along with having your page in the top carousel loading in smoothly like all the others. This can all be detected from your main page when crawled (as it'll link to the AMP version) so depending on the device one or the other can be presented as a search result. None of that requires being hosted by google. |
|
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.