Live data from Hacker News

uBlock Origin Maintainer on Chrome vs. Firefox WebExtensions

discourse.mozilla.org

11–20 of 340 posts

Re: uBlock Origin Maintainer on Chrome vs. Firefox WebExtensions

#11
post #3

Huh. These actually sound like good arguments to switch to Firefox, arguments I've never heard before until now.

I moved to firefox once 57 was released on nightly. Firefox is finally usable (in terms of speed) again and I can use it for day to day tasks.

I think I qualify as a poweruser by some standards, I tend to have 100's of tabs open and I've never left Firefox for speed reasons or others because it has held up extremely well over the years. My machine has a lot of RAM so maybe that's one reason things have been quick, and the main drive is an SSD. Is there anything specific about the 57 release that makes you feel caused the speed bottle-neck to disappear?

Re: uBlock Origin Maintainer on Chrome vs. Firefox WebExtensions

#12
post #9

I found this disturbing: "Chromium-based browsers are being “infested” by Instart Logic tech which works around blockers and worst, around browser privacy settings (they may start “infecting” Firefox eventually, but that is not happening now)." From his linked post: "Instart Logic will detect when the developer console opens, and cleanup everything then to hide what it does" Is this implemented via a CDN-delivered sc…

And he has a list of sites that use WebRTC to get around blocking. Didn't Firefox or someone say they'd reconsider auto-enabling WebRTC if this practise became widespread?

Re: uBlock Origin Maintainer on Chrome vs. Firefox WebExtensions

#13
post #5

> I am not aware of any anti-fingerprinting initiative taken up with Chromium Brave is Chromium-based and has anti-fingerprinting tech (which it was the first to include IIRC): https://github.com/brave/browser-laptop/wiki/Fingerprinting-... It also works on Brave for Android.

Unfortunately Brave doesn't have extensions and won't let you restore some settings from backup or transfer them to another PC, so it's not really a complete browser for most techies the way we think of Chrome and Firefox. Note that the settings loss thing is an issue (ehem "feature") with Chrome/Chromium itself and not specific to Brave on Windows builds.

Re: uBlock Origin Maintainer on Chrome vs. Firefox WebExtensions

#14
post #3

Earlier quoted context omitted.

I moved to firefox once 57 was released on nightly. Firefox is finally usable (in terms of speed) again and I can use it for day to day tasks.

I think I qualify as a poweruser by some standards, I tend to have 100's of tabs open and I've never left Firefox for speed reasons or others because it has held up extremely well over the years. My machine has a lot of RAM so maybe that's one reason things have been quick, and the main drive is an SSD. Is there anything specific about the 57 release that makes you feel caused the speed bottle-neck to disappear?

57 is lightning fast. Like, almost uncomfortably so on my machine.

Broay this is because quantum is much further along in nightly than on the other channels. Specifically, they're more aggressive with multithreaded settings, multiprocess is enabled, and the quantum css component is turned on, too.

Is also helps that we compare to chrome. On Linux chrome doesn't even do GPU rendering. So the HN crowd probably has a disproportionately bad experience with it

Re: uBlock Origin Maintainer on Chrome vs. Firefox WebExtensions

#15
post #3

Earlier quoted context omitted.

I moved to firefox once 57 was released on nightly. Firefox is finally usable (in terms of speed) again and I can use it for day to day tasks.

I think I qualify as a poweruser by some standards, I tend to have 100's of tabs open and I've never left Firefox for speed reasons or others because it has held up extremely well over the years. My machine has a lot of RAM so maybe that's one reason things have been quick, and the main drive is an SSD. Is there anything specific about the 57 release that makes you feel caused the speed bottle-neck to disappear?

57 is lightning fast. Like, almost uncomfortably so on my machine.

Broay this is because quantum is much further along in nightly than on the other channels. Specifically, they're more aggressive with multithreaded settings, multiprocess is enabled, and the quantum css component is turned on, too.

Is also helps that we compare to chrome. On Linux chrome doesn't even do GPU rendering. So the HN crowd probably has a disproportionately bad experience with it

Re: uBlock Origin Maintainer on Chrome vs. Firefox WebExtensions

#16

Huh. These actually sound like good arguments to switch to Firefox, arguments I've never heard before until now.

One thing I learned several years ago when I decided to jump on the bandwagon and try Chrome was that Chrome was unable to safely block javascript the way NoScript does because the plugin framework doesn't allow a plugin to block Javascript before it's loaded.

So all the noscript equivalent for Chrome could offer was to block Javascript after it had loaded. Which seemed unreal and pointless.

So I stayed on Firefox. Because I've been convinced for many years now that Javascript plays a major role in malware delivery through the browser.

And along with email the browser is the major delivery platform for malware.

Re: uBlock Origin Maintainer on Chrome vs. Firefox WebExtensions

#17

> It baffles me that some people thinks Firefox is becoming a “Chrome clone”, it’s just not the case, it’s just plain silly to make such statement. That's probably the single most reassuring statement about Firefox that I've heard in some time, coming from a serious dev who makes a popular cross-platform addon for both Firefox and Chrome.

What do you think of Opera becoming Chrome?

Re: uBlock Origin Maintainer on Chrome vs. Firefox WebExtensions

#18
post #9

I found this disturbing: "Chromium-based browsers are being “infested” by Instart Logic tech which works around blockers and worst, around browser privacy settings (they may start “infecting” Firefox eventually, but that is not happening now)." From his linked post: "Instart Logic will detect when the developer console opens, and cleanup everything then to hide what it does" Is this implemented via a CDN-delivered sc…

Also:

> The purpose of Instart Logic technology is to disguise 3rd-party requests as 1st-party requests, thus bypassing content blockers, and even the ability of browsers to block 3rd-party cookies (because they are stored as 1st-party cookies):

https://github.com/gorhill/uBO-Extra/wiki/Sites-on-which-uBO...

Re: uBlock Origin Maintainer on Chrome vs. Firefox WebExtensions

#19
post #3

Huh. These actually sound like good arguments to switch to Firefox, arguments I've never heard before until now.

I moved to firefox once 57 was released on nightly. Firefox is finally usable (in terms of speed) again and I can use it for day to day tasks.

How has the nightly been for you in terms of stability? Been thinking of switching to it from beta. The memory issues on MacOS are killing me, and I believe there are fixes in nightly now.

Re: uBlock Origin Maintainer on Chrome vs. Firefox WebExtensions

#20

Earlier quoted context omitted.

I think I qualify as a poweruser by some standards, I tend to have 100's of tabs open and I've never left Firefox for speed reasons or others because it has held up extremely well over the years. My machine has a lot of RAM so maybe that's one reason things have been quick, and the main drive is an SSD. Is there anything specific about the 57 release that makes you feel caused the speed bottle-neck to disappear?

57 is lightning fast. Like, almost uncomfortably so on my machine. Broay this is because quantum is much further along in nightly than on the other channels. Specifically, they're more aggressive with multithreaded settings, multiprocess is enabled, and the quantum css component is turned on, too. Is also helps that we compare to chrome. On Linux chrome doesn't even do GPU rendering. So the HN crowd probably has a di…

Wait, what? I know that hw accelerated video decoding is generally not available on linux chrome, but I'm pretty sure that lots of other things are. From my chrome://gpu

    Canvas: Hardware accelerated
    CheckerImaging: Disabled
    Flash: Hardware accelerated
    Flash Stage3D: Hardware accelerated
    Flash Stage3D Baseline profile: Hardware accelerated
    Compositing: Hardware accelerated
    Multiple Raster Threads: Enabled
    Native GpuMemoryBuffers: Software only. Hardware acceleration disabled
    Rasterization: Software only. Hardware acceleration disabled
    Video Decode: Software only, hardware acceleration unavailable
    Video Encode: Software only, hardware acceleration unavailable
    WebGL: Hardware accelerated
    WebGL2: Hardware accelerated
But this is with an integrated GPU, so maybe things are different for discrete cards.
Post reply on HN