It appears Safari implemented a special case. We'd prefer a more generic solution where browsers would share the canonical link by default, but this works for us.
We had that solution it was called 'the web'.
I'd prefer a more generic solution too: get rid of AMP.
It really isn't about what 'works for you' it is about what is good for Google versus what is good for the web.
If you want to incentivise not delivering multi-megabyte "experiences" to people, I could see a case for feeding page weight into the ranking algorithm. Then people would be less inclined to have tag managers loading tag managers loading a zillion random js trackers.
I have personally saved at least one decent laptop from landfill by installing uBlock Origin on it, and making the web usable again.
That would get rid of the cruft on the web in a heartbeat.
Every SEO consultant would suddenly have an actual job, playing code golf on CSS and HTML to deliver the content in the minimum number of bytes possible.
I mean, kinda, but not really. You have to cater to it specifically
But your average news page would weigh in roughly the same no matter what the source was. Assuming you'd strip out all the cruft.
For reference, I optimized my website a while ago and ended up with the average page being < 15K.
Try it, on any connection in normal use today it should load faster than you can blink.
Add a few pictures and it would still work quite comfortably.
Not all of them. For a trivial example, an in-depth article about a topic would be penalized more than a more epidermic one, because it would contain more text, graphs, etc.
> For reference, I optimized my website a while ago and ended up with the average page being < 15K.
I feel you, I absolutely hate that my website uses a bunch of stuff for almost no reason. 80 KB of CSS or 90 KB of font isn't awesome, and I started a project to provide information on how to create lighter websites (https://www.lightentheweb.com/, stalled a bit).
All I'm saying here, though, is that the solution is more nuanced than "heavier = lower". AMP is definitely not a step in the right direction, though. I wonder if Google could give sites that used a specific CSS file and no JS a bump, rather than loading things on their own domain.
But such trivial examples should be trivial to get right no? It's all about the relative weight of the various factors that determine the ranking and a 'lightweight' article could be recognized as such.
How do you recognize which is which?
Sounds like a publisher-assisted "readability view" would solve both problems, though. It would allow the user to view a "lighter" version of the page and search engines could just measure how large the "non-light" version is and penalize accordingly. I'm afraid that would incentivize the publisher to put ads and other crap in the "light" view, though.
You as the publisher/author have to implement an AMP page yourself and then alert Google of its existence.
A lot of the useless pages are 3 stories of scrolling through large images with very little text.
Also, "data" as in tables and small/vector charts isn't all that big.
Tell that to a photographer, designer, artist, illustrator, etc
I don't think that would be a good metric for relevance though and in most case, the total size isn't an issue. Which is why AMP is good, low file size when it's needed, full size when it's not.
For me, I'd given up on trying to browse the web on my smartphone until Firefox Focus came along. I realize Firefox for Android now allows extensions, but I still used it as a typical browser. I signed into my accounts, I had expectations for a personalized experience, etc. With Focus, it's just a quick visit to a site and then it disappears. I can find the information I want, quickly, yet again.
User here. I like AMP. At the end of the day, I want to read an article. Most of the time, Reader view works. But not always. AMP reliably and quickly renders legible web pages. This wouldn't be an issue if 90% of newspaper websites didn't look like they were designed by turnips.
If Google really wanted to improve the quality of the web they had excellent tools to achieve that: the weighing of the various elements that go into the ranking algo.
But instead they chose to do an end-run around all standards processes and to attempt to capture mobile content (which is an extremely valuable slice of all web traffic) at the expense of competition and the openness of the web.
And so you are now a very willing pawn in the endgame for the domination of the world wide web, which will eventually result in Google being the sole provider of your content by virtue of the web being consumed more and more through mobile devices.
If you're not concerned I totally understand, but maybe you should be.
Doesn't Google already do this ? There are unintended consequences to increasing speed's weight in search rankings. Principally, it disadvantages smaller players. (Also, the New York Times would consistently rank under Buzzfeed.)
> you are now a very willing pawn in the endgame for the domination of the world wide web
Most people get news from the walled gardens of Facebook and Twitter . The minority of us sharing links to newspaper articles probably also have direct relationships with publishers. For example, I read the New York Times, Washington Post, Economist, Bloomberg and other papers directly on their sites because I subscribe to their newsletters.
> maybe you should be [concerned]
Maybe, but I don't think so. The things I read about in the newspapers AMP gives me faster access to yield better (i.e. more serious and more actionable upon) avenues for my attention. In every context where AMP is a worry journalism's decline seems more important.
Well, assuming equal relevance yes. But the NYT is not exactly a small player and could easily up their game in the page speed department. Besides that you could slowly ramp up the weighing to give parties the time to adjust.
> Most people get news from the walled gardens of Facebook and Twitter .
And this is what worries Google. Their long term adversary is Facebook (not Twitter, at least, not nearly so much).
> The minority of us sharing links to newspaper articles probably have direct relationships with publishers.
Not necessarily. I use a variety of aggregators.
> For example, I read the New York Times, Washington Post, Economist, Bloomberg and other papers directly on their sites because I subscribe to their daily newsletters.
> The things I read about in the newspapers AMP gives me faster access to hand me better (i.e. more serious and more actionable upon) uses for my attention.
Yes, it's a very seductive proposition, and one that given Google's power in the marketplace they just might get away with. See also: Microsoft bundling their browser and tying it in at every level possible in to the OS and other abuses of monopoly power.
> In every case where AMP is a worry, journalism's general decline is more important.
But that's the same kind of argument that people use when India has news about their space program: Why don't they fix hunger first. It's possible to both worry about journalisms decline and monopoly power abuse on the web, especially when it concerns the distribution of news.
When I'm looking for news, I want the highest-quality source first. AMP gives everyone the option of going fast now while kinks are worked out back home.
(I should mention that my default search engine is Duck Duck Go. I usually !news (Google News), though, because I like Google's news results better.)
> it's a very seductive proposition, and one that given Google's power in the marketplace they just might get away with
They might. But a lot of things might happen. AMP makes good journalism more accessible. If Google abuses that privilege down the road, it's not like they're legally unassailable.
> It's possible to both worry about journalisms decline and monopoly power abuse on the web, especially when it concerns the distribution of news
Lecturing newspapers about why they should have had speedier websites went nowhere. Seeing that the same content produced more views through AMP got the message across.
I don't think the analogy to India's space program is accurate. Technological development lifts standards of living. There's a solid argument for doing both because each helps the other. Killing AMP and forcing to choose users between crappy websites and efficient walled gardens is counterproductive.
Well, no, you want the highest quality source first that loads fast. Otherwise you wouldn't care about AMP in the first place!
> AMP gives everyone the option of going fast now while kinks are worked out back home.
So, do you expect that Google will ever give up their stranglehold on the sites that use AMP once they are in?
In my experience such measures tend to become permanent fixtures with their own hooks embedded in the various fabrics making removing them hard to impossible once they have achieve critical mass. We may have already passed that point, in which case you can safely ignore me.
> They might. But a lot of things might happen. If AMP makes good journalism more accessible I'm all for it.
That's your privilege. I have yet to have a day where I could not read more news than I had time for so I'm not familiar with good journalism not being accessible but I concede that this may be your situation.
> If Google abuses that privilege down the road, it's not like they're legally unassailable.
Who will take that up? You? The EU? The publishers?
My guess is that once entrenched it will be impossible to get rid of, a parasitic element in the pipe between content producer and consumer.
> Lecturing newspapers about why they should have speedier websites went nowhere.
> Seeing that the same content produces more views through AMP, however, seems to have gotten the message across.
Well no, I still don't see news websites getting any faster. But they're already ridiculously fast, consider that 30 years ago you had to wait a full day to read the news and now you can read it in 10 seconds. It's great if that can be cut down to 0.01 second and I'm all for doing that and incentivizing those companies to do this but in the end it is their web property and the market should be allowed to sort this out rather than that a search engine monopolist that is already the gateway to almost all pages read on the web becomes the gatekeeper to our news.
> In the meantime, Google's cash flows get to subsidize this IT expenditure for the news industry while consumers get faster news sooner.
No, Google's cash flow will not subsidize this because they now have the eyeballs. Sooner or later there will be a push for monetization.
> Killing AMP and forcing to choose users between crappy websites and efficient walled gardens, however, is counterproductive.
There are other choices besides.
AMP isn't forcing me to read fast newspaper A over slow newspaper B. It's letting me read slow newspaper B fast. I've never clicked on an AMP link for a source I didn't know.
> In my experience such measures tend to become permanent fixtures...Who will take that up? You? The EU?
You made an analogy to Microsoft bundling browsers earlier.
> I still don't see news websites getting any faster
They are .
> [websites are] already ridiculously fast
That's your preference. Mine is for them to be faster.
> Google's cash flow will not subsidize this because they now have the eyeballs. Sooner or later there will be a push for monetization
AMP is open source. If we'd gone the penalise-slow-pages route, every newspaper would have had to "roll their own" AMP in house. Even if Google throws a tax on later, readers got fast pages sooner and publishers got free code.
> There are other choices besides [crappy websites and efficient walled gardens]
In theory. In reality, that's the battleground.
That's called HTML. Nothing special.
Maybe if you're using the Trump definition of fast...
True. But I do care what tech makes the magic happen and the consolidation of the web into a very small number of silos is a dangerous development for many reasons and AMP is one plank in that consolidation game.
> Google is actually in a position to fix the problem and why not let them benefit while at it?
Because their stated reasons for AMP do not align with the implementation details, AMP grabs way too much control for a simple improvement in speed.
And to give credit where it's due, I'm glad you do. While we disagree on this point, I have a great deal of respect for your comments and found our discussion enjoyable.
Your analogy may be reasonably apt, but if so, it shouldn't make anyone who makes their living thinking about systems sanguine.
It does turn out many consumers will trade ownership for convenience. Particularly if convenience comes at a fraction of a cost. Meanwhile, there are side effects: the people actually creating the product (recorded music) get paid a vanishing fraction of what they used to. That changes the economics of actually producing recorded music, shifting the ability to do it to people who can get their money elsewhere. Some people like to try and obfuscate that reality with talk of "new business models" and "innovation," but it all boils down to the assertion that people who make recorded music should have to do another job in order to provide cloud record collections like Spotify to a consumer for the cheapest price possible.
The consumer, as you've pointed out, doesn't want to think about this. Whether they think about it or not, it will shape what kind of music gets produced and by who, so perhaps they should think about it, even if the incentives are more long term and non-obvious.
Buuut even assuming they don't care to do that... it doesn't mean that people who do care to think about how that affects the industry don't have every right to "moan about the philosophy."
Same goes for AMP. Solutions like AMP will absolutely have second order effects. Many users don't care to think about them. Doesn't mean they won't be subject to those effects, that those effects are just about philosophy, and it surely doesn't mean that people who are interested in them have any obligation to stay quiet.
And of all the things to actually have this really be something people waste time on. Working out the economics of production and distribution of music in a time when making copies is just short of free is at least actually a tricky problem. The idea that making mobile pages that load fast is a tricky problem that requires a Google engineering solution is utterly ludicrous.
This isn't about "philosophy." This is about systems and consequences. The consequences are real to the user whether they're aware of the chain that produced them or not.
> Yeah, artists may get paid less now, but Spotify and its ilk pretty much removed piracy from the vocabulary of regular consumers. Back in 2004, music piracy was just something you did
2004 is a poor point of comparison if what you want is to get the big picture or even just answer the narrow question of whether the choice really is between cut-rate cloud record collection services like Spotify or free-for-all piracy. 2003 is when the iTunes Music Store launches and 2004/2005 is when you really start to see the rise of digital music retail. Between then and the early 2010s you see those services become widely accepted (even embraced by non-technical people) as an alternative to piracy, and you see revenue from those retail services rise just fine without streaming. In fact, I've seen some reports that suggest that by 2012/2013 the profits from digital retail was on its way to the profits from physical formats.
So the choice wasn't necessarily between fiddly inconvenient piracy and butter smooth streaming experience.
And the battle doesn't even necessarily play out on the field of consumer choice, really. I mean, in a perfect world I might well expect enough consumers to recognize how they vote with the wallet will shape the world, that when we value McDonalds the economy produces McJobs, that when your airfare dollars are ultimately decided by the lowest price you'll get a shitty airline experience.... but yeah, people don't. That's actually why it's more important for people who can see the consequences to discuss them, publicly, loudly, maybe even forcefully enough that product owners who can't see past their A/B testing (and may not even have arrived at the points where they understand the limits of that along with the value) might pay attention.
> My problem is that a lot of developer-type solutions exist in the Silicon Valley echo chamber and will never see adoption because they don't take into account the big picture....
We're concerned precisely because we see the big picture. Understanding that Google has the power to shape the landscape regardless of how that effects the value of the landscape as a whole doesn't mitigate the responsibility to talk about it, or imply that there's a missing larger picture.
> Google will do what they want to do and they're big enough to where if they lose a few million hardcore advocates in the process it's no skin off their nose.
If you're right, and we've reached the point where Google essentially no longer has management and engineering talent that cares to be a good steward of the web or no longer has the incentives to understand how AMP isn't, then that's a much heavier indictment of Google than most of AMP's opponents have leveled so far.
And that's even if you can get everyone to agree that weighing the different aspects of a change says it's an overall benefit.
Even if AMP pages would render 1000 times as fast it wouldn't matter, it would still be an abuse of power. The relationship between a reader and the source of their content should not be mediated by Google. What point is there in HTTPS everywhere campaigns and such if Google MITMs every news article you read? What point is there for a content provider to even have a website if Google will end up serving the content?
This is simply bad, the only upside is the speed gain and that is one that could be sorted out by the market with a gentle nudge from Google rather than by some kind of monopolistic end-game on their part.
What I don't understand is why they cache the page themselves, and make that the requested version.
It would seem like any cached page from a CDN would be just as quick.
If Google preloaded the page from a non-google server, there would be a few problems. The most important one is that it would violate the user's privacy. That server would have in it's logs a request from a user that didn't click on the article, and could intuit information about the user's searching behavior from that request.
Less importantly, without the page being served from Google's cache, there is no way to guarantee it's actually a valid AMP page. The only thing Google knows is that it was valid AMP the last time it was crawled, which could be days ago.
And a waste of bandwidth if the user never clicks.
That's one problem.
> without the page being served from Google's cache, there is no way to guarantee it's actually a valid AMP page
Yes there is. You can validate pages as AMP on any CDN. You just can't have any benefit unless they're hosted on Google CDN.
TL;dr AMP is 100% build on web tech. Pre-rendering achieves the performance but relies on history.pushState and iframes, which doesn't allow presenting a URL that is not on the same origin as the search page.
We think that the UX trade off in the URL is OK given the performance benefits. Given that it is a trade off we now have a bunch of projects to mitigate those trade offs. More coming soon, including lots of improvements to Safari. My team works directly on WebKit to fix bugs that affect AMP (but also the web as a whole, since AMP is just web tech).
Also, is someone working on a successor to AMP that doesn't break or try to replace the browser's own UI? Maybe something done at a lower level, maybe the HTTPS level? E.g., I could imagine something where the browser is informed that www.google.com is loading/proxying a web page on the user's behalf, and through some kind of verification system, it determines the website has given www.google.com permission to do so, and the browser UI updates itself to show the right address in the URL, etc. Maybe there's a better way to do all that, just one idea off the top of my head that seems infinitely better than AMP from a UX perspective.
Though it'd also be nice if you could get websites to make their actual main sites faster for everyone, maybe using a method like jacquesm suggested. That coupled with the low level proxying might be a nice alternative to what we have now.
This is not about technology. And whatever goal the AMP project states it has could have been achieved - and better - in other ways, such as the suggestion elsewhere in this thread to simply penalize page weight. If people wanted a consistent user interface across all websites they would have stuck with Videotext.
> TL;dr AMP is 100% build on web tech.
Yes, so was the search engine that put each result page in an iframe. Only difference was they didn't have a monopoly on search. And it does not make it right.
> Pre-rendering achieves the performance but relies on history.pushState and iframes, which doesn't allow presenting a URL that is not on the same origin as the search page.
Minor technical details, not relevant. If you feel the AMP discussion is going to be swayed by technical bits you're simply out of touch.
> We think that the UX trade off in the URL is OK given the performance benefits.
Who made you the deciders of what the UX of the web should look like? Stick to generating the best search results rather than trying to co-opt the entire web one little bit at the time and leave the UX to the browsers, it would seem you have enough input there already.
> Given that it is a trade off we now have a bunch of projects to mitigate those trade offs.
The only trade-off that will satisfy me is AMP dying off because websites will stop to support it. But as long as Google is strong-arming content providers to use AMP that won't happen. It is no longer fair play as far as Google is concerned. If it ever was.
> My team works directly on WebKit to fix bugs that affects AMP (but also the web as a whole, since AMP is just web tech).
Consider doing something more useful with your talents. For instance, fix the long standing issue with the SERPs that makes it impossible to cut-and-paste URLs pointing to PDFs.
* The post it's replying to admitted motives behind those critical of AMP to the discussion.
* The idea that page weight is a problem best solved by a solution like AMP is hostile enough to the principles the web is based on that it's hard to bar either motive or outright thoughtlessness from the discussion. Defenses on either front are also admissible.
As for the job insult: there are plenty of UI/UX issues that Google could fix tomorrow if they wanted but instead they chose to work on this abomination and on top of that caused a bunch of work for companies well outside the Google ecosystem just to make things work that weren't broken before. That's a very inefficient way to allocate one's resources even at the scale of Google.
Finally, DanG has written a lot about the 'principle of charity', it appears to me that you have done everything that you could in order to take the very least charitable view of my comment and then you attack me on that interpretation.
I care about the web, in a way that I don't care about much else (HN maybe), and any and all attempts to subvert it should - in my opinion, which you are free to ignore - be fought tooth and nail lest we lose what came at a pretty great price. If you're comfortable with walled gardens and with large corporations gobbling up more and more of the open web to put it behind their store fronts then that too is fine with me. But you're not going to shut me up on this subject, nor am I going to moderate my language because you feel I should. Take the tone as a measure of my feelings on the subject.
Yeah, this is really within the bounds of "civil discourse":
> Consider doing something more useful with your talents.
It's not like they're forcing you to click on the AMP results. When Chrome started experimenting with SPDY, one could have asked them "who made you the deciders of what the protocol for HTTP transfer should be?". Yet from the lessons learned from SPDY was born HTTP/2.
If I were only interested in results from Reuters (the top result in the previous search, which was AMP), <<trump on afghanistan reuters>> returns 3 "condensed" AMP results and a non-AMP result above the fold, followed by 8 non-AMP results.
I don't think you're going to get far though as you're obviously just "opinionated" and probably not "really interested" in the "technical discussion".
As long as "We know that most users love the experience" why deign to discuss it with the ones that don't?
I'm really curious to see where using AMP as a proxy speeds up the page, versus applying similar optimizations on origin server?
If it's a cached page (served from any normal CDN), and crafted with similar optimizations  wouldn't it be just as fast, without needing to do the URL redirection?
Even if it were difficult to convince developers to implement the changes, couldn't many of the optimizations could be rolled into a module like PageSpeed ?
 - https://medium.com/@cramforce/why-amp-is-fast-7d2ff1f48597
 - https://developers.google.com/speed/pagespeed/module/
Edit - Reformatted links; I forgot HN doesn't use Markdown.
Getting similar performance out of on-origin serving is a priority for us, but we aren't there yet. One challenge is to give it the same scale as the AMP cache.
Criticism of AMP certainly includes technical aspects, but most objections I encounter are ethical rather than technical.
Did Google explicitly consider ethical considerations when creating and launching AMP? If so, what did this process look like, and where could we find out more?
If not, isn't it time we expected ethical review to be part of significant changes in web infrastructure, the same way we would with significant changes in physical infrastructure?
Now that someone got rid of that it's suddenly an "ethical issue"?!
I cannot opt out of AMP if I use Google as my primary search engine. It's about market power.
The risk critics are concerned about here is a future where the internet no longer "belongs" to the people on it anymore, and despite the malicious nature of the abuses you named, they hardly represented that class of threat.
People here are opinionated about it, but users love it.
So, instead of actually using AMP, you could just follow the AMP guidelines and get most of the speed benefits with almost no downsides. But Google started prioritizing AMP pages in search results, so now there's a downside either way.
You can beat AMP's performance with hand-tuned optimizations. Its goal is to uplift performance across a significant percentage of web content (instead of just that developed by the few experts).
Is Google going to penalize my sites if we don't use it? No, AMP is not a ranking factor.
We don't include advertising in our pages, so should we care about AMP?
Advertising is to AMP like Advertising is to the Web. E-commerce is a big use case where advertising is uncommon.
I understand that AMP is not a ranking factor (except for its inherent speed, perhaps). However, is there not a carousal at the top of SERPs for pages in your AMP Cache?
So while not an organic ranking factor, it would still affect SEO. Is that a fair comment? Or am I missing another perspective?
As far as I see it, Google sees this as valuable to their interests, and have made clear what the talking points are and what should and should not be responded to. That's the only reason I can think of for this counter argument to be continually ignored by him.
In fact all the people here are users. Funny how that works.
I’d prefer hosting all JS locally. (Or at least within of EU jurisdiction, as Privacy Shield is likely going to fall in the courts, too, as Safe Harbor did before, and I don't want to end up liable for that (and I don't want to sell out my users to some foreign tracking company))
So I'm not sure whether AMP is just something controversial as a lot of things from Google tend to be it seems, or if there is some real technical merit as to why it's so bad apparently.
So basically the argument boils down to "because I have shit internet, everyone else should suffer too".
I'm astounded at how much better it is than the last time I tried it.
Switched to it in Chrome a few weeks ago and don't miss Google. Which is shocking to me.
It's been successfully bringing me the correct stackoverflow results I would expect when I need to search.
Plus, I'm really starting to like the bangs, which allow you to search language-specific docs directly without any setup.
For example, if you use a U2F key, you need an extension for that to work - and that extension doesn't work with FF 57. I honestly don't remember the last time something broke with Chrome.
Or smaller things, like the fact that I can't use the keyboard to manage bookmarks (in FF on macOS, backspace doesn't delete bookmarks).
But the worst is in FF, Ctrl+Shift+N isn't new incognito window, it's restore the previous window. Years of muscle memory don't go away overnight.
Firefox is an interesting choice but the Chrome plugin ecosystem seems much more complete for me than Firefox has today.
It'll be interesting to see what happens in the space. I was a Mozilla user, then Firefox and now Chrome user. I have no issue going to better platforms.
I've been trying to use DDG more, unfortunately I'm not so impressed. Quite often end up researching for Google.
Hello. Sorry, but I have to express my deep disgust for what you do. "Give us your content and we'll rank you higher' is the opposite of what made the web and Google awesome.
If you care about user experience, downrank pages based on CPU usage, Memory usage, number of tcp/ip connections, number of domains connected, number of ips connected, number of bytes transferred, percentage of time that the UI is non-responsive and so on.
Trying to force the web into your little AMP cage is a terrible idea. It's the Facebook way of doing things. Are you really so afraid that you have to join the crooks? Would you have managed to take such a big part of the pie from Microsoft if you had been afraid of them and played their game?
Don't fight oppression with oppression. Fight it with freedom. Get rid of that AMP crap.
The only problem I have with AMP is that (google search) users can't turn it off. Me - I love AMP. You would love it too if you had to browse the internet on shitty third-world 3G connections(if you're lucky! Otherwise you're stuck on EDGE or GPRS). Not all CDNs are equal when browsing from less developed countries.
AMP is great for the next billion internet users, not so much for the HN crowd who don't mind multi-MB page loads without worrying about timeouts. Google should make AMP opt-out so that those who can afford to turn it off have the choice.
Purely from the reach it can potentially have if everyone does start using is great. Everybody is already optimizing so that they get crawled by Google, better faster and more efficiently. This is the logical next step.
From a ranking perspective, I think it's important that the HN community stops thinking just in terms of geographical metrics. Yes, in the US, UK etc where our offices are it gets blotched. But our next users are not going to be there from these countries. If at all, being a PM for a global product here, tomorrow's users, paying or free will be from probably from a country where AMP users would be the most impressionable today.
You would love it too if you had to browse
the internet on shitty third-world 3G connections
There's more reason Google wants you to use AMP than "it makes the web faster!". That's just the sell. They REALLY want you to use it, enough that they don't want you turn it off. Maybe something to do with protecting ad revenue?
I heard that AMP was developed by people connected to the search team. And search team is probably another name for "AdWords cash cow team"
It's worth noting that since your comment was made, the idea "AMP use leads to better search rankings" is now directly contradicted by the TL of AMP (cramforce) in a comment this thread .
Also, FWIW, I don't have any issue with AMP as a technology, but I have a big issue with how AMP cache is used by Google.
So AMP at the very least indirectly impacts rankings (and thus impacts rankings), and it may directly impact the ability to appear in the carousel (which impacts rankings).
Would love for him to refute this, but I suspect that won't happen.
Note how over time more and more of the things that Google used to simply point to are served by Google directly. AMP is just another element in that strategy.
We did add the link away from AMP, so that users who cared have a per-link opt out. We know that most users love the experience.
But haven't you seen the level of vitriol that comes up every time AMP is discussed? This isn't a minor thing, a lot of people REALLY dislike it. I have SERIOUSLY considered switching to a different search engine entirely because of this.
The fact that there is now a link to get to the normal page after I've already gotten to the AMP page is not a solution to the issue. As an end-user that feels like I'm complaining that her website is too hard to read because of the noisy background and you're telling me I could just use print preview where the background doesn't show and read it that way.
This feature has significantly change the way I use Google for the worse, and in the time since it was first launched it really hasn't gotten any better for me. It's so bad my OS vendor is starting to incorporate workarounds directly into their code.
If I Google something how do I open five tabs to go look at? I have to ignore every AMP result because I can't open them in a tab. So would Google deems to be the "best" content is now unavailable to me.
I don't have a choice to simply turn it off.
Not everyone will. If you read the comments here there are people who do like it.
But there are clearly a lot of us who HATE it with a passion because it's made your website so much harder to use.
PLEASE give me an option to turn it off.
> But there are clearly a lot of us who HATE it with a passion because it's made your website so much harder to use.
You really seem to overestimate the size of HN readership compared to the rest of the internet.
It is a minor thing. We are a niche audience living in a bubble. We're not - by far - the typical or target users. Our usage behavior is - mostly - irrelevant to Google.
The world has over 3 billion internet users. Let's say that HN has 3M unique monthly users, and that only 10% of those comment, and they are split between liking and hating AMP.
That gives you 150k people who hate AMP compared to 3 billion users on the internet.
Why would you build and maintain a feature for 0.005% of your users?
Even taking at face value the assumptions that yield your numbers (not obvious to me that's safe):
150K is still a pretty large audience.
It's an influential audience, to the extent that tech and therefore thinking about tech is influential.
It's an audience that understands the implications of technology choices like this and can articulate them.
Also, I don't understand the assumption that this audience is completely complementary when it comes to understanding how the rest of the population thinks. I expect it's at least as likely a bet that there are people in the rest of the population who sense something is off or some aspect of the experience is degraded but can't understand and articulate the issue at as high a resolution as it is likely that everyone in the rest of the population simple does not care.
And you really don't have to be some kind of programmer or other ubernerd to see some of the relevant issues in play with regards to URLs and walled gardens.
I know HN loves to think they're influential but I'd suggest than less than two handfuls of HN users actually have measurable influence outside of HN.
No, it's tiny. And considering how HN readers usually user adblock, and rarely click on ads, it is a completely irrelevant audience for Google.
But let's say you make $10 out of each user per year. That's $1.5M in yearly revenue. It barely pays for 3 employees at a large tech firm.
> It's an influential audience, to the extent that tech and therefore thinking about tech is influential.
>It's an audience that understands the implications of technology choices like this and can articulate them.
Considering how even HN readers are divided about AMP, I'd say that the net impact of HN audience on AMP is zero. We're not as influential outside the tech bubble as you think.
What if it was 10% of all users? Or maybe 20%?
Where would you draw the line… what percentage of users would have to dislike amp for you to think it was reasonable to add an option?
I'm not sure what number I would choose (ignoring my bias that I don't like it and therefore my number would be smaller than probably reasonable).
One easy piece of math is (cost of adding and maintaining that feature) vs. [(users who dislike) x (% of users who would quit you) x (profit per user)]
For example, if 10% of all users disliked it (300M users), but only 1% of those would leave your services (3M users) and you made, on average, $10 per user in profit, you'd be putting $30M/year of profit at risk, which is probably enough to hire a few people to build and maintain that feature.
Mostly on HN. And it's clear from this thread that a lot of vitriol comes from deeply ideological positions rather than real technical reasons. That won't be fixed by adding an opt-out.
My assumption is that the idea logical issue is much stronger here on hacker news than among the public at large. Much like views on free software purity.
My guess, for lack of better reasoning, is that the percentage of people on hacker news who hate the experience is roughly the same as those in the "real world". I wouldn't expect that being more technically inclined would make people more likely to like AMP or dislike it (ignoring idea logical issues).
I wrote a comment earlier about my experience with AMP from my perspective as purely a user. Please excuse some of the rantiness of it. Like i said, I can get a little frustrated with AMP at times.
You know that most users love the experience, or you know that most users take the path of least resistance and don't click away using a UI whose purpose isn't particularly clear yet?
How exactly do you know that?
Also, given that the indicator for an AMP page is a greyscale, hard to see icon and words, people who don't want to use AMP might hit it because they are in a hurry and the text they are looking at is black and noticeable.
Which means even less reason to trust you.
Google search basically is a function where you input a search string and it returns a list of URL's matching the search criteria. That's all I need and want it to do. AMP breaks the core behaviour of Google Search, it no longer provides a list of URL's that match my criteria. Basically most search results aren't actual search results anymore.
It's equally possible the majority of people just don't care. That doesn't mean they like AMP or would op-in to it given the choice.
While this is most certainly true, it doesn't mean that data retention and web ownership aren't values worth fighting for.
This whole discussion reminds me of the people ranting against RMS who many years later come to the conclusion that he probably was right all along only by then the horse has bolted.
The long term consequences of AMP are to consolidate Google's power and to make Google even more of an intermediary deciding who gets to see what. It's an end run around the kind of openness that is a cornerstone of the web and I care deeply about that openness and will oppose vocally any attempt to hijack the web for fig-leaf reasons.
Note how Google is slowly boiling the frog by doing all those things that they said they'd 'never do' and how their 'don't be evil' motto gets trotted out time and again to show us how they are good little web citizens when in fact they ram their unilateral solutions down our throats in the interest of their bottom line while pretending it is all about the 'user experience'. Accidentally gaining control over the content delivery of the pages containing advertising tags of competing ad networks sure must look like a nice and juicy bonus.
Borders and Toys'R'Us both decided to partner with Amazon for a while. I'm not sure why they thought that was a good idea, but that was their choice.
What I care about is the user experience. That's where I'd be happy with an option to simply disable it on my devices.
I think it's kind of unfortunate that it's not possible for people to discuss AMP without both issues coming up and confusing things. But that's life.
But forget all that, on a simpler level, if you do nothing most things stay the same. If you're happy with the status-quo, you're welcome to be silent. Others prefer vocal protest.
If the majority of users merely tolerate AMP... I wouldn't exactly call that a win for Google.
A Google engineer saying their users love their products is probably expected. They were probably fed this by some marketing/sales droid.
How do you achieve this with a non-AMP website? It sounds great.
Congratulations, you re-invented WAP and turned back the clock on the mobile web 20 years.
In terms of the AMP open source project governance rules I am THE tech lead.
I also manage a team at Google that works full time on the AMP open source projects and act as an overarching tech lead, but there are several sub teams that have specialized tech leads (e.g. for UI, ads, analytics, caching, etc.).
Is that what you wanted to know? :)
This is identical to the ranking boost given to Google Shopping (for which Google was just fined 3 billion EUR), so you can expect the same result.
Isn't it different because (presumably) the AMP links aren't owned by Google?
The fine was specifically for anti-competitive behavior, i.e. consistently surfacing their own links over those of shopping competitors, which at least with AMP links isn't necessarily the behavior, though there is likely some overlap there.
Google only gives the carousel position benefit to sites using the AMP js from Google's CDN.
If you use any other CDN, you don't get the benefit.
From a legal standpoint, this behavior is clearly different from their last slap on the wrist.
Google doesn't want the web to be fast or lean, it incentivizes you to create a fast version to be shown from google while the slow version is shown everywhere else.
Google: fast, everyone else: slow.
And amp positioning and ui display is absolutely a ranking boost.
No, everywhere else it's the normal speed your servers can deliver it to clients. Nothing about AMP is slowing down your normal web page.
The positioning and display are a ranking boost for whoever chooses to implement AMP pages - they are not explicitly targeted at Google services, which is the behavior the EU fined them for.
Anyone who thinks the EU is going to fine Google for AMP is actively avoiding reality at this point.
Faster and slower are relative terms.
> Nothing about AMP is slowing down your normal web page
Nothing about AMP is making the web faster, which it says it's doing on the project homepage. It's making a fork of the web to be shown on Google that is 'faster'.
> The AMP Project is an open-source initiative aiming to make the web better for all. The project enables the creation of websites and ads that are consistently fast, beautiful and high-performing across devices and distribution platforms.
I understand how it works and Your arguments so far aren't changing my mind.
Thanks for posting the homepage text, for posterity.
I believe there is research showing that little adornments like that convey trust and increase the CTR vs other listings that don't have them.
The easiest way to do the "more generic solution" is to remove that turd burger from search results. Interwebz fixed.
So, like regular webpage visits?
Now Google has forever(?) broken links in search results, in order to count click-throughs - so I suppose all browsers should special case that too...
I can't for the life of me figure out why they married an ok html/css/js subset (amp pages) with an absurdly invasive proxy technology.
I hear they say "speed", and "75%" - but if that's going from 130ms to 50ms complete page render does it really matter?
"we fucked up again web to wap level and now everyone needs to jump along because sharing is royally screwed"
I really wish some interdimensional telepathic Fart would Goodbye Moonmen this TL into abandoning AMP.
AMP has always worked poorly on iOS: it has different scrolling, it breaks reader mode, and it breaks status bar autohide and jump-to-top. Perhaps Apple would be less hostile to AMP if the implementation were better.
This never made sense to me.
You can have natural scrolling, an accurate reader view, a working back button and other highly performant features in a mobile-optimized HTML and CSS standard like AMP. In fact, you practically have to go out of your way to break these things in the way that AMP does.
Why does AMP have to suck so much?
When they do load, they fuckify the URL, so I can't copy/paste it normally. I know I can go in through the page's menus and get the real URL, but it makes it harder for no reason.
I consider the URL part of the page's UI, and commonly manually edit it. This makes it harder.
So far as I can see, there is no advantage to AMP pages, versus a fast and simple HTML page, with no external resource requests.
Sites can serve that themselves, rather than using Google.
In short, it breaks features I use, and doesn't provide advantages.
People who like it can't seem to understand that it has a crappy user experience for some people and always assume you don't like it for "philosophical reasons".
I really don't care about AMP from that POV, I just wish it was a secondary link instead of the stealth replacement of where I wanted to go with a page that usually doesn't load and messes up my back button.
> Why does AMP have to suck so much?
Because it violates every assumption on how browsers should work. I would prefer a slow browser I understand to a fast one I can't control.
My only real complaint about AMP is the scrolling - it doesn't feel natural and breaks shrinking the browser UI (I have an iPhone 5S, so screen real-estate is a premium).
They must have actually had to do work to override the expected behaviour and break the user experience, which I just don't get.
I don't understand why Google has to break these well-established UI conventions.
Down with AMP!
Actually, AMP pages had the most consistent scrolling with the rest of the system. It was 'regular' web pages that had the different scrolling
iOS 11 fixes that. All pages now scroll at the same 'speed' as the rest of the system.
This Apple action is done to honor the AMP teams design of how AMP URLs should be handled, so it's actually, in a sense, part of Google's efforts to improve the web, not a counter to them.
In this case that HAPPENS to align with what Google wants.
Of course google could've decided not to screw up the web in the first place… but we're obviously way past that.
I find Apple making AMP suck less for pay, to be much more likely than the Apple developers doing it because they think this is good for the web.
There will be no loss of trademark aspect, in law or effect, would Chrome be available in the edition provided by the Royal Institute of Engineers, or Firefox found in a edition created by the Chartered Institute of Management Accountants. US DoD AND PBS all have the place and reason to augment the capability of the FUNCTIONAL UTILITY of Web browsers. Google, Apple, Microsoft and the greater OSS diaspora, should be able to healthily play both the supporting role, and Arbiter of First Resort.
You do realize that Chrome and Firefox are open-source, right?
Mozilla has similarly and previously made their branding intentions clear.
I chose my example to convey the substance of a most respected voice in a profession, but there are thousands more.
These institutions have budgets and charters to assist their membership.
Browsers are perennially in need of support, financing and quality assurance.
I venture a dream in which out professional associations and not Google or Microsoft, are the recipient of our browsing data, and a world in which my browser use is assisted by the data that my associates have been winnowing for the answers that generally have been disappearing in my search results, since the early days of a WWW largely populated by academics and domain experts.
There is a awful lot which I believe other engineering professionals can contribute to the browser ecosystems and which as a byproduct may free us from the free no charge supply of the meta data that is often the actual result of considerable real work.
Consumers too, might be easily induced to pay a modest sum, to have a specific facility in plug in already installed and smoothly running, offered by one of the most respected bodies in the country.
Of course none of this is possible without the projects being open source. I am closer than my job title admits, to similar projects. I have also practice intellectual property law, in defence of my company and the rights which we also trade to creative works for clients who have had their work exploited and used commercial by companies beyond their ability to affect. Not now, but I will soon write up my litigation stories for public consumption. I have a awareness of the value placed on professional work and the way it affects often necessarily issues guarded and unwilling correspondents on possession of libraries which are essential to their profession, but must never be made freely available. The chance to be a member organisation with commit rights to the repositories, and the ability to control their own security audit is a very real consideration that might be very important progress indeed, as the meta data from closed libraries is invaluable for the use of search engines generally. The opportunity to use the latest software from a respected institution, who has their own additional security review process, for a token sum, like 5 pounds or 8 dollars, is something that I would like to buy, when I am selling to that sector.
I spoke above about branding.
And professional collaboration with financial support from highly respected engineering professionals in hundreds of comparable organisations, who are individually identified with the essential infrastructure of our built world and industry.
There incentive for organisations like these, to actively engage and support, possibly augmenting their distribution with a contribution to the projects of browser tools that assist the user in potentially specific ways such as archive cross reference private searches of the user's history and tabs, against closed or private libraries, which is a common service that is provided by associations in a physical form.
Firefox is losing XUL and this is upsetting a considerable number of people I speak to, who have developed in house assistant plug in software.
I am personally very disappointed with the depreciation and actually complete removal of XUL, and the initiative to port the superb microcosm of browser tools, really requires a very strong effort, which is the exact example of what the associations I spoke to privately whish they were able to make a genuine connection to the project maintainers, who universally respond to genuine inquiry with the exact reply which you just gave me.
I started my career 25 years ago and stayed in a very stop gap sales job, originally intended to fill a gap year before applying to university, because I was able to speak to serious company directors on a frank and open basis, from which I realised that I might gain no better experience in my education. Starting my own business was a natural step. The advertising trade newspapers claim every opportunity that online advertising is fully displacing print and the shrill claims have been proven empty for two decades now. This is a market that is unloved but vast in terms of the ability to address the most senior professionals in any known industry field. The economy is a incredible experience for untying the knot of misdirection that has turned the business of advertising agencies permanently away from their clients and completely to align their capabilities to sell, in funnelling the unsuspecting into unmeasured deals with above 60 percent of the cost, captured by integration of the so canute non real advertising "exchange" system, crippling opportunities for small business. The result is decimation of the small business economies of the USA and the UK.
Security of meta data.
Reuse of search and general browsing use recycled to make vertical market assisted tools for search and research annotation and collection.
Independent funding separated from conflicts of interest.
A new revenue stream for the project maintainers.
Improved oversight of security.
That's the most of the improvements I am seeking.
I wish AMP simply wasn't a thing, and they put more effort in promoting progressive web apps (PWA's) instead. There's too much tie-in to Google on the internet already.
AMP is basically "Hey, you suck at your job. Here's a subset of HTML/CSS that not even YOU can eff up."
PWA is "Hey, you suck at your job. Here's the industry's best practices for mobile-first development."
But people didn't, and here we are. Again, as a normal user, I'm relieved to see the AMP symbol. I click on those links first, to the exclusion of others given the chance, because multiple years of trust have been broken.
Maybe I'll rue the day I wrote this, but we're going to have to see. This is a self-created problem, and now publishers of all stripes will have to work to earn back the trust they poisoned.
Yes, it's possible to create fast mobile pages without AMP. So if that's true, why does AMP make such a big difference to so many consumers?
The bottom line is that the theoretical possibility of fast non-AMP pages is meaningless to consumers if few content providers actually act on that possibility. What matters is what happens in the real world.
Let/encourage developers (front-end and back-end) to optimise for performance and I'm sure we'd all see fantastic gains! All without needing to feed Google even more than we already do.
Google is a company, its motivation is profit. Did you really expect otherwise? Do you really think Facebook wants to "make the world more connected"?
Where do (or would) you put your savings? Let me guess, in the assets that provide the best return/risk? Why do you expect that the companies you're investing in expecting the highest returns would act in any different way?
Just because they can make a profit doing something doesn't mean they should be allowed to continue, especially if the mechanism of profit damages public or communal infrastructure/resources/etc.
Do you really want to sit by and let them ruin the web just because they can make money doing so?
Who's talking about consequences? I'm debating OP's point about "Google's (less than neutral) motivations/actions".
It is a private, for profit, company, why would anyone expect neutral "motivations". The motivation is profit.
I understand the usability case for AMP, but let's face it -- making a mobile-friendly web site really isn't that difficult, as long as you're not insisting on jamming things up with untold megabytes of JS woo. Google's argument to publishers is essentially "jam up your desktop sites with whatever JS woo you want, and let us unjam the mobile site for you." And, you know, fine, but to take advantage of it, you're essentially tailoring your web site to let Google reformat your content in a similar fashion to Safari Reader -- and, unlike Reader, Google is doing it by rehosting your content. They get the clicks, and you get whatever analytics and revenue they deign to share with you. And worse, that opens up the strong potential for Google's search results to penalize those of us who would rather maintain control over our own content.
You need to load the page first to do that.
1) iOS loads the full site, displays it in reader mode?
2) Some server (Apple's?) fetches the site, strips it down to reader mode, iOS fetches it from that server?
#1 requires downloading the full site. #2 is just using an old "reformat pages for mobile" proxy.
It's a hard problem.
Having everyone use Google as a proxy and content server, trusting them to deliver ads and so on, is one way to improve quality of service, but it's a way that's hostile to publishers and infringes on the privacy of users, so the industry absolutely hungry for a solution here.
A major issue is that Google acts as a gatekeeper for competing products, so we're unlikely to see any effect unless high profile publishers take a stand, or we individuals lobby our government to intercede.
> It's hard to be anti-AMP when the user experience is that much better with AMP.
I know. Ben Franklin warned us in a way about convenience, so his words seem quite appropriate here; I value my quality of life and my privacy, and I see it as such a slippery slope, so I don't implement AMP on my properties.
My organic Google traffic has admittedly suffered since the AMP logo program started, but focusing on making my sponsored search buy stickier has proven a lot more valuable to me fiscally, while allowing me to preserve my morality.
There are the publisher dynamics at play on a larger level, but the user experience is .... really good! Things are fast.
Perhaps someone should make some PaaS to help out all these publishers make fast AMP-ish pages, so they don't have to rely on Google to do it for them
Well, other places (including Bing) do the same thing with AMP caches, so even if it were only good or then cache operators, that wouldn't just be Google.
But, the speed is good, and whatever problems the client has on iOS, it's been great on Android, so as a user I mostly see it as a positive.
And it's got built in support for advertising and analytics and the cache operators end up handling much of the traffic, so it seems like a win for publishers, too.
So, I'm not sure who the “everyone else” that AMP is supposed to be bad for is.
It seems to me that AMP is so divisive on HN that whenever it comes up both sides continue to draw their battle lines and regurgitate the same arguments. Every AMP discussion I see on here is less of a conversation between sides and more of each side talking at each other. It seems to me there are 3 separate debates that end up getting all mixed together:
1. The user experience of AMP
2. The technical details of AMP
3. The concern about google abusing its market dominance in an anticompetitive way (or not, depending which side you fall on)
I'd like to add a bit of my own personal experience with AMP, focusing entirely on the first point of user experience. I'll admit that I have had a more negative experience with AMP.
The things I love about AMP:
- Like you said "the speed is good." AMP really has sped up the page load and rendering experience. Whatever technical details are used to accomplish this (caching, prefetch, etc?), it truly is noticeable to me how quickly AMP pages load.
- I have experienced website bloat issues for years, both on mobile and desktop. Whether it is images or text jumping around as a page loads or pop ups, banner images, and bloated ads that make the web page hard to use. Even though I have always heard discussions about how this should be fixed, AMP is actually achieving it.
The things I dislike:
The things I strongly dislike about AMP can be addressed through the other part of your comment
> whatever problems the client has on iOS, it's been great on Android
As an iOS user, the AMP experience has been horrible for me. It's not that AMP is 'bad' or 'unusable' on iOS, it's that AMP imposes its own UI rules that are jarring on iOS. Having regularly used other google apps on iOS (gmail, maps, calendar) it feels like AMP is another part of google's "material design is the one true way" mentality.
On an iPhone the system and third party apps are generally very consistent in the placement of menus, back buttons, share buttons, etc as well as what they look like and how they function. Likewise, the gestures and navigation follow some general patterns: pages scroll up and down; swiping right and left are forward and back motions. Headers and footers tend to auto hide when scrolling up and down. And so on.
In google apps on an iPhone you get the Android/Material Design version of things. Buttons have different shapes. The menu in google apps is the hamburger icon instead of a button that says 'menu' or 'options.' Likewise there is no 'done' or 'back' button, only an 'x' button. Pages don't scroll in google apps, and the vertical flow is nonexistent. Instead pages are flipped through by swiping left and right, just like the android app drawer. For a great example of this compare google calendar app on iOS to the native iPhone calendar app.
On a web page those things don't matter. The browser's header (URL bar) and footer (navigation bar) autohide when scrolling. Give a good swipe left to go back a page in your browsing history. A good swipe right to go forward in your history. Even Firefox on iOS implements these same patterns. AMP manages to break those. It somehow prevents autohiding, so now I perpetually have safari's URL bar and navigation bar wasting space on my screen. AMP provides its own menu header bar as well. But it is wonky and auto hides or unhides at seemingly the slightest tap, jumping around and wasting more screen space. Likewise, once I am on an AMP page safari's swipe left and right gestures are broken. Swiping left doesn't being me back a page (back to the google search results); it brings me to new AMP page. Swiping right doesn't bring me forward a page in my browser history; it brings me to a new AMP page. My forward and backwards navigation gestures have been hijacked, thus trapping me in AMP-land until I explicitly tap safari's back button or the 'x' button on AMP's header bar. On top of that, the swipe gestures are incredibly sensitive on AMP compared to normal safari and iOS usage. Often I find myself scrolling down an AMP page not-quite-perfectly-vertically and accidentally jumping to a new article because I am so unused to the AMP-specific swipe sensitivity.
At least they finally added the ability to get the native article URL, which was infuriating when AMP first came on the scene and was a big complaint of mine in the past. And now Apple is implementing their fix for the share button with the URLs as well.
At the end of the day though, why can't I disable AMP? Why is there no way for me to click through to the native web page from the google search results? My experience as an iOS user with AMP pages has been overwhelmingly negative, but consistently from google and the AMP team I see some form of "well users overwhelmingly love it and it makes pages load faster." That's great. I don't love it though. I hate it. Please let me disable it, and please stop forcing AMP down my throat, breaking my browser's behavior in the process. Please stop imposing Material Design aesthetics within AMP. I am not browsing the web on through a google platform. Please stop trying to 'fix' that for me.
If I had a way to disable AMP I wouldn't feel so strongly negative about it. But instead I am left with the notion from google "AMP is good. See, users love it. You're wrong if you don't as well. Thus there's no need to disable it, ever."
Odd ones on HN might be, but HN readers are the odd ones in a mobile-only world.
I once put an ad on AdWords, and noticed that >90% of the views and clicks were on mobile. That's when it really hit me how different we are from the average user.
Nobody uses desktops or laptops for personal use anymore.
Google SERPs that contain a cribbed copy of the answer to your query rather than a link to that answer and so on. As long as you stay on Google's properties with their ads on that page.
I don't get the hostility towards AMP, or the outright obnoxiousness of people who are against it (the replies to someone who works on AMP are so uncharitable and hostile). There are downsides, and I do wish the alternative was simply a "HTMLite" that standardized many of the restrictions of AMP to stop it from being the tragedy of the commons that many publishers make it, but it's hardly the villain its held as.
> There are downsides, and I do wish the alternative was simply
A simple alternative would be public content caches; a meta tag that says "prefetch me" is a way for the publisher to tell sites it's okay to prefetch it and store the content in the content caches. I think trusting a google-run content-cache with no cookies would be easy for browser manufacturers to implement. It also wouldn't affect the user interface adversely.
A separate, unrelated program could be used for the "fast" logo that would require all/most content on public caches and pageload fired in under 0.5sec (or some other metric).
AMP is marketed as a pre-requisite for fast site loading, when in reality it's just one in many ways to achieve that. But with this ideology, Google prioritizes AMP pages because they must be the fastest, and they hijack the URLs on Mobile, again all in the name of Speed, but at what cost.
1) Click the AMP link in Google
2) See half the reddit thread comments, since AMP is a cached older version, I then need to click "View full comments" which gets me to the mobile reddit link I wanted in the first place
3) For some reason, links in AMP reddit dont let you open in a new window -- which I often want to do when reading comments inline and see someone post a link in a comment. Frustrating.
AMP cost me more time and effort than having just gone to the non-AMP link directly.
This is something Chrome has implemented, and they've asked other browser vendors to do too. You want AMP to load the page quickly on your first load, but for sharing, the canonical link is the best to give to people.
Apple isn't taking up the good fight against AMP. They're simply removing it from URLs when those are shared via the build-in "share" functionality.
99% of interactions with AMP pages will see no impact. It seems like it should be uncontroversial that it is preferable to use the canonical non-AMP URI when sharing, so as to invoke content-negotiation between that page and the devise of whoever clicks on the shared link.
We are all mad that this is necessary in the first place. Apple is modifying their OS to fix something that Google shoved on people without any option to disable it or thought to the secondary effects of its existence.
<link rel="canonical" href="http://www.cnn.com/2017/08/23/politics/trumps-ire-at-aides-advice/index.html">
Apple is just following AMP's request.
Apple _is_ routing people back to the main road, not because of Google's suggesting it, but because it's the only reasonable thing to do.
The implication of your comment is that if Google has asked Apple to pass on the AMP links that they would do so, which I highly doubt.
A far more appropriate summary is: Apple is acting to correct Google's interference with web links; irrespective of Google's desires.
That this wasn't "Apple standing up to AMP" as the commenters claimed.
Apple is just following AMP's policy.
I would switch back immediately, if I could disable AMP on my google account.
AOL used to break lots of sites/graphics/scripts which noone would put up with today, AMP just makes you use and run everything through Google or else. This is a move to control more of the web through a walled garden and goes against the distributed nature of the web.
The one thing that AMP may be beneficial for is archival purposes, preserving content past when another source may keep it. However, knowing Google products and how they are killed off like George R.R. Martin characters, no hope for that.
1. If a site downloads more than 100K, halt the page load or display a "too much data" error.
2. If a site takes more than 1 second to render, halt the page load or display a "too long to load" error.
Do that for a few days and maybe these absurd sites would lose enough views that they might actually bother to figure out where their data is going.
I recently had to browse with "data roaming" at the low low price of $2.05 per MEGAbyte and had to disable pretty much everything on my phone within minutes.
I don't use Twitter, but other people do, and when they share a link to me I'd like to be able to 1) see what I am clicking on, and 2) avoid sending analytics information to Twitter when I do so.
Apple already has my money, they focus 110% on making my life easier and their products fantastic. Go Apple!
In iOS 11 you're able to default certain domains to always open in reader mode so you don't even need to download all that crap.
I doubt that.
The only pages that get improved by AMP are those that abuse AMP then again anyway.
Re: Abuse of AMP. AMP places sane restrictions on pages https://www.ampproject.org/docs/reference/spec#html-tags including hard limits on CSS size, etc... Google enforces these restrictions for pages served through their servers.
This is a much much needed effort to take the publishers toys away given they've proven they cannot be trusted with the full feature set of the web without adult supervision.
You mean TV channels? The ones that all look the same? The ones run by Sinclair broadcasting which will soon be able to control 76% of them?
There seem to be very few true local companies left, the ones around pretend to be local when in fact they're identical to every other one owned by their national parent company.
And that company can afford to do it right. They're rich. They don't need Google to do it for them
In that case not sure what their excuse is but my point still holds true: Their sites are almost universally godawful and they're demonstrably not able to be trusted with the full feature set of the web. AMP provides some sanity including things like hard limits on the size of CSS.
On a related note, anyone know an extension for desktop Chrome that converts AMP pages to non-AMP pages? Or is that not programmatically possible?
I hate that amp crap! It's the main reason for moving to ddg.
Google should appreciate the ad revenue from linking to your valuable content. Don't give Google more control over your content.
If Apple would stick to just making great hardware and products and follow the standards like other vendors do then I feel like the whole tech world would be better off.
Edit: Apparently I need to spell out in more detail my arguments because if read at surface level people only focus on AMP. This isn't about AMP. This is about sharing a link to something you are viewing. You are currently viewing the AMP page and that might look a certain way or even contain a certain type of graph that looks a certain way because it's static and fast to load. If you click Share and send this to a friend they will receive an entirely different page that might look different than what you were seeing. I don't think it's a good thing that we can no longer trust sharing a page with someone else. Now the ultimate destination is being edited behind the scenes without you knowing. It's a slippery slope that, like other things Apple has done, have possibly bad consequences in the future. The road to Hell is paved with good intentions after all.
It's a classic walled garden, like the Android app store. You can develop Android apps that don't meet their guidelines but you can't distribute them through normal channels.
But I believe the larger issue is how it makes URL meaningless, and futures a centralisation of the web. It's not against the standard, but certainly the spirit of the web as it was supposed to be.
The part that mandates including js from a corporation on your pages.
Edit: clarified about AMP usage and Google's involvement.
Google and Micorosft (Bing) have caches. I think Twitter does to (they definitely use AMP). Lots of other social media and other platforms use and highlight AMP content, and I think there are a couple other big players with caches, too.
It's definitely not just Google.
I can’t even use the JS from a local CDN.
In this case Apple is literally helping you and publishers not get screwed. I think you need to read up on AMP, because seeing the words 'standard technologies' and 'AMP' in the same comment in that way is extremely awkward.
I'm not getting screwed by AMP, and neither, AFAICT, are publishers.
I don't like how Apple unilaterally changes the way that things work (even if that means AMP) without regard to any other parties.
They have the biggest search engine by far. They have the most popular mobile OS by far.
But it's Apple you're mad at?
You can use exactly the same arguement you made against AMP, I don't see negating AMP as some great evil.
 or more charitably appealing to a subset of users at high cost to a non-trivial fractions of other users
So the issue isn't that you haven't spelled out your argument in proper detail, but that you're just incorrect.