Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google AMP Cache, AMP Lite, and the Need for Speed

developers.googleblog.com

Post reply on HN
Print view View original

201–210 of 247 posts

Re: Google AMP Cache, AMP Lite, and the Need for Speed

#201

Post by applejuicestand »

saycheese wrote: post #10

There is zero reason for AMP to be hijacking URLs or embedding any additional elements into a page that are detectable by the average user. Beyond that, universal opt-out should be possible and stats on the percentage of users opting out should be published real-time. As such, until this is addressed, I am against AMP.

Looking at this from the users perspective, the URL is becoming less noticeable anyway. On mobile you don't have the screen real estate for it. And I don't see the average user complaining about the sub-second loading times. If anything, this is a step in the right direction.

Re: Google AMP Cache, AMP Lite, and the Need for Speed

#202

Post by unclebucknasty »

wmf wrote: post #128
ClassyJacket wrote: post #12

Earlier quoted context omitted.

It also sucks if you want to interact with the page, since, inanely, you can't click through to the real page.

What can you do on the real page that you can't do on the AMP version?

Navigate the site, share the underlying page, etc.

Re: Google AMP Cache, AMP Lite, and the Need for Speed

#203

Post by tdkl »

Sir_Cmpwn wrote: post #177
tdkl wrote: post #176

Earlier quoted context omitted.

It sure would be awesome if Chrome on Android had it available as an option. But, it's Google.

If you trust APKs from random strangers on the internet, here's my custom Chromium for Android build with DDG support: https://sr.ht/dIQO.apk Here's the patch that adds it to the list of search providers: https://sr.ht/h4bZ.patch

Thanks, I tried some Chromium based browsers on the Play Store, but they all have unreliable or even non working Chrome Sync. I'd go full FF, if scrolling on Android wasn't so jerky compared to Chrome.

Re: Google AMP Cache, AMP Lite, and the Need for Speed

#204

Post by gressquel »

macNchz wrote: post #84
rubyn00bie wrote: post #36

I hate AMP. Not even kind of, I mean so much I've started using Bing (DuckDuckGo hasn't been so useful for me). Beyond the distasteful navigation hijacking, and often broken or buggy page loading... I think Google throwing its weight around to force publishers to use it is an abusive use of power. I also think it's an unnecessary standard since it's nothing more than simple well wittten HTML and CSS. Yes, we should m…

I switched my default search engine on my phone from Google to DuckDuckGo because I got sick of the growing number AMP links, which I also don't like for all the same reasons you listed. They are a bad reminder of the early days of the mobile internet when lots of websites would automatically redirect you to a terrible 'mobile version'. I certainly want better mobile sites, but not in the form of these AMP pages.

Changed my iPad search engine to Bing

Re: Google AMP Cache, AMP Lite, and the Need for Speed

#205

Post by davewasthere »

detaro wrote: post #168
stuckagain wrote: post #92

Earlier quoted context omitted.

You don't seem to understand the technology or the argument you made. The URL bar says google.com because google.com is serving the content you are reading. In other words, it exactly honors the "fundamental contract" you find so important. I also dispute your qualitative opinion that nbcnews.com works "just fine". If I load their top story currently from AMP it loads in about half a second. If I visit it from nbcnew…

And what happens if you load the AMP version from their server, which IMHO is the fairer comparison when discussing complaints about the Google cache of it? AMP as a "document standard" on top of HTML would IMHO already solve a lot.

It's not really a fairer comparison, because their non-AMP view is what they currently think is appropriate to serve.

It's not.

The web has bloated out of control - and while I'm not a fan-boy, I at least think AMP encourages the right things and is a progressive step forward in the right direction.

I _like_ viewing AMP pages from an end-user perspective. And I don't think they're terribly onerous from a publisher/dev perspective.

Re: Google AMP Cache, AMP Lite, and the Need for Speed

#206

Post by flukus »

monochromatic wrote: post #156
macNchz wrote: post #84

Earlier quoted context omitted.

I switched my default search engine on my phone from Google to DuckDuckGo because I got sick of the growing number AMP links, which I also don't like for all the same reasons you listed. They are a bad reminder of the early days of the mobile internet when lots of websites would automatically redirect you to a terrible 'mobile version'. I certainly want better mobile sites, but not in the form of these AMP pages.

AMP annoys my too, but it hadn't occurred to me to switch to DuckDuckGo. Good idea, just made the change.

I started using it because it get's better results. Google says "oh you searched for something vaguely related two weeks ago? let me show you those results instead of what you're searching for now".

Re: Google AMP Cache, AMP Lite, and the Need for Speed

#207

Post by RileyKyeden »

Lazare wrote: post #173
rubyn00bie wrote: post #36

I hate AMP. Not even kind of, I mean so much I've started using Bing (DuckDuckGo hasn't been so useful for me). Beyond the distasteful navigation hijacking, and often broken or buggy page loading... I think Google throwing its weight around to force publishers to use it is an abusive use of power. I also think it's an unnecessary standard since it's nothing more than simple well wittten HTML and CSS. Yes, we should m…

Conversely, I love AMP. I find it works well, I don't think there's any abuse of power, and I think it's an entirely necessary standard.

Same. An AMP link tells me two things:

1: I won't have a page that bounces around for 5 minutes as useless, non-content elements load.

2: I won't have to peer at a few lines of content through a window of toolbars and ads.

Re: Google AMP Cache, AMP Lite, and the Need for Speed

#208

Post by flukus »

tiffanyh wrote: post #67
greenspot wrote: post #50

Earlier quoted context omitted.

> 5 different JavaScript frameworks This is not the problem. You can easily use i.e. React and some related libs on mobile without slowing down the experience at all. Everything will be fast and responsive, loading times and the mobile site itself (if done right). The problem Google tries to address (and this is a real problem) are the cascaded ad networks on webpages which load hundreds of JS libs once a page is loa…

>> "This is not the problem. You can easily use i.e. React and some related libs on mobile without slowing down the experience at all." Hasn't Facebook proven this to be incorrect. Facebook mobile app was originally just HTML5 & JavaScript. The experience was so slow, they ditched it and instead built a native iOS & Android app. [1] [1] https://techcrunch.com/2012/12/13/facebook-android-faster/

No, fastlite and a dozen other facebook apps have proven this incorrect. The official facebook app is slower, more bloated and battery draining than the mobile version ever was.

Re: Google AMP Cache, AMP Lite, and the Need for Speed

#209

Post by d0vs »

ParadoxOryx wrote: post #17
saycheese wrote: post #10

There is zero reason for AMP to be hijacking URLs or embedding any additional elements into a page that are detectable by the average user. Beyond that, universal opt-out should be possible and stats on the percentage of users opting out should be published real-time. As such, until this is addressed, I am against AMP.

Sounds like Cloudflare is working on it [1]. "In the spirit of open source, we're working to help develop updates to the project to address some of publishers' and end users' concerns. Specifically, here are some features we're developing to address concerns that have been expressed about AMP: ... A way for end users who would prefer not to be redirected to the AMP version of content to opt out" [1] https://blog.clou…

UX is still horrendous.

Re: Google AMP Cache, AMP Lite, and the Need for Speed

#210

Post by alpb »

rubyn00bie wrote: post #36

I hate AMP. Not even kind of, I mean so much I've started using Bing (DuckDuckGo hasn't been so useful for me). Beyond the distasteful navigation hijacking, and often broken or buggy page loading... I think Google throwing its weight around to force publishers to use it is an abusive use of power. I also think it's an unnecessary standard since it's nothing more than simple well wittten HTML and CSS. Yes, we should m…

I often think if this would make people like you happier:

A spark icon next to the search result that would take you to the AMP page if you want to just read something without navigating to a whole new website and the behavior of clicking to a search result is the same as before ––or vice versa, an icon would still take you to a website.

Post reply on HN