3 ms·
A very low quality article. The whole point of AMP is to define a restricted subset of HTML that is safe to prerender and still provide working analytics to the
by lern_too_spel 9y ago
A very low quality article. The whole point of AMP is to define a restricted subset of HTML that is safe to prerender and still provide working analytics to the publisher. When you prerender, the advantage of AMP is substantial as it is impossible to beat a user experience of instant, which is why users prefer it and why publishers go through the trouble of implementing two web versions of their web pages (in addition to Facebook and Apple News non-web versions).
The point of the AMP cache is not for CDN speed, as the author mistakenly believed and measured, but for same-origin or CORS prerender, and Google is not the only implementer.
- millstone 9y agoPublishers go through the trouble in order to get the boost in Google's rankings. As an iOS user I find AMP to be quite buggy, and AMP versions of pages like reddit are borderline non-functional. I don't prefer it at all.
- lern_too_spel 9y agoYour experience was due to a bug in iOS that Apple has since fixed. Those of us using platforms that allow quickly updating non-buggy browsers never saw such issues.
- what_ever 9y agoIt's a trouble of writing template once though and it is not that much work. I worked on this at my previous employer and it was alright, little frustrating but once it was done, it was done until you redesign the pages. Disc: Googler but nowhere close to AMP.
- abritinthebay 9y agoIt’s a continuous pita as it’s buggy as hell and as a publisher we are the ones who get blamed.
- manigandham 9y agoIt is absolutely not that simple. We are a marketing company working with hundreds of publishers and this is a constant struggle. It's splitting whatever little dev time they have on yet another format that adds nothing to the already universally accessible "web" version.
- madeofpalk 9y agoIsnt that going to depend on your publishing platform?
- underwater 9y agoThe AMP team actually got up on stage and tried to tell a bunch of developers that sites could be converted in a couple of hours. Worst developer outreach I’ve ever seen. I work for a major news publisher. Rendering is tied to legacy systems with esoteric business logic, journalists could embed any one of hundreds of first or third party embeds, and many pieces of content embed arbitrary HTML directly. It seems crazy, but this is how a lot of news organisations are dealing with content. AMP is designed to fail on any error, is incompatible with existing HTML and CSS, and to do CSS inlining right means completely rewriting existing build pipelines. In a Google world implementing AMP wouldn’t be that hard; code is generally high quality and you control the stack. In media organisations responsibility for domains might extends between different (poorly communicating) teams and many critical components are handled by third party systems. Doing something simple like implementing AMP’s custom CORS logic was a nightmare. Building an AMP site is not hard. Building an AMP site that runs on legacy publishing systems IS hard. This is something the AMP team should understand, but they seem incapable of accepting any sort of feedback.
- geuis 9y agoAMP is a cancer on search results. The purpose of a search engine is to provide the best links it can to content related to a user’s search. The search engine should not be providing the content of the search result as a primary link. Having a backup cache of the link is fine in case it changes or disappears. It’s the responsibility of the original site to be able to serve its visitors.
- lern_too_spel 9y agoMost users think otherwise. Most users prefer results that load instantly, which is why the dominant search engines in the US, Japan, China, and Russia as well as the dominant short message sharing services in the US and China all provide special support for AMP results.
- pcwalton 9y agoIt's hardly surprising that the dominant search engine in the US and Japan uses AMP, since that search engine and AMP are products of the same company.
- lern_too_spel 9y agoThe dominant search portal in Japan until very recently was Yahoo! Japan, which runs its own AMP cache and is a product of Softbank. The dominant search engine in the US is Google. These two companies hold no significant investments in each other.
- Kalium 9y agoYou're right! Users are looking for something very specific when they search. Generally, they are looking for a particular bit of information. Sometimes the best way to get that is to click through to someone's site and read an essay. At other times, well, it's possible that it might be the best experience for the user to have information presented to them immediately. It's definitely negative for people whose entire business model depended on those clicks, though. I understand their pain, fear, and anger.