4 ms·
I am conflicted Yes, AMP is an anti-competitive move by Google At the same time AMP is "faster" because it gets rid of all the nagware and JS crap that the or
by raverbashing 6y ago
I am conflicted
Yes, AMP is an anti-competitive move by Google
At the same time AMP is "faster" because it gets rid of all the nagware and JS crap that the original page has.
So yeah, I don't like what Google is doing but I don't like what NYT is doing neither
- ogre_codes 6y ago> At the same time AMP is "faster" because it gets rid of all the nagware and JS crap that the original page has Google gives preference to AMP content whether the source page is lightning fast or not. I get the frustration with crappy web pages, but a big part of the reason web pages are getting increasingly crappy is because Google and Facebook (and to a much lessor extent Amazon in a weird way) have a stranglehold on the web advertising market and publishers are getting smaller and smaller slices of advertising revenue. AMP increases Google's lock on the market. Since AMP pages can only really be monetized by the publisher, this puts even more power in Google's hands.
- markosaric 6y agoIt is ironic considering that 7 out of top 10 most used third party connections on websites are owned by Google. So you can see why there must be some kind of internal struggle at Google. They understand the value of a faster web but they also cannot go after the main cause of the slow web. And this is how technology such as AMP gets invented and makes things worse. https://markosaric.com/google-amp/ https://markosaric.com/google-amp/
- moksly 6y agoAMP is faster? I’ve never been on an AMP page where I didn’t eventually need to go to the actual site to get the full content. So it’s really just an annoying step between me and the content I searched for. It’s been one of the primary things that’s driven me away from google and into DDG. I don’t really care about privacy enough to leave google, but I end up leaving more and more of their services because their competition is just less annoying.
- amelius 6y agoBut why allow a third party (Google in this case) to collect data on your reading behavior on NYT?
- varenc 6y agoIf you loaded the megabytes of JS served by the actual nytimes.com, they’ll certainly be sending your data to Google as well for advertising purposes. (Albeit, that’s far more blockable)
- acdha 6y ago> AMP is "faster" because it gets rid of all the nagware and JS crap that the original page has. AMP is faster only for poorly-optimized JS-heavy pages but the design is fundamentally flawed to require all of its own large amount of JavaScript to run before anything displays, whereas most of the traditional bloat doesn’t block rendering. That means any optimized page - Washington Post, NYT, etc. – loads noticeably faster even before you factor in how often you need to wait for AMP to load, realize that some part of the content is missing, and then wait for the real page to load anyway. That design forces it to be less reliable, too: before I stopped using Google on mobile to avoid AMP, I would see on a near-daily basis failed page loads due to the AMP JS failing in some way and when it wasn’t failing it was still notably slow (5+ seconds or worse on LTE). Since all of that JavaScript is forced into the critical path, anything less than unrealistically high cache rates means the experience is worse than a normal web page. WPT examples: https://www.webpagetest.org/result/200704_GR_62165b7f695e30026f5ac3964d16864b/ https://www.webpagetest.org/result/200704_GR_62165b7f695e300... https://www.webpagetest.org/result/200704_5F_f5c36a7c41cf4c2429880dc1a42d4665/ https://www.webpagetest.org/result/200704_5F_f5c36a7c41cf4c2...
- lern_too_spel 6y agoThose tests show you don't understand why AMP works. It works because it prerendered, which is going to be faster than anything you can do.
- acdha 6y agoIf that were true, AMP would be consistently faster. Since anyone who’s used it knows that it’s not, you would find it educational to learn about the issues with detecting user intent, reliably prefetching dependencies, and the relatively small / frequently purged caches on mobile browsers. AMP’s design is very fragile: if you are using Google search results, they correctly guess what you’re going to tap on before you do and your browser fully preloads it, it _might_ be faster to run all of that JavaScript before anything is allowed to load and render. If any part of that chain fails, it will almost certainly be slower or, because it disables standard browser behavior, prevent you from seeing content at all.