Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I was on the reddit thread when it happened - was super confused as I just updated my firefox and it happened at a very similar time frame so I assumed it was from the update

I personally found the issue trivial, my main addon is ublock origin. There was a workaround using about:debugging and installing UBO on there which worked so it's not like the fix was a long process.

Being committed to a single browser, if anyone was using firefox for as long as me, I can't fathom someone leaving their main browser over something like this. I haven't been using it for THAT long but what if Chrome did something like this too? Then they'd move to another browser that's not FF/Chrome?



I too use only two extensions, uBlock Origin and HTTPS Everywhere and the hotfix pushed by Mozilla re-enabled them within half an hour of disabling. I do sympathise with those who apparently lost the settings of certain addons, notably Container based ones. Fortunately I always found the UX of Containers so clunky that I never bothered.

Sticking with Firefox as an open competition to the browser monopoly is critical now more than ever before.


> Sticking with Firefox as an open competition to the browser monopoly is critical now more than ever before.

I think this fact cannot be emphasized enough. Or we'll have the 90s monopolized web again: "Optimized for Chrome" - not that there'd be a lack of websites already doing that as of now.


Mozilla fine tuning some of their practices is as critical. These hn threads might give good pointers by concerned, well-meaning users.


I have been on the tipping edge of switching from FF to another browser for a long time now.

Short-lived bugs such as this one do not annoy me as much as the terrible performance of FF. It is not rare that FF uses 2 cores at full utilization all the time.

I always end up installing a new browser out of anger, but I _always_ come back to FF for its great features that I have become addicted to.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: