On: Google backtracks on Chrome modifications that wou...

[chr1]

Playing devils advocate here, why a different engine is needed? Chrome clone can add webrequest feature too, and it would be much easier to maintain.

[ocdtrekkie → chr1]

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.

[chr1 → ocdtrekkie]

chasing 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

[rat9988 → ocdtrekkie]

Unless you make the fork the dominant browser.

[feanaro → rat9988]

At which point you begin to question what benefit you gained from initially siding with a single engine in the first place.