> Though I agree with your basic argument, it must be noted that you have a choice to fork Firefox. You cannot do that with Chrome.
Except that in reality, no, you don't. Except if you are a team. And have funding. No one can possibly go through all those changes and apply them in a clean manner while having compatibility in mind. And even if that happens (waterfox), I (as a user) cannot trust them because I (and many more) don't have the time to search through all the commits to see what the fork is _actually_ doing (which in reality is just wasting time).
From one hand, I actually love how firefox is open and transparent and I trully believe the main devs and the whole project deserves so much more, but at the same time I consider many of their choices very poor and without thought.
Except that in reality, no, you don't. Except if you are a team. And have funding. No one can possibly go through all those changes and apply them in a clean manner while having compatibility in mind. And even if that happens (waterfox), I (as a user) cannot trust them because I (and many more) don't have the time to search through all the commits to see what the fork is _actually_ doing (which in reality is just wasting time).
From one hand, I actually love how firefox is open and transparent and I trully believe the main devs and the whole project deserves so much more, but at the same time I consider many of their choices very poor and without thought.