What happens to Firefox forks if Firefox dies?
-
Maybe if all the forks merge into a single project, and if that project becomes part of some foundation like the Linux foundation or most likely freedesktop, and if some folks from big tech companies get paid to work on it full time (probably google would, for obvious reasons, but it wouldn't be enough), and if distros start shipping that in place of firefox, and if for some reason the less tech savvy get to know about this project...
...Then if all of that happens, forks might have a chance of still existing.
This is how most big open source projects (like Linux, gnome, mesa, etc) thrive. With the catch that while most tech companies have some stake in Linux and friends, no company other than google has any stake in Firefox existing.
I'd say the more likely version of that scenario is not all the forks merging, but them all collaborating on a common base project from which they each can still produce their own spin.
-
With the enshittification of all-things-Google, a lot of us have left Chromium-based browsers for Firefox. But still, over the last 15 years, Firefox has gone from 30%+ market share to about 6% now.
With the big backlash against them over the last week, I've seen a number of people advocating for Librewolf and Waterfox -- Firefox forks focused on security and privacy -- but if Firefox loses what little revenue it has left, what will become of the forks if Firefox dies?
Hell, all Mozilla need to do is to remove
about:config
to kill the forks. Due them being Firefox with a user.js (sometimes also a CSS Theme). -
I'd say the more likely version of that scenario is not all the forks merging, but them all collaborating on a common base project from which they each can still produce their own spin.
I really hope that the forks coordinate for this to happen, soon, if not yesterday.
Maybe a group that keeps track what is to be done if Firefox development stops or if Mozilla folds or somehow abandons Firefox. Things such as:
- how to take over development from Mozilla
- the minimum that needs to be done to keep up to the standards
- the minimum that needs to be done to keep the (base) browser on par in performance with Chromium (and the others, such as Servo)
- coordinate developers and other people involved in the project
- manage donations and funding
Maybe I'm imagining some sort of a cooperative formed by Firefox forks with the main aim of keeping Firefox alive despite of (or after) Mozilla.
-
I'd say the more likely version of that scenario is not all the forks merging, but them all collaborating on a common base project from which they each can still produce their own spin.
but them all collaborating on a common base project from which they each can still produce their own spin
This is viable because this has already happened in gaming.
https://github.com/Open-Wine-Components/umu-launcher
Lutris, Heroic, Bottles use this in their backend.
-
I really hope that the forks coordinate for this to happen, soon, if not yesterday.
Maybe a group that keeps track what is to be done if Firefox development stops or if Mozilla folds or somehow abandons Firefox. Things such as:
- how to take over development from Mozilla
- the minimum that needs to be done to keep up to the standards
- the minimum that needs to be done to keep the (base) browser on par in performance with Chromium (and the others, such as Servo)
- coordinate developers and other people involved in the project
- manage donations and funding
Maybe I'm imagining some sort of a cooperative formed by Firefox forks with the main aim of keeping Firefox alive despite of (or after) Mozilla.
But since Chromium has soooo much of the market share, Firefox will always be playing catch-up. If Google decides to go full rogue and ignore W3C specs entirely and make up a bunch of their own shit, that devs then start to use because why not since the majority of their userbase use a chromium based browser, then Firefox can easily be taken out.
-
With the enshittification of all-things-Google, a lot of us have left Chromium-based browsers for Firefox. But still, over the last 15 years, Firefox has gone from 30%+ market share to about 6% now.
With the big backlash against them over the last week, I've seen a number of people advocating for Librewolf and Waterfox -- Firefox forks focused on security and privacy -- but if Firefox loses what little revenue it has left, what will become of the forks if Firefox dies?
My opinion is there will be a new Firefox, whether using gecko or servo. Hell, I'd start a new foundation myself if required.
-
With the enshittification of all-things-Google, a lot of us have left Chromium-based browsers for Firefox. But still, over the last 15 years, Firefox has gone from 30%+ market share to about 6% now.
With the big backlash against them over the last week, I've seen a number of people advocating for Librewolf and Waterfox -- Firefox forks focused on security and privacy -- but if Firefox loses what little revenue it has left, what will become of the forks if Firefox dies?
The chances are some new foundation/non-profit will be created to fund its development.
It's either gonna be great like other community oriented project (like FreeCAD, Blender, or KDE), or corporate centric that prioritize industry needs (every single Linux Foundation project).
-
They die. Full stop.
Not even Microsoft had the strength to maintain a browser engine, that's why they moved Edge to Chromium, they gave up.
But microsoft is garbage company so that doesn't say much. They've been trying to remake their settings page for more than a decade and it is still shit.
-
Who isn't to say that the forks will just simply branch off and be self-sustainable? See, that's the beauty of open source and the licenses of which these things operate under. It would suck if it was as close-sourced as Windows is because if all of the forks functioned off of the licenses something as Windows operates under, we wouldn't have choice.
Without lots of money, it's not doable reliabily
-
With the enshittification of all-things-Google, a lot of us have left Chromium-based browsers for Firefox. But still, over the last 15 years, Firefox has gone from 30%+ market share to about 6% now.
With the big backlash against them over the last week, I've seen a number of people advocating for Librewolf and Waterfox -- Firefox forks focused on security and privacy -- but if Firefox loses what little revenue it has left, what will become of the forks if Firefox dies?
Honestly, people are overreacting to the ToS changes. Mozilla haven't actually changed what they're doing; they're just removing text they legally can't include since the definition of "selling data" varies by jurisdiction. It doesn't always mean literally selling user data. California is very strict about it for example.
-
They all die. To maintain that codebase millions of moneys are needed every year and dozens and dozens of devs working on it full time. There's a lot of boring and hard work that will never be replaced by some indie hackers working on their free time that needs to be done.
I read millions of "monkey" instead of "money" and was trying to understand if you were insulting browser developers or implying that thousands monkeys could to do the same work as a developer
-
Because web browsers are stupidly complicated and expensive to maintain. The only real competitor is google who has infinite money to maintain the chrome superiority and you need resources to maintain safety, fix bugs, and adhere to new standards, which get every time more complex (also thanks to google that doesn't want competitor). You need a lot of budget for that.
-
But since Chromium has soooo much of the market share, Firefox will always be playing catch-up. If Google decides to go full rogue and ignore W3C specs entirely and make up a bunch of their own shit, that devs then start to use because why not since the majority of their userbase use a chromium based browser, then Firefox can easily be taken out.
If Google decides to go full rogue and ignore W3C specs entirely and make up a bunch of their own shit, that devs then start to use because why not since the majority of their userbase use a chromium based browser, then Firefox can easily be taken out.
Which is basically the ending of the first browser wars, as far as I can remember. Internet Explorer had a little bit less market share than Google Chrome has nowadays, but still an overwhelming majority. Moreover, Internet Explorer had these IE-only tags and features, which further reinforced such things.
But here we are. Yes, Google Chrome and Google has an overwhelming majority right now, but so was IE (thanks to Microsoft's practices) back then. Google Chrome came at the right time with what people actually wanted at that time, and so was able to gain the upper hand, and eventually a chokehold.
My response though is more about "keeping things alive for its users", at least until such a breakthrough happens (maybe Servo has it?) or more pessimistically, until internet browsers fade away into obscurity (or perhaps just like IRC clients, it's still a thing, right?)
-
I read millions of "monkey" instead of "money" and was trying to understand if you were insulting browser developers or implying that thousands monkeys could to do the same work as a developer
If you have infinite monkeys on IDEs, some subset of 1000 of them will eventually make Firefox.
-
With the enshittification of all-things-Google, a lot of us have left Chromium-based browsers for Firefox. But still, over the last 15 years, Firefox has gone from 30%+ market share to about 6% now.
With the big backlash against them over the last week, I've seen a number of people advocating for Librewolf and Waterfox -- Firefox forks focused on security and privacy -- but if Firefox loses what little revenue it has left, what will become of the forks if Firefox dies?
Probably the same thing that happened when Netscape died
-
Probably the same thing that happened when Netscape died
It will become Seamonkey?
-
With the enshittification of all-things-Google, a lot of us have left Chromium-based browsers for Firefox. But still, over the last 15 years, Firefox has gone from 30%+ market share to about 6% now.
With the big backlash against them over the last week, I've seen a number of people advocating for Librewolf and Waterfox -- Firefox forks focused on security and privacy -- but if Firefox loses what little revenue it has left, what will become of the forks if Firefox dies?
Honestly, Firefox would be much better off without Mozilla. A donation model that would fund a small development team that could just focus on making a good browser would work just fine for this.
-
They die. Full stop.
Not even Microsoft had the strength to maintain a browser engine, that's why they moved Edge to Chromium, they gave up.
The dynamics of commercial companies and open source are completely different. Microsoft moving to Chromium was a business decision. They didn't see the value in spending money on a niche browser that didn't give them any leverage. People developing open source aren't doing it for profit or market dominance.
-
But microsoft is garbage company so that doesn't say much. They've been trying to remake their settings page for more than a decade and it is still shit.
Bad argument, Microsoft is among the three most valuable companies in the world, when something is important to them they get it done properly (e.g. hyperv is the best made part of windows, because they need it for azure). The settings page doesn't get them money, only nerds care if it's bad, a browser does.
-
With the enshittification of all-things-Google, a lot of us have left Chromium-based browsers for Firefox. But still, over the last 15 years, Firefox has gone from 30%+ market share to about 6% now.
With the big backlash against them over the last week, I've seen a number of people advocating for Librewolf and Waterfox -- Firefox forks focused on security and privacy -- but if Firefox loses what little revenue it has left, what will become of the forks if Firefox dies?
All the forks need to make a common engine independent of Mozilla. Pale Moon did it with Goanna and it is shared between Basilisk and K-Meleon as well. The big problem is that any new engine has to beat being filtered by Cloudflare or other WAFs that discriminate by user agent. A bold idea is for all the Firefox forks to rebase off of the new Ladybird engine and abandon the old Gecko codebase entirely.