News for hackers. Stuff that matters.
Re:Google AMP Cache, AMP Lite, and the Need for Speed by tiffanyh on Thursday January 12, 2017 @11:00AM (#13383244)
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 experience is like in parts of the world still on 2G or 3G.

If people would stop for a moment and question to themselves "do I really need to use 5 different JavaScript frameworks just to post to my simply personal blog", there's a good chance AMP would not need to exist.

Re:Google AMP Cache, AMP Lite, and the Need for Speed by fragmede on Thursday January 12, 2017 @11:55AM (#13383846)
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 (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?

Now, I'm visiting https://news.google.com/news/amp?caurl=htt%3A%2F%2Fwww.nbcne.... in order to get content from NBC News, while http://www.nbcnews.com works just fine. The writers of the article I'm reading are (ostensibly) hired by NBC news, not news.google.com, and there's no way to get to the same article on www.nbcnews.com unless I do something really awkward, like go back to Google and hunt and peck (I'm on my mobile phone, remember?) to type in "site:www.nbcnews.com article name".

I have hate for the UI of AMP itself (they broke scrolling down to get to the URL bar somehow), but that's also a distraction from the fundamental contract that AMP breaks.

Google would (rightly) get pissed if I made my own search page which "rebranded" Google search results to have my advertisement and then present the Google search results as coming from me; I hate them for doing the same thing to news publishers.

Re:Google AMP Cache, AMP Lite, and the Need for Speed by stuckagain on Thursday January 12, 2017 @01:03PM (#13384532)
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 nbcnews.com it renders in about seven seconds and doesn't finish loading for about 90 seconds, and then when it does I get a big popover survey/ad thing with a dismiss button that's too small to touch. The mobile experience on this site is far from fine.

Re:Google AMP Cache, AMP Lite, and the Need for Speed by detaro on Thursday January 12, 2017 @04:38PM (#13386356)
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.
Re:Google AMP Cache, AMP Lite, and the Need for Speed by davewasthere on Thursday January 12, 2017 @06:31PM (#13387120)
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 by detaro on Friday January 13, 2017 @03:55PM (#13394616)
Google could easily "motivate" them to provide AMP pages (as they have successfully done) without adding their own caching layer, which the complaints above mostly seemed to be about.
Re:Google AMP Cache, AMP Lite, and the Need for Speed by dandv on Thursday January 26, 2017 @06:59PM (#13496580)
This post explains very well the #1 benefit of AMP caches (yes, there can be more than Google's, and Cloudflare has just released their own cache): pre-rendering:

https://medium.com/@pbakaus/why-amp-caches-exist-cd7938da245...

Re:Google AMP Cache, AMP Lite, and the Need for Speed by bsimpson on Thursday January 12, 2017 @01:00PM (#13384498)
If browsers detected AMP pages and treated the address bar accordingly:

Cached from: nbcnews.com/some-article

Would you feel better about it?

Re:Google AMP Cache, AMP Lite, and the Need for Speed by msbarnett on Thursday January 12, 2017 @02:16PM (#13385191)
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 by ponderingthings on Thursday January 12, 2017 @04:11PM (#13386154)
SVG was Adobe's open implementation of the ideas of behind Macromedia Flash. It solved a real pain (the lack of vector support on the Web) and has been implemented by all the browsers. Does this upset you? Most of the progress of the web platform is sponsored by companies like Adobe and Google.

AMP is a curated subset of web functionality designed to load quickly and be safely cacheable. Like SVG, it's an open attempt to solve deficiencies in the platform. It's been sponsored by Google and adopted by a lot of their properties, but it's unfair to call it "Google's news product."

Re:Google AMP Cache, AMP Lite, and the Need for Speed by msbarnett on Thursday January 12, 2017 @05:11PM (#13386626)
SVGs are displayed whether or not they're hosted on Adobe's servers.

What other servers are serving AMP pages, (edit: and would benefit from this "cached from <other site>" URL bar display logic) other than Google's news product?

Re:Google AMP Cache, AMP Lite, and the Need for Speed by detaro on Thursday January 12, 2017 @05:12PM (#13386634)
All the publishers Google copies the AMP from? Google could just redirect mobile users to that if they wanted, as can every other site linking to a page. If they then also got rid of the requirement of loading the AMP JS from a CDN Google runs, they'd actually have something resembling an open standard...
Re:Google AMP Cache, AMP Lite, and the Need for Speed by msbarnett on Thursday January 12, 2017 @05:17PM (#13386674)
> All the publishers Google copies the AMP from?

But all of those URLs display correctly.

We're talking about having browsers add special-case logic in which some URLs on one particular special domain (news.google.com) belonging to one private company (Google) are treated and displayed differently than everything else on the internet.

> If they then also got rid of the requirement of loading the AMP JS from a CDN Google runs, they'd actually have something resembling an open standard

Sure, if this turned into an actual Open standard, and we were talking about extending browser display logic to any server on the internet that served an AMP page belonging to some other site, that would make sense.

But having browsers bless one company's subdomain with special rules that apply only to it is about as anti-open web as you can get.

Re:Google AMP Cache, AMP Lite, and the Need for Speed by detaro on Thursday January 12, 2017 @05:25PM (#13386728)
> But having browsers bless one company's subdomain with special rules that apply only to it is about as anti-open web as you can get.

I totally agree with you on that. They could easily get rid of their cache domain for serving AMP, or people could build browser extensions and other projects avoiding it while still using AMP, but only because all the publishers behind it already serve AMP if you ask for it. Which is why I made the point that it is not just Google serving it, which I clearly should have explained better.

Re:Google AMP Cache, AMP Lite, and the Need for Speed by tracker1 on Thursday January 12, 2017 @03:27PM (#13385789)
I would love that.. beyond that, a link that says "go to <website.com>" for that article, or some such, that would help too.

I have mixed feelings about it myself, as it isn't always obvious you're seeing content from website.com not google.

Re:Google AMP Cache, AMP Lite, and the Need for Speed by fixermark on Thursday January 12, 2017 @03:45PM (#13385949)
That link is often provided by the content providers (check bottom of page or under a dropdown menu).

It's annoying that its location isn't standardized.

Re:Google AMP Cache, AMP Lite, and the Need for Speed by monochromatic on Thursday January 12, 2017 @04:20PM (#13386221)
That would be far worse.
Re:Google AMP Cache, AMP Lite, and the Need for Speed by lostsock on Thursday January 12, 2017 @06:01PM (#13386967)
I just browsed to the first NBC news article I could find and at the bottom of the article was a big button saying "View full experience" which took me to the normal NBC website. I'm not sure I see the big deal?
Re:Google AMP Cache, AMP Lite, and the Need for Speed by Zelphyr on Thursday January 12, 2017 @02:00PM (#13385053)
> 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 by fixermark on Thursday January 12, 2017 @03:44PM (#13385945)
Why do you need to get to the same article on www.nbcnews.com ?
Re:Google AMP Cache, AMP Lite, and the Need for Speed by djeikyb on Thursday January 12, 2017 @04:35PM (#13386333)
So I can share a real link. Remove google's huge amp toolbar. Scroll normally. Have a correctly rendered page. Because I want content from the source, not google.
Re:Google AMP Cache, AMP Lite, and the Need for Speed by fixermark on Thursday January 12, 2017 @04:37PM (#13386354)
That seems an arbitrary desire based on an older-model of web surfing that still gets around a site by physically selecting and deleting pieces of the URL.

Lots of users don't operate that way. Caring about the URL is increasingly going in the direction of caring about the IP address.

I can share the link by tapping the "Share" option on the dropdown menu in my phone's browser. Works great.

Re:Google AMP Cache, AMP Lite, and the Need for Speed by djrogers on Thursday January 12, 2017 @12:38PM (#13384300)
If google thinks page bloat and loading speed are a problem, they could have come up with a set of recommendations (likely most of the ones in AMP) and use PageRank to promote websites that adhere to those standards.

Instead, they created a way to hijack the mobile web and become the de facto content presenter for any publisher who doesn't want to be punished by Google.

Re:Google AMP Cache, AMP Lite, and the Need for Speed by tiffanyh on Thursday January 12, 2017 @01:26PM (#13384746)
In case your not aware, since 2010 Google has in fact PageRanked higher faster web sites.

https://moz.com/blog/how-website-speed-actually-impacts-sear...

Re:Google AMP Cache, AMP Lite, and the Need for Speed by angry-hacker on Thursday January 12, 2017 @01:37PM (#13384856)
Which is exactly the point. Use it as a stronger signal and case closed. Web will change the way they want. Always. Right now they want to change it to their walled garden.
Re:Google AMP Cache, AMP Lite, and the Need for Speed by fixermark on Thursday January 12, 2017 @03:46PM (#13385952)
If they've been using it for six years, and it hasn't improved things, what makes you think using it as a stronger signal will (a) actually improve things, (b) not make it trivial to game SEO?
Re:Google AMP Cache, AMP Lite, and the Need for Speed by angry-hacker on Thursday January 12, 2017 @04:10PM (#13386143)
a) It would improve things because website owners, seo's or whatever you want to call them, always listen everything Google says. I'm in the industry. One tweet from Matt Cutts and they are already changing the brand name if Matt tells them so. That is the way industry works. Everyone knows site speed is a weak signal. Google could impose harsh penalties but they don't.

b) Google has become really smart nowadays. You could theoretically game everything in this world. They execute the javascript and run the page, they already know how to detect banners, interstatials etc. They also have manual team giving out bans.

Re:Google AMP Cache, AMP Lite, and the Need for Speed by mthoms on Thursday January 12, 2017 @05:35PM (#13386802)
> they've been using it for six years, and it hasn't improved things

Citation?

Re:Google AMP Cache, AMP Lite, and the Need for Speed by fixermark on Friday January 13, 2017 @09:09AM (#13390842)
On the six years or on the "hasn't improved things?"

The six years is the age of the speed PageRank signal, according to the grandparent post.

"Hasn't improved things," I had assumed 'the web is getting slower' was common knowledge, but here's an example of the family of articles you can quickly find on the subject: http://www.webperformancetoday.com/2015/07/08/news-sites-tak...

Re:Google AMP Cache, AMP Lite, and the Need for Speed by CaptSpify on Thursday January 12, 2017 @03:17PM (#13385709)
I'm not sure that they prioritize it enough. I've used this example elsewhere here but...

Here's a fast loading, well designed webpage: http://myfreeweather.com/

yet when I search for "weather", all of the results are slow, terribly designed sites. The above site is nowhere to be found. The same goes for other "common" sites like lyrics, etc.

Yes, the problem that AMP is trying to solve is real, they are just going about it in the opposite way that they should be.

Re:Google AMP Cache, AMP Lite, and the Need for Speed by greenspot on Thursday January 12, 2017 @11:09AM (#13383334)
> 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 loaded. This is a huge problem and yes, it needs to be solved. Just go to any news site and open Chrome Inspector's Networking tab, then you'll be shocked about the millions of resources still being loaded. AMP is solving this by putting Google as the gatekeeper in front of all this networks. I am ok with this, those ad networks created the problem and I am fine if they now need to deal with Google's monopoly but I am not fine with being restricted in using JS in general because you can do it right, even on mobile.

Re:Google AMP Cache, AMP Lite, and the Need for Speed by mtberatwork on Thursday January 12, 2017 @11:38AM (#13383650)
> This is not the problem.

It's certainly a large part of the problem. All this unnecessary offloading of processing to the client has gotten way out of hand. Why does a simple Wordpress blog (or any blog for that matter) that is essentially serving read-only pages need React in the first place? I have yet to see a blog that needs to be designed as an SPA.

Re:Google AMP Cache, AMP Lite, and the Need for Speed by tboyd47 on Thursday January 12, 2017 @03:11PM (#13385674)
Not sure why you're being downvoted. You're right. I'm not a fan of React and ilk myself, but they aren't the problem. Ad delivery technology is the problem, and Google itself is a huge part of that since they own so much of the ad industry.
Re:Google AMP Cache, AMP Lite, and the Need for Speed by tiffanyh on Thursday January 12, 2017 @11:33AM (#13383597)
>> "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/

Re:Google AMP Cache, AMP Lite, and the Need for Speed by objclxt on Thursday January 12, 2017 @12:12PM (#13384018)
That article is four years old. Facebook's app architecture has changed significantly since then, as has the speed at which JS can execute.
Re:Google AMP Cache, AMP Lite, and the Need for Speed by manmal on Thursday January 12, 2017 @04:58PM (#13386516)
Two more reasons why this comparison is not on point:

- On iOS, the FB App had to make do with a really slow JS engine at the time. IIRC Safari's JS performance was x5 compared to JS performance in apps' web views? This has more to do with how iOS treats apps, rather than how fast web pages in Safari are or were.

- The FB apps were okayish at the time, given that they were web based. If you manage to get your web app to that level, your site is ok. Now add to that the performance gains and browser optimizations of the last 4 years and you get a system that flies. Native apps are still faster and respond quicker to touch, but you cannot hold that against JS web apps.

Re:Google AMP Cache, AMP Lite, and the Need for Speed by iainmerrick on Thursday January 12, 2017 @01:13PM (#13384615)
That seems irrelevant here -- Facebook is a web app that needs you to log in, and displays user-specific info in a very dynamic way. It's not the kind of thing that could ever be cached, whether by Amp or any other generic CDN.
Re:Google AMP Cache, AMP Lite, and the Need for Speed by matthewmacleod on Thursday January 12, 2017 @12:46PM (#13384356)
That article's no longer relevant, and in any case the existence of a bad implementation does not mean that a good implementation is not possible.
Re:Google AMP Cache, AMP Lite, and the Need for Speed by flukus on Thursday January 12, 2017 @06:49PM (#13387240)
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 by makmanalp on Thursday January 12, 2017 @11:13AM (#13383376)
Would this theoretically be solved by some HTTP 2 stuff?
Re:Google AMP Cache, AMP Lite, and the Need for Speed by pmlnr on Thursday January 12, 2017 @11:17AM (#13383414)
It's not Google's responsibility to fix the bloat. If something is painful, let it be painful; when they start losing visitors, they'll see something is off.

This is _not_ a solution and google should not be doing anything with this.

Re:Google AMP Cache, AMP Lite, and the Need for Speed by eeeeeeeeeeeee on Thursday January 12, 2017 @12:32PM (#13384247)
Sure, but Google can offer tooling and best practices to push people in a certain way, like they do with everything. The best way to encourage people to move to new technology on their own is to change the search algorithms to provide positive incentives to implement those changes. Look at SSL. A lot of people don't care about encryption, but they care about SEO improvements more.

Google's AMP policy has been aggressive and heavy-handed. You can appreciate the technology and Google's desire to make the web faster and disagree with how they are implementing it.

Re:Google AMP Cache, AMP Lite, and the Need for Speed by tracker1 on Thursday January 12, 2017 @03:31PM (#13385823)
They could easily heavily penalize any website delivering over 1mb of html + css + js, and have a bonus for being under 500/100/50kb total as part of their pagerank.

That would be a huge driver... if nobody with over 1mb of html+css+js would be in the top 5 results, period.

Re:Google AMP Cache, AMP Lite, and the Need for Speed by fixermark on Thursday January 12, 2017 @03:53PM (#13386007)
What you've described would be a pretty game-able SEO algorithm.
Re:Google AMP Cache, AMP Lite, and the Need for Speed by angry-hacker on Thursday January 12, 2017 @04:22PM (#13386232)
So is every Google's guideline, yet most fail to game them. Google is smart. And good people will follow the guidelines instead of testing if something can be gamed, majority of industry is afraid of Google and its guidelines.
Re:Google AMP Cache, AMP Lite, and the Need for Speed by tboyd47 on Thursday January 12, 2017 @02:53PM (#13385522)
Anecdotally, client-side bloat is mostly going to be ad tech -- not React & company. Since Google and Facebook have such a tight grip over ad tech these days, maybe a better fix than AMP would be encouraging server-side, rather than client-side, ad delivery.

Edit: In a way, AMP feels like a scheme by Google to force content providers to enforce the solution to a problem that Google created. They're trying to speed up the web with their right hand while slowing it down with their left.

Re:Google AMP Cache, AMP Lite, and the Need for Speed by monochromatic on Thursday January 12, 2017 @04:22PM (#13386230)
If the issue were really about page speed, google could penalize the rankings of slow sites. No need to shovel a broken, self-hosted version of the site onto me.
Re:Google AMP Cache, AMP Lite, and the Need for Speed by bryanrasmussen on Thursday January 12, 2017 @03:57PM (#13386037)
well then they could have announced that they were going to aggressively penalize sites that were too bloated and SEO would take of the rest.