It's actually a pretty nifty feature when you're browsing the web from a plane's slow wifi.
But the people who designed the page in the first place should be able to make it just as fast without using AMP.
The Problem with AMP
31–40 of 353 posts
Re: The Problem with AMP
#32Using https://encrypted.google.com/ to avoid AMP is a great tip. I'll be doing that, does anybody have more information on what that URL is for? Is it possible to set it as default on iOS/Android somehow? AMP really frustratingly breaks link sharing, and I'd like to totally avoid it.
> does anybody have more information on what that URL is for?
Many years ago, Google Search existed only on http:// and schools used filters to block searches that they didn't like. Then Google shipped https:// for search on www.google.com, upset the schools because they could no longer block just some searches, then moved encrypted search to encrypted.google.com so that the entire domain could be blocked: https://cloud.googleblog.com/2010/06/an-update-on-encrypted-...
Re: The Problem with AMP
#33Is it possible to fork the project and keep all the good things that makes it fast but remove all the evil lock in stuff?
Re: The Problem with AMP
#34Earlier quoted context omitted.
I get the frustration, but mobile sites in general also have this problem. "Request desktop site" should be a more prominent feature, at least in safari which is what I'm familiar with. It's quite buried unfortunately and I think that more non-techies would benefit from knowing about it.
Firefox on Android does have this feature as well.
as does chrome on android
Re: The Problem with AMP
#35One thing I love about AMP, that seems to never be mentioned when people discuss it, is viewing AMP-HTML pages on my laptop. I wrote a small chrome extension that always forwards my page to the equivalent AMP page (if one exists) and the experience of reading the news is so much better. AMP pages off mobile are really really amazing. Compare Non-AMP[0] vs AMP[1] [0] http://www.sfgate.com/bayarea/article/Trump-on-the-…
Yeah but here it's functioning effectively as a better ad-blocker (one that doesn't screw up site layout). Looking at how AMP works, I can see why : you'd have to decide before you know who the user is what ads to show.
Wouldn't that effectively mean that in a search query followed by an AMP site visit only Google has the opportunity to show targeted ads ?
Re: The Problem with AMP
#36And what happened to whole "don't build different markup for different devices" mantra that has been the accepted wisdom in web development for the past 4 or 5 years (whenever responsive design was discovered)? Feels like "m." sites all over again (but this time with google's CDN as a required intermediary).
As someone happy with their AMP site, I'm only happy with it on the basis that my Jekyll theme builds the whole site as a single site that happens to support AMP on the desktop page.
I couldn't imagine dealing with supporting two deployments.
Re: The Problem with AMP
#37Using https://encrypted.google.com/ to avoid AMP is a great tip. I'll be doing that, does anybody have more information on what that URL is for? Is it possible to set it as default on iOS/Android somehow? AMP really frustratingly breaks link sharing, and I'd like to totally avoid it.
> Does anybody have more information on what that URL is for?
You used to have to use that domain to run searches over HTTPS. Google's enabled that for all users now, so it's kind of obsolete -- but apparently it still behaves a little bit differently?
Re: The Problem with AMP
#38The more I read about complaints about AMP, the more it dawns on me that there are still a fair amount of people that do not understand that the web is basically Google's product.
Facebook and others have arrived to take significant time away from that product. Then combine that with things like Facebook Video and Instant Articles. Google is in a difficult position where Facebook may be able to start offering up a superior product for content as opposed to the web.
If you want to blame a big corp for AMP, you should probably take a closer look at Facebook as without it Google risks losing a large chunk of its market.
Re: The Problem with AMP
#39Is it possible to fork the project and keep all the good things that makes it fast but remove all the evil lock in stuff?
If you mean the Google CDN cache, just don't include the Google CDN file and host it yourself instead
Re: The Problem with AMP
#40Sorry, this is a lame blog post. I did not feel any pain in using AMP powered pages.
You must have not wanted access to the site's full set of features, not wanted to use a mobile ad blocker, now wanted access to comments, etc. That's fine, but for many, it's an annoyance.
Comments are half the news anyways :)