Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How to fight back against Google AMP as a web user and a web developer

markosaric.com

Post reply on HN
Print view View original

221–230 of 570 posts

Re: How to fight back against Google AMP as a web user and a web developer

#221

Post by ogre_codes »

I'm not a fan of Google's proprietary web, but it's worth pointing out that this is largely a response to the increasingly shitty way publishers treat their users. Just reading basic articles on the web has become a painful exercise in dodging "Subscribe" faux-pop-ups; trying to scan text while your vision is bombarded with unrelated video; and user-hostile scroll capture effects.

For much the same reasons Google AMP is a thing, I use Apple News for most of my news reading. The web has overcome commercial broadcast television as being the shittiest way of consuming content.

Re: How to fight back against Google AMP as a web user and a web developer

#222

Post by tyingq »

bduerst wrote: post #212
tyingq wrote: post #105

Earlier quoted context omitted.

Google is capable of driving SERP and carousel position based on the performance of the site. They don't need AMP for that. AMP is very much about creating an semi-walled garden. Any performance benefit is the lovely exterior of the Trojan horse.

And has been. Look at how well that worked for mobile web.

Sorry, "has been" what?

You mean Google is using performance, in a meaningful way, to drive SERP and Carousel placement?

If so, I disagree. They talk about it. They don't do it in a way that drives behaviour. They could.

A significant drop plus a webmaster tools message that says why, would work.

Re: How to fight back against Google AMP as a web user and a web developer

#223

Post by undoware »

syshum wrote: post #152
brianzelip wrote: post #23

Here's one great takeaway: > Treat the cause: Third-party requests slow down the web > ... > - Google owns 7 of the top 10 most popular third-party calls > ... > So you can see why there must be some kind of internal struggle at Google. They understand the value of a faster web but they also cannot go after the main cause of the slow web. And this is how technology such as AMP gets invented and makes things worse. It…

While I agree we need to stop using chrome, I don't know that FF is the path forward. Mozilla's continued trend away from Openness and the foundation's original goals and more towards business objectives and corporate "morals" similar to those seen in google seems like we are just replacing one Corporate master for another with Modern Mozilla, inc Long gone are the days of the Mozilla Foundation standing up for the u…

[citation needed]

Re: How to fight back against Google AMP as a web user and a web developer

#224

Post by amatecha »

nkw wrote: post #163
elbrian wrote: post #126

Earlier quoted context omitted.

> I saw many flaws and bugs. Can you tell us about (or link us to) some of the many bugs you found in Firefox?

So I'm not the above poster, but for me the one that killed my workflow was this still-open, 17-year-old bug: https://bugzilla.mozilla.org/show_bug.cgi?id=195361

That's not really a bug - I'd say that's a product design choice. I'm surprised the ticket is still open, tbh.

Re: How to fight back against Google AMP as a web user and a web developer

#225

Post by [deleted] »

ilikehurdles wrote: post #37
nailer wrote: post #31

Earlier quoted context omitted.

> Stop using chrome. FF is great, but it's also worth pointing out that Edge has all the Google adware removed and better privacy. There was a post from Eric Lawrence detailing all the Google stuff they removed a little while back, it was about 25 separate components. There's telemetry though so make your own mind if you're cool with that.

Call me when Edge is on OS X or Linux (and ideally open-source, like Firefox). I imagine a lot of the hn userbase, myself included, doesn't rely on Windows for their day-to-day work.

[deleted]

Re: How to fight back against Google AMP as a web user and a web developer

#226

Post by kuschku »

darkwater wrote: post #183
nkw wrote: post #163

Earlier quoted context omitted.

So I'm not the above poster, but for me the one that killed my workflow was this still-open, 17-year-old bug: https://bugzilla.mozilla.org/show_bug.cgi?id=195361

And how on Earth is that a deal breaker? Selecting text from disabled fields?

a lot of websites assume that you’re using chrome and show content you have to copy in disabled text fields (with some styling applied)

Re: How to fight back against Google AMP as a web user and a web developer

#227

Post by dwild »

rland wrote: post #210

Imagine if Cox or Comcast came up with AMP. Same technology, same idea. If websites use the Comcast AMP framework, Comcast will cache their sites and make them faster for users. See, it's about the users! Because the Comcast AMP framework is open, and has nothing to do with the business interests of Comcast. Comcast will give a bit to open source and have a few conferences per year to make sure developers know that i…

> If websites use the Comcast AMP framework, Comcast will cache their sites and make them faster for users.

They probably do it with Netflix, some ISP do it with Steam too... there's nothing wrong with multilevel cache (except cache invalidation).

Re: How to fight back against Google AMP as a web user and a web developer

#228

Post by [deleted] »

brianzelip wrote: post #23

Here's one great takeaway: > Treat the cause: Third-party requests slow down the web > ... > - Google owns 7 of the top 10 most popular third-party calls > ... > So you can see why there must be some kind of internal struggle at Google. They understand the value of a faster web but they also cannot go after the main cause of the slow web. And this is how technology such as AMP gets invented and makes things worse. It…

[deleted]

Re: How to fight back against Google AMP as a web user and a web developer

#229

Post by criddell »

cletus wrote: post #192
brianzelip wrote: post #23

Here's one great takeaway: > Treat the cause: Third-party requests slow down the web > ... > - Google owns 7 of the top 10 most popular third-party calls > ... > So you can see why there must be some kind of internal struggle at Google. They understand the value of a faster web but they also cannot go after the main cause of the slow web. And this is how technology such as AMP gets invented and makes things worse. It…

> It blows my mind how many devs around here are devoted to their browser and search. Are they though? Or is AMP just a storm-in-a-teacup? There a handful of people on Earth that will stop using Google search (in particular) and Chrome as a protest against AMP. > ... and yet a MAJOR investment in all of our future. [citation needed] Personalized search is not inherently bad. Use Google search without being logged in…

> Use Google search without being logged in if you really care.

AFAIK, the search is still tailored to some degree. Log out and search for "plumber" and I bet you get local results.

Post reply on HN