You Don't Get AMP(blog.153.io) |
You Don't Get AMP(blog.153.io) |
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.
No thanks
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/
This is exactly what means not be yours. It's Google and they lease it to you.
> But these are just guidelines, and Google can’t guarantee they’re behaving well, so they’re not first-class citizens.
> I’d love for this to be something you could statically verify, just like AMP HTML, so that anybody could add a Cache to the ecosystem and get a lightning bolt on Google search results and Cloudflare links and Twitter Moments™, but I’m pretty sure this reduces to the Halting Problem.
AMP is a PROXY/MITM service, with all the perks that come from being such a service. There is nothing stopping google ,or whatever company owns them after they become a Yahoo!, from changing their "policy" to better be aligned with their interests.
Have a look through the list of AMP components, you'll be surprised what's possible. https://www.ampproject.org/docs/reference/components
Google loves AMP because they (and only they) get to still track users.
Wrong. https://www.ampproject.org/docs/reference/components/ads/amp...
This is a problem that Google created. If they would prioritize small, simple, fast sites, and rank them higher, people would make more sites like that. Google is the one pushing slow, bloated sites to the top of the list. Now they are coming in to "fix" the problem that they made.
As soon as Google stops providing value to publishers, they are the industry.