You Don't Get AMP

[colept]

Cleverly leaves out the part where Google siphons your traffic. AMP is the trojan horse and I don't "get" those welcoming it into the gates.

[quarterto]

If you use Cloudflare as your CDN, is Cloudflare "siphoning your traffic"?

[flukus]

> Tap a Top Stories card, and bam, you’re in the article. Takes maybe 100 milliseconds, just at the edge of perception. You can’t do that with a full page load: not on a 3G network, not on a mobile CPU.

Yes you can, quite comfortably. Pre rendering is just patching the bloated web, not fixing it. If you want to make the web better focus on less javascript, with noscript on I get AMP like speeds almost everywhere.

[quarterto]

But that's the point: AMP allows far richer pages than just totally cutting out Javascript. Like it or not, the web is an application platform.

[webartisan]

As someone who has developed for mobile web, it can be surprisingly hard to push back on bloat from marketing / seo / analytics teams. I hope this becomes a W3C standard so us developers can show them the finger the next time they want to bring mobile web to a crawl.

[CaptSpify]

Does Google not have any guidelines that say to keep pages small and fast? Seems like they should have a list of things to keep in mind when looking at search-rankings

[CaptSpify]

Oh, I get AMP just fine. I get that it's a power play by Google. The problem AMP is trying to solve is very real. But instead of trying to fix the problem, Google is using it to take an even greater chunk of the web.

No thanks

[quarterto]

> Google gonna Google. They’ve been dangling carrots in front of publishers for twenty-one years.

[RichardHeart]

If you let GOOGLE control the browser, OS, search engine, keyboard, maps, and user created video content, what could possibly go wrong?

[owebmaster]

OP: You don't get HTML