Linked by Thom Holwerda on Sat 19th Jan 2013 14:22 UTC
Opera Software This is actually pretty big news - both exciting and tragic at the same time. Opera has revealed Opera Ice, its next mobile browser, to PocketLint. This new browser represent a big shift in both user interface as well as rendering engine, since it has a new, unique interface, as well as a new rendering engine... New to Opera, that is, as it's a WebKit-browser.
Thread beginning with comment 549456
To view parent comment, click here.
To read all comments associated with this story, please click here.
Wondercool
Member since:
2005-07-08

Why would you leave your 20 year investment in your own technology behind and switch to something that will provide no competitive angles to the competition?

It is *not* free to switch, you will have to relearn the technology and reprogram all that you have invented previously, like Opera Mail, Unite.

I still don't see it. Unless they are only switching the rendering engine? Still a lot of work, still a lot of reprogramming...

Reply Parent Score: 3

MrWeeble Member since:
2007-04-18

Why would you leave your 20 year investment in your own technology behind and switch to something that will provide no competitive angles to the competition?


Perhaps they took some advice from Nokia?

Reply Parent Score: 7

zima Member since:
2005-07-06

Symbian was largely external to Nokia, too. And now, after retiring Symbian, Nokia seems to focus more on Series40 (their internal OS technology) than it was the case over the last half+ decade.

Reply Parent Score: 2

someone Member since:
2006-01-12

This is actually not such a big switch from a technical perspective. Opera uses Qt as its toolkit, and Qt had already adopted WebKit as its standard rendering engine a long time ago. So essentially, they are just switching from a custom rendering engine to the standard rendering engine of the platform. In addition, Opera always has the option to integrate their Carakan Javascript engine, if they are unsatisfied with the performance of JavaScriptCore or wanted something to differentiate themselves from the rest of the WebKit crowd

Edited 2013-01-19 17:36 UTC

Reply Parent Score: 0

PresentIt Member since:
2010-02-10

Why would you leave your 20 year investment in your own technology behind and switch to something that will provide no competitive angles to the competition?


Because your 20 year investment is bogging you down and leaving you well behind the competition?

Because switching to the technology the competition is making for you for free suddenly gives you loads of spare resources that can be used for actual innovations instead of constantly trying to catch up?

Using the same engine as another browser doesn't mean you have no competitive angle. That depends entirely on what you build on top of the engine.

It is *not* free to switch, you will have to relearn the technology and reprogram all that you have invented previously, like Opera Mail, Unite.

Unite is being dropped.

And while it's not free to switch, the resources used to build something on WebKit would otherwise be wasting their time constantly fixing compatibility problems. And once the port has been done you suddenly have tons of spare resources that used to be dedicated to building a separate engine. This makes sense if you think ahead a few years.

I still don't see it. Unless they are only switching the rendering engine? Still a lot of work, still a lot of reprogramming...

Sure, it's just a rumor based on basically nothing. But it would not be a stupid thing to do. The reprogramming would be done by people who would otherwise be working on the current engine.

Reply Parent Score: 1

Wondercool Member since:
2005-07-08

Well, I hope it will pan out well for Opera. Surely it must be painful to dump your own technology and switch to the competitors tech? I would be gutted if I was working for Opera.

I actually don't think Opera has a technology problem that needs solving with Webkit, more a marketing problem.

At least the latest 12.12 desktop browser seems mighty fine and it has proper extensiosn (finally after so many years)

Another problem with webkit might be that you have to keep different code bases for desktop and mobiles which might to extra costs and compatability issues.

I guess we will know in a year if it is a good move.

Reply Parent Score: 2