News for hackers. Stuff that matters.

A comment on Kill Google AMP before it kills the web. Parent comment

Re:Kill Google AMP before it kills the web by tyingq on Saturday May 20, 2017 @08:44PM (#14385165)
It is interesting that AMP is about the only edge cache that doesn't let you use your own domain. Cloudflare is fairly good evidence that it's workable at scale. Of course, that would eliminate the hijacking header and Google control over the URL.

Edit: Disagree? What part isn't true?

[ Parent | on HN ]
Re:Kill Google AMP before it kills the web by wmf on Saturday May 20, 2017 @09:39PM (#14385314)
Do you think Google wants to hijack the URL and add extra chrome? They don't. They want the absolute fastest performance which requires prerendering which requires hijacking the URL. (This seems like a bad tradeoff to everyone on HN.)
[ Parent | on HN ]
Re:Kill Google AMP before it kills the web by tyingq on Saturday May 20, 2017 @09:47PM (#14385329)
That extra chrome didn't even include a way to see the original URL until after much squealing. It did, however, include left/right swipe to other people's content. The MVP that rolled out fairly clearly shows who benefits.

An edge cache of an optimized page is plenty fast without preload. Images, in fact, can be preloaded cross domain if that is really needed.

You know it's a mess when the New York Times has to inject a "sorry this video doesn't work on AMP pages, visit our site" message on stories.

[ Parent | on HN ]