The Edge browser sometimes holds features back even though they are based on chromium source code. For example AV1 support, so there is some kind of diversity of browsers possible even though the people who code it all up have power.. but they have power because they create features which is deserved.
A fork with features removed is better than nothing, but not as good as an independent implementation. A fork has to weigh the risks of becoming too far out of sync with mainline—if it vetoes too often it can become difficult or impossible to merge in future fixes from upstream. An independent implementation, on the other hand, can make a call on each feature individually based on the value and the risks.
it's the same thing in the end: Firefox weighs pros and cons of implementing a feature and Edge weighs pros and cons of including a feature. It is still true though that Google has more power when everyone depends on their implementation especially because it's the path of least resistance to include everything and change nothing. And yes that means it could be more work if you choose to change something.
> especially because it's the path of least resistance to include everything and change nothing
It's only the path of least resistance for a chromium fork. For Firefox it takes a lot of work to implement a feature, which means the value proposition has to be really good for it to make it in.
