News for hackers. Stuff that matters.

A comment on Fight back against Google AMP (2018). Parent comment

Re:Fight back against Google AMP (2018) by EpicEng on Wednesday December 04, 2019 @01:06PM (#21704940)
>and web developers are not against lean websites

Of course no one is _against_ good performance, but web devs obviously don't care enough to do anything about it. There's no practical difference between the two.

[ Parent | on HN ]
Re:Fight back against Google AMP (2018) by dessant on Wednesday December 04, 2019 @01:17PM (#21705116)
Most web developers do make fairly lean websites, but that is not enough when ads and a dozen tracking scripts which in part are supplied by Google are slapped over their work.
[ Parent | on HN ]
Re:Fight back against Google AMP (2018) by xvector on Wednesday December 04, 2019 @04:12PM (#21707051)
Which is completely 100% irrelevant from the end-user perspective.

Just to be clear, I hate AMP, but I also feel a sort of pleasurable vindication in the pain that developers and companies must now go through because of the horrendously slow trackers and ads they used to fill their pages with.

[ Parent | on HN ]
Re:Fight back against Google AMP (2018) by dessant on Wednesday December 04, 2019 @05:07PM (#21707736)
Google could restrict the content loaded in AdSense iframes and apply AMP restrictions to ad content only. They also have the means to limit the number of ads partners can load on a page, and restrict the overzealous use of Google Tag Manager which slows down sites.

Google offers both the poison and the antidote, and each of their solutions, see what they're doing with request blocking in Chrome, happens to erode user liberties and privacy rights to concentrate power around Google properties.

[ Parent | on HN ]
Re:Fight back against Google AMP (2018) by cameronbrown on Wednesday December 04, 2019 @02:30PM (#21706001)
It's a bad idea to just slap AdSense and analytics in a page. If they're a requirement then they need to be properly integrated and thought about. It can be done properly but nobody really does.

FYI Personal opinion not Google's.

[ Parent | on HN ]
Re:Fight back against Google AMP (2018) by e_proxus on Wednesday December 04, 2019 @01:18PM (#21705131)
Page rank would make them care. Can't understand why Google didn't just down rank heavy pages...
[ Parent | on HN ]
Re:Fight back against Google AMP (2018) by haroldp on Wednesday December 04, 2019 @03:12PM (#21706411)
It absolutely does. Improving your page speed (or google's idea of your page speed) is a critical step in optimizing a site's organic google search ranking.
[ Parent | on HN ]
Re:Fight back against Google AMP (2018) by e_proxus on Thursday December 05, 2019 @05:09AM (#21711196)
Which means AMP actually has very little to do with "performance".
[ Parent | on HN ]
Re:Fight back against Google AMP (2018) by silexia on Thursday December 05, 2019 @10:20AM (#21713006)
Why do people feel the need to "fight back against Google"? Should their actual fighting energy be going to fighting dictatorships around the world and torture by the CIA? Priorities are really messed up.
[ Parent | on HN ]
Re:Fight back against Google AMP (2018) by e_proxus on Friday December 06, 2019 @05:34AM (#21720596)
Why not both?
[ Parent | on HN ]
Re:Fight back against Google AMP (2018) by vile_wretch on Wednesday December 04, 2019 @01:41PM (#21705439)
Web devs care but efficiency is expensive and clients don't want to pay for it.
[ Parent | on HN ]
Re:Fight back against Google AMP (2018) by EpicEng on Wednesday December 04, 2019 @02:46PM (#21706149)
No it's not. We're not talking about squeezing every last ounce of performance out of the CPU and hand tuning every query. Just stop bloating your pages with 10,000 dependencies and awful JS frameworks and pretending everything needs to be a SPA.
[ Parent | on HN ]