If you’re maintaining any Firefox forks, it’s your moral duty to not cotribute your patches directly to the Firefox project, maybe even to turn it into a hard fork.
On one end, a clear sign of “f*** you” with such decisions is important. On the other, Mozilla is already in a rough place, and with so many genuinely good projects, including Waterfox, depending on Firefox or at least Gecko, this is akin to biting the hand that feeds you.
All these teams cannot maintain their own browser engine, and without it, they may as well turn to dust. Thereby, maintaining their upstream is in their best interest.
It is, but it’s so divergent these days that 90% of Mozilla patches won’t even apply to the codebase (and presumably vice-versa). My conclusion is that Pale Moon and Goanna are capable of surviving if Firefox development ceases.
If you’re maintaining any Firefox forks, it’s your moral duty to not cotribute your patches directly to the Firefox project, maybe even to turn it into a hard fork.
It’s…complicated.
On one end, a clear sign of “f*** you” with such decisions is important. On the other, Mozilla is already in a rough place, and with so many genuinely good projects, including Waterfox, depending on Firefox or at least Gecko, this is akin to biting the hand that feeds you.
All these teams cannot maintain their own browser engine, and without it, they may as well turn to dust. Thereby, maintaining their upstream is in their best interest.
False.
Pale Moon is criticied precisly because its developers don’t have the resources to keep it fast, feature complete and secure.
Interesting, though Goanna is still a Gecko fork.
It is, but it’s so divergent these days that 90% of Mozilla patches won’t even apply to the codebase (and presumably vice-versa). My conclusion is that Pale Moon and Goanna are capable of surviving if Firefox development ceases.
I see