The problem with Firefox forks I have:
- you don't know when they are gonna keel over and die.
- non-existent support from distro package repositories. Void Linux for example has an understandable policy of not providing Firefox and Chromium forks. I really don't wanna install them from appimages or fatpak.
I have found using firefox provided by my distro with something like arkenfox to be a decent medium but it sucks that this is required in the first place. I wonder if distro repository maintainers try to package Firefox with better defaults but I don't know how to look for that.
That, and in many cases they get "stuck" at the firefox version they are based on which means that newer things might not work and more importantly security fixes might not be applied.
> you don't know when they are gonna keel over and die
Would it really matter? Browsers are pretty much a commodity item. Of all the big pieces of software in your life, I can't imagine one easier to replace than a browser.
You have to then go through the trouble of redoing persistent logins, transferring bookmarks, history, plugins, etc. That's a nontrivial amount of effort right there.
At least with firefox based browsers I believe the actual user profile folder is pretty compatible across browsers, copying that should copy every aspect of what makes your browser yours, though it might contain extras that won't be utilized by vanilla firefox.
I have found using firefox provided by my distro with something like arkenfox to be a decent medium but it sucks that this is required in the first place. I wonder if distro repository maintainers try to package Firefox with better defaults but I don't know how to look for that.