Opera and Open Source, Insight Into The ‘Turbo’ Technology

In this article we get to discuss Opera’s role as an innovator in the browser market as well as find out if Opera will release its code under the GPL and some technical bits about the ‘Turbo’ technology.

Recently I wrote an article about Opera 10 – which is currently in development – and got a lot of backlash from readers.

According to about 70 comments which were published, I downplayed Opera’s importance as a browser and as an innovator.

Jon says:

I agree with N_P. To say Opera has stagnated because it has not brought true innovation is just wrong. For one, they were the first to introduce a system like “speed-dial” which you describe as being familiar to rival browsers who were simply emulating Opera’s innovation.

I left the Opera camp a long time ago, at least 4 years, and according to some, I’ve missed the mark completely when I said Opera didn’t bring true innovation these past years.

You are wrong, then. Firefox’s awesome bar? Ripped off from Opera. Chrome and Safari’s top sites feature? Ripped off from Opera. And so it continues… Just look at the feature list for Safari 4. It’s like looking at a list of existing Opera features!

Thomas Ford, Communications Manager at Opera, contacted me after a day or so with some clarifications. We continued our conversation, and, as a result, I’ve got some interesting bits of information which I’m going to share with you.

T.F.: A lot of the comments raise different points, but I’d like to highlight a few that they didn’t. I won’t take issue with you saying there isn’t much new in the labs release. That’s fair. The labs release of Opera 10 with Turbo is essentially to showcase that technology only. It certainly isn’t a complete representation of Opera 10.

Thomas then goes on to point out an interesting aspect about the Opera Turbo technology:

T.F.: One important thing about Turbo though is that it is different from Opera Mini technology. Where Opera Mini’s OBML is actually a transcoding technology, Opera Turbo is a compression technology. They have fundamentally the same client-server architecture, but they work quite differently. Opera Mini translates the code from the Web into OBML then spits it out on the handset. Opera Turbo simply compresses things. It doesn’t transcode. This means you can use technologies like Ajax which are broken in the transcoding process.

I replied shortly:

S.N.: Truth be said, I’ve lost my faith in Opera a while ago and I didn’t give Opera Turbo enough time when I wrote the review, which was clearly pointed out by the comments.[…]

Referring to ads integrated into the browser interface, one of the main reasons I gave up on Opera years ago:

T.F.: Totally fair. I think the ads turned a lot of people off. We faced a problem. We used to be a paid product, then wanted to release a free version. Of course, we had engineers to pay and our mobile business had yet to really take off. So the ads were a necessary evil to make enough money to keep operating. I think that was in 2000 or so. In 2005 we were able to go free through the same monetization strategy Firefox uses (Google search).
I think there are a lot of users who went through the same thing with Opera. Convincing them to try us again is a challenge, but I think we’re trying even harder now.

S.N.: How would you feel about releasing the Opera code into under GPL, like Mozilla did with Firefox? What are the benefits for keeping the source code closed?

T.F.: It’s actually something that has come up a lot. I should point out that some things we do are open source. We released Opera Dragonfly (our developer tools) under a BSD license and we’ve released a bunch of open developer libraries.
But in terms of releasing the browser core under a GPL or other OS license, the benefit isn’t necessarily there for us. We make a significant amount of revenue from licensing the browser. Since we have only one core (the same browser core is at the center of Opera on desktop, on mobile and on TVs, etc), we would give away a lot of our competitive advantage.
Our CEO I think had a decent answer to the question. He’s a computer scientist by training and has worked on open source projects before. Here’s an interview that might be interesting if you have the time.
You raise a valid question and it’s definitely something we can’t rule out for the future as our company evolves. Overall though, I think our resources are best spent trying to bring open standards to the Web to improve interoperability.

S.N.: If Mozilla comes out with a decent competitor for Opera Mobile, they showed some alpha code recently, what would your response be to that situation? It would probably cut a whole lot of your revenues from OEMs.

T.F.: In practice OEMs and network operators expect many things from a Web browser. Often it requires a great deal of customization to meet their demands. No two OEMs or operators have the same demands so it makes the mobile browser space quite different to the PC browser space.
I don’t think that it necessarily would cut into our revenues. Currently there are several Windows Mobile browsers already available. Even with those competitors we have been able to grow our revenues every quarter.
Mozilla does present a more formidable competitor due to its brand recognition and pre-existing user base. I guess we’ll have to see how it plays out. I’d like to think we add value to operators and OEMs through close collaboration and partnership and thus would continue to earn their business.

To conclude, I think Opera 10 is definitely worth another review when it reaches Release Candidate status.

IT Support West London: