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

111–120 of 247 posts

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

#111

Post by angry-hacker »

mathw wrote: post #15
pmlnr wrote: post #4

"We remove image data that is invisible to users, such as thumbnail and geolocation metadata. For JPEG images, we also reduce quality and color samples if they are higher than necessary." Great. Except that that information might be deliberately a part of the image. These things should be opt-in.

They are. You don't have to publish an AMP version.

And no one is forcing you to work, don't ever whine about your salary. It's voluntary agreement.

Google own the web and people have no choice. Monopoly.

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

#112

Post by acdha »

Panino wrote: post #106

I think the root issue here is that most websites are now designed by people who don't even know HTML. ("You had one job!") From there, we get years of unoptimized, bloated websites made by people drawing pictures with HTML editors. They are exclusively focused on visual presentation and ignore any mechanics under the hood. Not everyone, but most. Finally Google can't take it anymore and creates AMP as an angry middl…

> From there, we get years of unoptimized, bloated websites made by people drawing pictures with HTML editors.

One look at the source code for most popular sites shows this isn't true – and that makes sense because when you look at the average sluggish site the bloat is mostly JavaScript rather than the HTML source.

What's actually happening is that a bunch of people are working hard on something which is important to them but not the user: advertising and analytics, followed by “social” sharing. Since those numbers are associated with revenue, they're directly seen as important whereas concerns about page-weight are more subtle and often an inadequate check on bloat until it gets really bad.

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

#114

Post by Zelphyr »

fragmede wrote: post #74
tiffanyh wrote: post #42

There's a lot of hate going on in this thread towards Google ... maybe unfairly. Keep in mind, a huge reason why Google created AMP is because website bloat has gotten out of control. It's not uncommon for a simply Wordpress blog to be 4MB in size and have 70 requested objects to fetch. I live in a geography that has LTE and web site are painfully slow to load on mobile devices. I can't even imagine what the Internet…

You have a valid point about page bloat, but its a distraction and a poor excuse for hijacking the entire web. My hate for AMP is because Google is using its might to break a fundamental contract for how the web works - the URL bar shows what site you're on, and content is coming from that domain. No other site has gotten away with this. The last time I can recall someone attempting something similar was Digg (rememb…

> Digg (remember them?) with the "Digg bar" which added a toolbar linking back to Digg for all of the internet, and well, what happened to them?

At the risk of getting off topic, the reincarnated Digg is actually pretty good.

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

#115

Post by cygned »

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 hate the scrolling on mobile (iOS). I don't know what they tried to do, it feels like a JavaScript smooth scrolling on top of native smooth scrolling.

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

#116

Post by kavok »

MrVitaliy wrote: post #44
artimaeis wrote: post #32

Earlier quoted context omitted.

Can you detail the issues you've had with AMP pages? I use Safari on iOS 10.2 daily and have never noticed an issue loading AMP pages.

I'm on iOS 10.2 also. Searching for something like "site:reddit.com casserole" gives a couple of AMP results. Clicking them just shows google loading circle thingy indefinitely, the page never opens.

I have the exact same issue on iPhone 7 iOS 10.2

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

#117

Post by msbarnett »

bsimpson wrote: post #91
fragmede wrote: post #74

Earlier quoted context omitted.

You have a valid point about page bloat, but its a distraction and a poor excuse for hijacking the entire web. My hate for AMP is because Google is using its might to break a fundamental contract for how the web works - the URL bar shows what site you're on, and content is coming from that domain. No other site has gotten away with this. The last time I can recall someone attempting something similar was Digg (rememb…

If browsers detected AMP pages and treated the address bar accordingly: Cached from: nbcnews.com/some-article Would you feel better about it?

Under no circumstances should web browsers be hard-coding special favors to paper over deficiencies in the user experience of Google's news product.

The entire idea is insane. Google is just another company on the internet, and should be treated like any other.

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

#119

Post by cekvenich3 »

Even w/o AMP you need to have a no javascript version for SEO.

Even w/o AMP you need to have fast downloading images.

Even w/o AMP you must use a CDN.

So don't call it AMP. Call it: "SEO optimized and for when users are not on Wi-Fi or for huge scale/load". You can include the lighting bolt or not.

Wha, wha.

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

#120

Post by isleyaardvark »

cygned wrote: post #115
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 hate the scrolling on mobile (iOS). I don't know what they tried to do, it feels like a JavaScript smooth scrolling on top of native smooth scrolling.

In mobile Safari you can tap the area right above the address bar to scroll all the way back to the top of the page. But not on AMP pages.
Post reply on HN