Hacker News new | ask | show | jobs
by lblume 482 days ago
Well, we absolutely should be. The entire point of the open source community is to be able to react to this kind of organizational failure and disalignment with original values. Where exactly do the problems lie? Resource allocation? Trust/security issues?
1 comments

Not a (consumate, formal trained) developer so please don't take my word on this, but for what I've read the big issue development wise about forking Firefox is that its codebase is kind of a mess, in like dissociating the Gecko engine and the UI would imply a tedious, herculean effort, and this is the main reason there are few Firefox "forks" (librewolf, etc.) with little modifications respect to Firefox, whereas there are tons of forks of Chromium.

Now, I understand making a Firefox fork that doesn't include this new changes in upstream doesn't imply major changes in its code, but still it seems like if you want people to use your fork requires more than that, or maybe you'll end up with a scenario like Debian vs Biebian and Hannah Montana Linux.