> However, for development teams with enough resources to outrun upstream projects - to develop their own stuff and to see specific benefits faster than waiting for such things to appear upstream, if ever - it becomes tempting to fork the code and ignore the community.
And it is also tempting since it also isolates you from the opposite problem: inconsiderate upgrades causing regressions and lack of backward compatibility. Honestly, which distribution cares about backward compatibility from one release to another? Just for fun compare with Windows. Or even worse, think about Fedora who keeps issuing hundreds of non-security upgrades after the release. And this not just on the latest release but even for older "releases".
I realize backward compatibility is expensive while most Linux distributions are free. But still: if you do not care about external developers then you cannot ask them to behave and not fork.
(RedHat is off topic here since we are talking about a web browser)