Hacker News new | comments | show | ask | jobs | submit login

You are misunderstanding what "using Chromium means." As I replied to cpeterso:

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 think we are in total agreement: They will use Chromium but change some things on top, including the UI. They will also add support for Opera addons, change the login stuff, etc.

I disagree though about your saying differentiation not taking place in the engine. It takes place everywhere, including the engine.


You wrote:

> 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.


Opera has said they will leave all the core stuff to Google and just modify UI and other stuff on top. That means almost all development is done by Google.

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.


> Opera has said they will leave all the core stuff to Google and just modify UI and other stuff on top.

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.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: