4 ms·
> AMP does NOT outperform HTML5 unless the HTML5 page is horribly designed and ridiculously bloated. But that can be fixed without Google's help. And yet, noon
by izacus 10y ago
> AMP does NOT outperform HTML5 unless the HTML5 page is horribly designed and ridiculously bloated. But that can be fixed without Google's help.
And yet, noone cared enough to fix it until now. It's really really hard to sympathize with publishers when they brought this upon themselves by turning their pages into giant autoplaying video infested places.
- MBCook 10y agoIf that's all Google truly cared about they could've simply put a heavy penalty on Pages that rendered slow or presented garbage. Instead they invented their own thing which caused you to stay on Google sites using Google services to read other peoples content… and said they did it to speed things up. It feels like that was either justification after the fact or that was with the original engineer had in mind but was not the point of the project once it got approved. All those horrible infested pages? That's why I run an ad blockers, use RSS, and stopped reading a lot of sites. As every publisher got more and more aggressive other people were going to start doing it too. Eventually, I think it would've had an effect. This feels a lot more like when Birders (or was it B&N?) outsourced their web sales to Amazon. Remember how well that went? Outsourcing a key part of your experience to another company it's a bad idea, especially if they like being in control of everything.
- danso 10y ago> If that's all Google truly cared about they could've simply put a heavy penalty on Pages that rendered slow or presented garbage. There already is a penalty for slow-loading pages, but you make a good point that the penalty could be increased to the point where publishers would be forced to adapt accordingly. However, outside of the news ecosystem, that would end up penalizing a much larger base of content creators who don't have the means and infrastructure to handle this. To say that "well users who have good content should also get their shit together" rings a bit hollow, especially on HN, where technical/deep/interesting articles get upvoted to the front page only to crash from the traffic. If authors of those articles/sites can't do it, then it's a problem for most folks.
- MBCook 10y agoI understand. But I don't know what else I'd want google to do other than turning up the penalty a lot. If there are pages that have to load slow for some reason then hopefully they're good enough to overcome that penalty. Or maybe they could choose to apply it only to news sites? The problem is that Google took this in such and embrace-and-extend direction that seems to benefit them and give them a lot more power than they had before. And I already think Google is way too powerful. Their solution annoys me and creeps me out more than the problem did. By a large factor. I don't like them being so deeply involved at this kind of level. If they are going to do something, I can't think of something I would like for them to do other than just tuning the penalty.
- belorn 10y agoIf you increase the penalty you also increase the artifacts from measuring the speed. Should it measure first byte, content above the screen size (and which size then), or fully loaded site. What about lazy load which neither method represent when a site is usable, but rather at what point javascript takes over the responsibility to load the site. A small penalty devalues gaming the way google measure the speed.
- codedokode 10y agoThis penalty also can have negative consequences on image quality on websites. I had to worsen JPEG image quality to get good score for a website in Google's PageSpeed tools [1] because our management believes it affects search rankings. That tool is awful. I would never follow Google's recommendations on my own site. The compressed versions of images it suggests one should use have visible artifacts. [1] https://developers.google.com/speed/pagespeed/insights/ https://developers.google.com/speed/pagespeed/insights/
- codedokode 10y ago> However, outside of the news ecosystem, that would end up penalizing a much larger base of content creators who don't have the means and infrastructure to handle this. AMP does the same thing. Many sites don't have resources to convert their content to AMP pages and they will get worse positions in search results.
- ehsankia 10y agoExactly... Saying that it's "technically possible to fix all performance issues" is like saying that it's "technically possible to write your script in C instead of Python". Sure it is, but no one has been doing it and if it wasn't for AMP, it would've stayed a slow hell for users, if not getting even worse. If you've got a better suggestion to motivate all these news sites to spend thousands rewriting their website from scratch and optimizing it, go for it. But right now, this is the best we've got. It's not perfect, but it has actually been making huge strides in solving common issues over the past year.
- deleted 10y ago[deleted]
- MBCook 10y agoSee what I wrote here: https://news.ycombinator.com/item?id=14384560 https://news.ycombinator.com/item?id=14384560 You say it's been solving problems, but for me it's only been causing them. It's made it significantly harder to use Google search on iOS. Also the slow pages? Reader mode on safari has worked fantastically on them for years. Slow pages wasn't even a problem for me because of reader mode. Not only were they faster they were also easier to read because they didn't have crazy styling applied to them. I kind of wonder if this whole thing is an accidental android/iOS litmus test. People who use android don't seem to have problems with it because the experience sounds good there. That's NOT my experience using Mobile Safari. I have a literally considered switching my search engine over it. I've dug through all the Google account settings looking for a way to turn it off. If someone put some sort of content blocker in the App Store that would disable AMP? I buy it in a heartbeat.
- vesinisa 10y ago> It's made it significantly harder to use Google search on iOS. Works well enough on Android Chrome. Irony is, AMP, Android, Chrome and Google Search are all Alphabet (Google) products. I am personally all for platform portability, but certainly it's been Apple who have been pushing for One Closed Ecosystem since the introduction of iPhone, and Apple users have been very happy about it and playing down the vendor lock-in issue - some even as far as claiming it desirable that The One Benevolent Vendor control everything (note that real Chrome is not available on App Store simply because Apple has decided that iOS users should only use the Safari rendering engine!) Now that there's a shard in the walled garden, another player seemingly using the very same tactics as Apple, it's frustrating to see the same users complain about how much it sucks to be disenfranchised from modern computing because they use a different vendor - only this time Apple is the "other" vendor. Should Google succeed to marginalize iOS (assuming this is intentional and not just a bug in Safari), I bet many of these folks will soon be writing about how great it's that Google controls everything, how Material embodies the latest hip in UX and how the new Pixel has become so integral to their daily life.