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.
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.
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.
https://medium.com/@pbakaus/why-amp-caches-exist-cd7938da245...
Cached from: nbcnews.com/some-article
Would you feel better about it?
The entire idea is insane. Google is just another company on the internet, and should be treated like any other.
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."
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?
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.
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.
I have mixed feelings about it myself, as it isn't always obvious you're seeing content from website.com not google.
It's annoying that its location isn't standardized.
At the risk of getting off topic, the reincarnated Digg is actually pretty good.
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.
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.
https://moz.com/blog/how-website-speed-actually-impacts-sear...
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.
Citation?
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...
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.
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.
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.
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/
- 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.
This is _not_ a solution and google should not be doing anything with this.
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.
That would be a huge driver... if nobody with over 1mb of html+css+js would be in the top 5 results, period.
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.
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.