No to Chrome • Hacker News Board

Re: No to Chrome

#131

Post by Karunamon » Fri, Dec 06, 2019, 2:27 PM UTC

jakelazaroff wrote: post #109

tyingq wrote: post #19

Earlier quoted context omitted.

Their apis only support declarative static blocking lists. No heuristics, right click to block, IAB ad size detection, etc. Similar to what chrome plans to do with manifest v3. Advertisers are already figuring out how to get around that. CNAME cloacking, proxying with same domain, etc.

But on the other hand, it prevents malicious extensions from exfiltrating your browsing data.

A powered off computer is completely unhackable.

This idea of removing usability in the name of safety has gone way, way too far. It was crap when Mozilla did it, it's crap when Apple does it.

Re: No to Chrome

#132

Post by dewey » Fri, Dec 06, 2019, 2:27 PM UTC

Qwertystop wrote: post #118

dewey wrote: post #73

Earlier quoted context omitted.

People also only used to stay in their villages or neighbourhood and don't travel as much as they do these days. It's a different world and just because we got by with sailing the oceans and using star navigation doesn't mean we can't use modern technology to improve our lives.

You've skipped a rather large period of time in which people would travel, and would bring a map with them or buy one when they got there. You think road trips only got to be a thing after Mapquest?

It was obviously an exaggeration but maps are just an iterative improvement until we landed (for now) GPS enabled devices, in the future we'll maybe have it embedded in our glasses, eyes or brain. I didn't say that we could only start traveling or doing road trips once we invented smartphones.

Re: No to Chrome

#133

Post by MichaelConlon » Fri, Dec 06, 2019, 2:28 PM UTC

FussyZeus wrote: post #108

S_A_P wrote: post #56

Earlier quoted context omitted.

More specifically, they blocked extensions that work a certain way. The deal breaker for me was when uBlock origin was no longer able to run. I immediately switched to Firefox and Brave.

I have uBlock running on Safari...? Newest version. Or is uBlock not the same as uBlock origin?

They are not the same product[1].

uBlock was the original tool but was handed over to another maintainer some time ago. The original developer of uBlock, being unhappy with the direction of the tool, forked the repo and made uBlock Origin which he maintains and is often considered the better product by people here

[1]https://ublock.org/faq/

Re: No to Chrome

#134

Post by rusk » Fri, Dec 06, 2019, 2:31 PM UTC

jefftk wrote: post #94

Braggadocious wrote: post #85

Earlier quoted context omitted.

it's literally the same engine as chrome. the only reason i use chrome is for the dev tools.

Firefox uses the Gecko engine, while Chrome uses Blink. The engines don't even have a shared ancestor.

“Originally” if I recall correctly, Chrome was a fork of firefox right? That is a long time ago though!

Re: No to Chrome

#135

Post by tenacious_tuna » Fri, Dec 06, 2019, 2:32 PM UTC

PretzelFisch wrote: post #129

Is it better to push people to firefox and safari or include Opera and Edge as well so we don't get another defacto standard?

Part of the issue is that most browsers other than Firefox at this point use the Chromium engine [0]. Using a browser that uses a different engine from Firefox and Chromiums would be most ideal, since that would put even more value on the use of the real standards, and not what the market leader implements.

[0] https://en.wikipedia.org/wiki/Chromium_(web_browser)#Browser...

Re: No to Chrome

#136

Post by dredmorbius » Fri, Dec 06, 2019, 2:32 PM UTC

ken wrote: post #70

mc32 wrote: post #46

Earlier quoted context omitted.

People need wayfinding regardless of how you get around.

Why? We did just fine without it up until a couple years ago.

It's getting harder (though not fully impossible) to find maps.

Where you used to find a stand with local maps in most fueling stations, you don't.

I'm looking at AAA's Map Gallery page trying to figure out if they offer paper maps any more. What's on offer are PDFs for online viewing or printing.

I'm someone who's got several atlases, globes, and piles of paper maps, as well as highway atlases and other paper-based navigational aids. I know how to use them. I prefer them.

They're simply not availabe as they were a decade ago (and for decades before that). And may well not exist in another ten years, except through extraordinary effort.

The "it's just an option" argument works until it doesn't. At which point it's not only not helpful, but not true.

Re: No to Chrome

#137

Post by oefrha » Fri, Dec 06, 2019, 2:32 PM UTC

azdv wrote: post #76

Interesting, I just moved back to Firefox after many years of using Chrome. I have to admit, it has gotten a lot faster recently, Firefox sync is working very well, and the Firefox Android app is a pleasure to use (being able to install uBlock origin is a huge plus). Anything else I missed on Chrome was easily solved by an addon, or a small tweak on userChrome.css (customizing the browser interface by overriding its…

I can’t solve highlighting search results in the scroll bar, and apparently I search a surprising amount and am absolutely crippled without scroll bar highlighting, so I’ll stick to Chrome until I can’t (e.g. when content blocking is crippled).

Re: No to Chrome

#138

Post by err4nt » Fri, Dec 06, 2019, 2:32 PM UTC

PretzelFisch wrote: post #129

Is it better to push people to firefox and safari or include Opera and Edge as well so we don't get another defacto standard?

Blink based users (Chrome, new Edge) are 2/3 users.

WebKit based users (Safari, GNOME Web) are 1/10 users.

Gecko based users (Firefox) are 1/25 users.

Opera and Edge are neglible slivers of Blink's market share. IE and old Edge are dead.

Re: No to Chrome

#139

Post by jeegsy » Fri, Dec 06, 2019, 2:33 PM UTC

azdv wrote: post #76

Interesting, I just moved back to Firefox after many years of using Chrome. I have to admit, it has gotten a lot faster recently, Firefox sync is working very well, and the Firefox Android app is a pleasure to use (being able to install uBlock origin is a huge plus). Anything else I missed on Chrome was easily solved by an addon, or a small tweak on userChrome.css (customizing the browser interface by overriding its…

Has firefox solved its long standing issue with the rendering of radio buttons?

Re: No to Chrome

#140

Post by msla » Fri, Dec 06, 2019, 2:34 PM UTC

rusk wrote: post #134

jefftk wrote: post #94

Earlier quoted context omitted.

Firefox uses the Gecko engine, while Chrome uses Blink. The engines don't even have a shared ancestor.

“Originally” if I recall correctly, Chrome was a fork of firefox right? That is a long time ago though!

Chrome was never a fork of Firefox.

If anything, it was a fork of Konqueror.