> When we took the decision to switch to Chromium, compatibility was one reason — but most importantly, we wanted to spend our time on browser innovation, rathe

> When we took the decision to switch to Chromium, compatibility was one reason — but most importantly, we wanted to spend our time on browser innovation, rather than competing on building a rendering engine. This seems to be saying that "browser innovation" can only be done in the UI? That seems misguided. Innovating only in the UI has been tried many times: Flock, RockMelt, Dolphin, etc. It's never worked in a significant way. Not to say it never will, I suppose anything is possible, but it seems highly unlikely - what is different this time?