(The other more minor requirement for me is bookmark tags, but I may be able to hijack my way around that)
What, if anything, should I do about using Mozilla's Firefox
11–20 of 149 posts
Re: What, if anything, should I do about using Mozilla's Firefox
#12As the post is saying: I'm disappointed, but there is no technical reason to drop Firefox for now. Yet I feel like I must do something when the ToS is still hot, although I don't expect any change from Mozilla.
Re: What, if anything, should I do about using Mozilla's Firefox
#13Earlier quoted context omitted.
From the article: > sustainable, viable alternative Free/open source browser, in a state which I can use today, supporting the plugins that I use daily, which is not based on Chromium Brave is based on chromium.
I'd say Vivaldi[0] scratches that itch better for me, without having to sell my soul to the crypto gods. I only wish it did not crash randomly on MacOS a couple of times per week. [0]: https://vivaldi.com/
Re: What, if anything, should I do about using Mozilla's Firefox
#141. Mozilla is now an advertising business - see e.g. links in this El Reg post [0].
2. How you feel about the alternatives.
Behind the PR bluffing of the last few days, #1 is clear. Mozilla has hitched the wagon to advertising.
There's unlikely to be a single good answer for #2. All the alternatives have compromises: Vivaldi is chrome-based and has some closed source code; Brave has crypto and Eich's political views (and also chrome-based; the various firefox forks (LibreWolf, PaleMoon, Waterfox, ...) all have questions over their sustainability.
Perhaps the most promising is Ladybird, but it's a good way off yet.
Let's hope we're near the botton of the enshitification curve and there are positives on the horizon somewhere.
[0]: https://www.theregister.com/2025/03/02/mozilla_introduces_te...
Re: What, if anything, should I do about using Mozilla's Firefox
#15I tried Librewolf, but the unstable RPM repository was very annoying, because zypper disallows system updates if even one repository fails to refresh. I also had some weird issues keeping it pinned to my desktop environment's dock. It also didn't want to save its window geometry (very annoying for me), and the only way to transfer from Firefox is to manually copy your profile data.
But mainly, I'm still dependant on Mozilla no matter where I go. They are the ones actually doing the hard work of developing the browser engine; all of these forks are just some patches upon that, so with Firefox I only have to deal with (and trust) Mozilla and my distro, and not some other project in addition to Mozilla.
Re: What, if anything, should I do about using Mozilla's Firefox
#16Re: What, if anything, should I do about using Mozilla's Firefox
#17The Chrome/Chromium mono-culture google created is imo the problem here. Until a solution to that is found this will continue to be a problem
Re: What, if anything, should I do about using Mozilla's Firefox
#18It is unclear why that having multiple different browser engines is strategically important. As far as I know we've long left behind the world where a hobbyist project could reasonably expect to implement modern JavaScript. Brave's existence and success suggests that competitors building on Chromium are viable.
Not to say it is a bad thing to have alternatives floating around; but at this point it is probably easier to have multiple forks of Chromium than strive to have code with a completely independent genealogy.
Re: What, if anything, should I do about using Mozilla's Firefox
#19Earlier quoted context omitted.
I'd say Vivaldi[0] scratches that itch better for me, without having to sell my soul to the crypto gods. I only wish it did not crash randomly on MacOS a couple of times per week. [0]: https://vivaldi.com/
Vivaldi is chromium based and not open-source.
Re: What, if anything, should I do about using Mozilla's Firefox
#20It's the best option we have.