> The tight relationship between rendering engine and browser has been broken by Chrome and its “children” (and in some way also by Apples enforced usage of the

> The tight relationship between rendering engine and browser has been broken by Chrome and its “children” (and in some way also by Apples enforced usage of their WebKit implementation in ios). Mozilla need to follow suit in order to survive, rip that rendering engine out, build a new browser and a “browser toolkit” to let other people build their own. Exactly. I would really like to use something google-free, but the interface of Qutebrowser is too good, and Qutebrowser can't use Mozilla's rendering engine, even though the developers would like to.