1332
this post was submitted on 26 Jan 2024
1332 points (99.0% liked)
Technology
59631 readers
2686 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
There is a difference between forks made by other people to tweak a project/do something specific for it, and the base project's dev team moving away from whatever it became.
I'm usually not in favor of such fork because the reason for moving away is sometime dubious; some project just rename themselves to "start fresh and drop legacy compatibility issue". But in the case of Firefox, Mozilla is the thing holding back features while adding bloat. Since it can't change to a saner structure with more long-term sustainability plans, devs/engineers could move into a fork to not be bound to that anymore.
Of course it's not that easy; for all the bad Mozilla (foundation or other, I don't care much that they are two entities at this point since one is owned by the other) is doing to the actual software, they do provide salaries. At least, for now.