3 ms·
The problem with forks is having to chase upstream. The dominant browser can keep making changes with reckless abandon. And the fork has to keep up with those,
by ocdtrekkie 8y ago
The problem with forks is having to chase upstream. The dominant browser can keep making changes with reckless abandon. And the fork has to keep up with those, even if it breaks their own features, lest they become incompatible with the "standard" version.
- rat9988 8y agoUnless you make the fork the dominant browser.
- feanaro 8y agoAt which point you begin to question what benefit you gained from initially siding with a single engine in the first place.
- chr1 8y agochasing upstream is a lot easier than chasing web standards and chromes performance, especially if you are only interested in providing more powerful extension api and better ui