Live data from Hacker News

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

markosaric.com

161–170 of 570 posts

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

#161
> Just visiting a site with Firefox’s Enhanced Tracking Protection on makes a faster and less intrusive web. It’s a built-in blocker of intrusive ads and invisible scripts.

What am I missing here? I installed FireFox, set Enhanced Tracking Protection changed to "strict", and went to typical sites that track you (news sites). I still see third-party hits in the Developer Tools (e.g. facebook) and it says it blocked 0 trackers so far.

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

#162
post #20

Earlier quoted context omitted.

!bangs in DuckDuckGo enables you to do searches right on the destination website https://duckduckgo.com/bang

Why even ddg? Chrome and Firefox support this out of the box in the browsers.

Most importantly, DDG comes with a host of bangs, whereas firefox And I assume chrome as well) require some configuration. Secondarily, bangs work regardless of their position in your query. At least in Firefox, they must be the first word. Finally, I can use DDG with bangs from anyone's device, that I might not want to do any setup on.

I do primarily use bangs from Firefox's address/search uni-bar, so if they added bang support from there, I would start using that feature without changing my habits at all.

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

#163

Earlier quoted context omitted.

> Stop using chrome. Honestly, wtf?! Firefox is awesome. I do not use Chrome, but I don't think Firefox is awesome. While I use FF, partly for moral reasons, my experience is average and I saw many flaws and bugs. I prefer the features of Vivaldi, which is based on Chromium, but does not phone home to Google. > STOP USING google SEARCH! While my default search engine is Duck Duck Go, I don't recommend it to friends a…

> 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

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

#164

Earlier quoted context omitted.

> Stop using chrome. Honestly, wtf?! Firefox is awesome. I think plenty of people have found Mozilla to have made some poor decisions over the years. It feels as though you have to choose between two options that aren't great, so is there a point in switching? Take the add ons situation. At least on Chrome I can run my own add ons.

> I think plenty of people have found Mozilla to have made some poor decisions over the years. It kills me that someone would be pissed at Mozilla for adding pocket, Chrome comes with so many damn Google centric plugins, and one little useful utility you can remove is what makes you lose it over Firefox? Come on.

It kills me that you think Pocket is the poor decision everyone is talking about

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

#165

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…

DDG is worse than Google for me and totally useless for any searches in my native language. Firefox has 50% worse performance for me in WebGL applications. Media isn't also accelerated still on Linux. Where is the "awesomeness" in that? I really wish those caveats didn't exist for what I use daily.

Agree on ddg, for me it's fine since most of my searches are technical stuff, rest is !g

For Firefox, I don't see how these things matter in my use case. Admittedly I have no clue if any of the sites I use make use of webgl, but the overall speed and snappiness doesn't feel any different between the two browsers, and I use both on Linux.

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

#166

Earlier quoted context omitted.

> Stop using chrome. Honestly, wtf?! Firefox is awesome. I do not use Chrome, but I don't think Firefox is awesome. While I use FF, partly for moral reasons, my experience is average and I saw many flaws and bugs. I prefer the features of Vivaldi, which is based on Chromium, but does not phone home to Google. > STOP USING google SEARCH! While my default search engine is Duck Duck Go, I don't recommend it to friends a…

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

https://bugzilla.mozilla.org/show_bug.cgi?id=594876 - 9 years old

https://bugzilla.mozilla.org/show_bug.cgi?id=1210727 - 4 years old

https://bugzilla.mozilla.org/show_bug.cgi?id=1010527 - 6 years old

Not to mention the weird random full-blown crashes that occur when I try to use it that I can't reproduce, no point in opening an issue for those.

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

#167

Earlier quoted context omitted.

> Stop using chrome. Honestly, wtf?! Firefox is awesome. I do not use Chrome, but I don't think Firefox is awesome. While I use FF, partly for moral reasons, my experience is average and I saw many flaws and bugs. I prefer the features of Vivaldi, which is based on Chromium, but does not phone home to Google. > STOP USING google SEARCH! While my default search engine is Duck Duck Go, I don't recommend it to friends a…

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

Not OP, but here are a few simple ones I encountered that swayed me back the chrome:

1. When switching tabs (ctrl + tab), instead of simply moving there, it showed a menu. This means I need to use that tiny menu to decipher which tab I’m on, instead of the entire background.

2. When closing a full screen video playback using ctrl + w, it takes a few seconds of a black screen on Firefox vs instantaneous on chrome

3. When installing extensions, they don’t always have an icon on the top bar, this makes discovarability a pain

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

#168
I would like to point out that it is possible to have web pages that load faster than AMP. It has not been made easy but many publishers have figured out (in some cases publishers have web pages that load faster than their AMP ones...)

Take a look: https://webperf.xyz

I have a number of issues with AMP but I will just mention two:

1. If Google addressed how their ad system was being mis-used (and in many respects as-intended) that would have gone a long way to addressing webpage performance. Instead they pushed more work on the publisher to adopt yet another new format (add it to Facebook Instant Articles, Apple News JSON formats, Google News MediaRSS etc.)

2. AMP helped killed some early momentum to make pages faster. They sold a bandaid solution that was 'good enough' for management and undercut engineering efforts to address the root cause.

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

#169
post #50

Earlier quoted context omitted.

Serious question: what else those websites are supposed to do (that AMP does not provide) with all those megabytes of scripts? Newspapers display a text and an image and very rarely an interactive content(Election day maps and charts, mostly). Is there a reason FROM USERS PERSPECTIVE to have different website codebase for each publisher? For years the Web community kept creating new JavaScript libraries every day and…

from USERS PERSPECTIVE, amp is meh. yes it's faster, does it really matter if you re getting an article in 1 second when you -obviously- plan to spend 2 minutes reading it? i dont know anyone who thinks so, perhaps your USERS do > A strealined conent delivery platform prioritizing UX that the publishers failed to create what you re implying is, Google failed to improve their algorithms to bypass obvious SEOs, so they…

You clearly don't speak for the users in the developing world with bad connections. Speed is anything but irrelevant.

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

#170
post #153

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…

> Firefox is awesome. FF dev tools are awesome. FF, like Wu Tang, is for the kids. FF is awesome, but have they fixed the battery issues on Macs yet? It's a non-starter for me to switch.

Yea they fixed it:

- https://mozillagfx.wordpress.com/2019/10/22/dramatically-red...

- https://www.zdnet.com/article/upcoming-firefox-update-will-d...

Give it a go again!

Post reply on HN