In my opinion, that's a bad move. I did the opposite. Firefox let's you customize everything you want, staring from UI to how the browser itself works. Firefox is really 100% customizable unlike any other Chromium browser out there.
Don't like Mozilla data policy? Just turn data collectio off and you're good.
Don't like Firefox looks the way it looks? Create your own userChrome.css and make your own design of the browser. Or use one of the hundreds already made designs.
Don't like how the browser works? User.js file is your best friend.
Brave and Chromium is stuck with predefined settings, flags and that's pretty much it.
Dito. And there's not even a need to use an external text editor - for editing those, not need to touch those files either (unless you use one made by another - replacing default) - you can do all that within the browser, by typing:
about:config in address bar. They save instantly - as soon as you press enter. You can also add some missing entries (if not present there). Clicking on
Show Only Modified Preferences - will show you all the changes made (from Default) - even the option to revert to Default - if a setting was changed from about:config.
At times, Firefox shoots itself in the foot - by playing the same tricky game as Chrome - to get some extra points in "synthetic benchmarks". Rather stupid at times, like setting: nglayout.initialpaint.delay & nglayout.initialpaint.delay_in_oopif to 5 as Default setting. Which can be rather demanding for many systems or phones - using FF - thus, on heavy pages - one could notice a slight strugle to render the page at that speed. Around a decade ago - this setting was set to 250 - which shows more common sense as "default setting (for every macine using it)". So hey, if your system - was powerfull enough - you could lower the value and notice a faster loading page. But... 5, is just to low - formany machines. Thus, to get the best of both worlds - setiing it to more reasonble values like 50 or even 100 - can actually be an improvment "for most systems and the human eyes" - since now it has enough time to render the content "more smoothly" - avoiding a visable imput lag (as if it's chocking - before rendering the whole page "if a heavy page that is" ).
I didn't, so i'm still waiting for some incriminatory evidence.
