Re:Google AMP Cache, AMP Lite, and the Need for Speed
by detaro on Thursday January 12, 2017 @04:38PM
(#13386356)
And what happens if you load the AMP version from their server, which IMHO is the fairer comparison when discussing complaints about the Google cache of it? AMP as a "document standard" on top of HTML would IMHO already solve a lot.
[ Parent
| on HN ]
Re:Google AMP Cache, AMP Lite, and the Need for Speed
by davewasthere on Thursday January 12, 2017 @06:31PM
(#13387120)
It's not really a fairer comparison, because their non-AMP view is what they currently think is appropriate to serve.
It's not.
The web has bloated out of control - and while I'm not a fan-boy, I at least think AMP encourages the right things and is a progressive step forward in the right direction.
I _like_ viewing AMP pages from an end-user perspective. And I don't think they're terribly onerous from a publisher/dev perspective.
Re:Google AMP Cache, AMP Lite, and the Need for Speed
by detaro on Friday January 13, 2017 @03:55PM
(#13394616)
Google could easily "motivate" them to provide AMP pages (as they have successfully done) without adding their own caching layer, which the complaints above mostly seemed to be about.
Re:Google AMP Cache, AMP Lite, and the Need for Speed
by dandv on Thursday January 26, 2017 @06:59PM
(#13496580)
This post explains very well the #1 benefit of AMP caches (yes, there can be more than Google's, and Cloudflare has just released their own cache): pre-rendering:
https://medium.com/@pbakaus/why-amp-caches-exist-cd7938da245...