You Don't Get AMP
blog.153.io
You Don't Get AMP
1–10 of 37 posts
Re: You Don't Get AMP
#2Cleverly 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.
Re: You Don't Get AMP
#3Cleverly 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.
If you use Cloudflare as your CDN, is Cloudflare "siphoning your traffic"?
Re: You Don't Get AMP
#4> 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.
Re: You Don't Get AMP
#5> 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.
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.
Re: You Don't Get AMP
#6Cleverly 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.
If you use Cloudflare as your CDN, is Cloudflare "siphoning your traffic"?
Does cloudflare take users to a webpage that isn't yours with a header with a button that doesn't lead to your site?
Re: You Don't Get AMP
#7> 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.
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.
What does amp give me that a non-js page can't?
Also, applications aren't the target for amp.
Re: You Don't Get AMP
#8Oh, 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
Re: You Don't Get AMP
#9Earlier quoted context omitted.
If you use Cloudflare as your CDN, is Cloudflare "siphoning your traffic"?
Does cloudflare take users to a webpage that isn't yours with a header with a button that doesn't lead to your site?
The page is still yours. You have absolute control over the branding, the analytics, the monetisation. Just because it happens not to be served from your domain doesn't mean it's not yours.
Let's also not forget that AMP is actively encouraging alternative caches: Cloudflare Ampersand[1] was announced literally an hour after my post. It's a whitelabelled AMP cache aimed at solving this exact problem.
[1]: https://www.cloudflare.com/website-optimization/ampersand/
Re: You Don't Get AMP
#10Oh, 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
> Google gonna Google. They’ve been dangling carrots in front of publishers for twenty-one years.