5 ms·
This entire AMP project is already workaround after workaround, but this gets even worse. All that would have been required to solve these problems would have
by kuschku 10y ago
This entire AMP project is already workaround after workaround, but this gets even worse.
All that would have been required to solve these problems would have been a simple standard for lightweight pages that anyone could implement, and a better ranking for any complying page.
Google could offer the cache optionally, or sites could do their own stuff.
Then, the entire rendering and preload problems could have been improved with a simple JS api to allow for exactly that.
Then none of the rest would have had to be solved, we’d get none of Google’s increased dominance over the web, and we wouldn’t have to put up with thousands of AMP pages loading slower than normal pages (because they bundle fucktons of useless JS) for the sake of improving the loadtimes of a handful of sites.
- Ajedi32 10y ago> All that would have been required to solve these problems would have been a simple standard for lightweight pages that anyone could implement FWIW that's exactly what AMP is. It's not a W3C standard, but a standard nonetheless: https://www.ampproject.org/docs/get_started/create/basic_markup https://www.ampproject.org/docs/get_started/create/basic_mar...
- taylorbuley 10y agoI'd love them to standardize the serving aspects, in addition to the formatting aspects. Changes like these seem somewhat arbitrary but yet impact everything end-to-end.
- rocqua 10y agoAMP is more though. Or if you want to define AMP narrowly, google does a lot more with AMP than just the standard.
- callahad 10y agoAMP is not a standard. It is a Google product with developer documentation, but that documentation does not make it a standard any moreso that Twitter having an API makes it a standard. AMP allows your websites to rank better / more prominently within Google and Bing, but it comes at the cost of ceding control of markup itself to Google. A truly open standard would not have hard dependencies on a single for-profit corporation.
- kuschku 10y agoSo, it’s only a standard, there’s no AMP Cache, no AMP Viewer, no requirement for loading Google’s JS? That’d be a solution. This is merely a workaround.
- throwaway91111 10y agoSo what the hell is up with google search results? I don't get the connection. What is stopping google from just giving me the URL?
- acdha 10y ago> a simple standard for lightweight pages that anyone could implement, and a better ranking for any complying page. It doesn't even need to be that much work: simply publishing desired time-to-render scores would have had the same effect: x seconds for mobile 3G, y seconds for desktop, etc. Maybe add a couple of <link rel=preload> tags for the top 1-2 results and the mobile experience would be enormously better than what we get with AMP and its 100KB of render-blocking JavaScript.