> why Firefox is not used to build more independent browsers the way chromium is?

Ease of integration. It's impossible to integrate Firefox compared to chromium. Unless this is solved, Firefox will die. The hope is new engines like Servo (maybe ladybird), where they are actually putting time and resources to make it easy to integrate. I'll never switch to chromiumia, but as soon as one of those new engines is mature enough, I'm definitely dropping Firefox.

Yeah, I dont like either, but I wont support Mozilla closed mind and stupidity. They pretty much abandoned Firefox (when was the last time they really updated the browser, other than incremental small corrections?), and I refuse to give my money to fund the type of shit they expend it.

They should have through about that before going all political in their positions as an organization. It was easy with the cushion of google and federal goverment money under them (impressive how easy is to do "charity" and activism with other people money).

Now I wanna see if they will put their wallets where their mouth is, and apparently, they will not.

Every time I receive a e-mail from mozilla fundation asking for 10 bucks to fund their precious inclusivity program that have nothing to do with firefox, because they lost goverment funds, I just laught and think they should ask for a loan from their previous CEO, since she receive 7 mi in one year. I just delete the e-mail after that.

> My question to the FOSS community is why Firefox is not used to build more independent browsers the way Chrome is?

I actually looked into this. Say you consider yourself as part of the FOSS community, and want to build a new browser, and you start to look for your options. The only things readily available as libraries are webkit (currently owned and open sourced by Apple) and webkit-gtk (based on the former). Apple is like Apple and doesn't really want you to use their open source lib, so even though webkit-gtk team made it happen anyway, good luck if you want to do it yourself. If you decide to just use webkit-gtk, you've made a decision similar to lots of other members of the FOSS community in this area (luakit, the Rust webview crate, etc.). Another option is Qt WebEngine. It's based on Chromium. It's part of the Qt ecosystem and though I think you can use it as a standalone library, carving it out still requires some engineering. So these are the options that are available as libraries. And where are the Firefox ones? Servo makes it clear at the beginning of The Servo Book that it isn't available as a library yet. And Gecko? Firefox source doesn't even include a directory named gecko. It's so tightly coupled with the other parts that you'll need a lot of engineering to carve it out. And this is in contrast to Blink, the engine of Chromium, which is nicely placed in its own directory, having its own webpage with some learning resources.

My guess is that browsers like ice weasel, libre wolf, while good pieces of software, they dont have a whole company behind them.

Libre wolf "about us" page, dont even have the developers real name, only their online handle.

The closest of a "professional" port of firefox is pretty much Zen Browser.

Is what I been using, alternatin with Brave Browser.