They are using Chromium as their browser. Chromium is a full browser, so basically almost all the work on Opera's new browser will be done by Google. That is why I said "outsourcing development to Google", but of course I didn't mean it literally as in "paying Google to develop for them".
That's not speculation, that's just what it means when Opera is switching to Chromium.
Opera will add stuff on top. But Opera can't differentiate much in the core browser stuff, otherwise it would be forking Chromium and it would become harder and harder over time to get updates from upstream. That makes no sense technically or business-wise. What does make sense is to add things on top that are modular and separate, for example remove Google's login and replace it with Opera's, etc.
Using the Chromium framework doesn't mean that you are using the actual final Chromium UI. The CEO himself said they're building a new UI.
Differentiation doesn't take place in the browser engine. It take splace in the UI. Most people have no idea which engine they are using, and they don't care.
I disagree though about your saying differentiation not taking place in the engine. It takes place everywhere, including the engine.
> almost all the work on Opera's new browser will be done by Google. That is why I said "outsourcing development to Google"
According to that logic, using any open-source component is outsourcing development. Doesn't make sense.
This isn't the case when you use a small open source codebase. But it is the case here when Opera is using an enormous codebase by a huge corporation, and just innovating in the UI and other modular features on top of the huge core.
False. Opera has said they will contribute to both WebKit and Chromium.
> But it is the case here when Opera is using an enormous codebase by a huge corporation
WebKit is not Google's codebase.