12 Comments

Summary:

Opera has confirmed that it’s adopting the WebKit rendering engine and the Chromium framework. Why? Apple and Google have so much influence that the mobile web is being written to their specs.

opera-mini-iphone-thumb

Opera is about to shake up its browser business in a major way, by abandoning its Presto rendering engine in favor of the increasingly-ubiquitous WebKit, and by joining in the open-source Chromium project. The Norwegian firm has also announced that it now has more than 300 million monthly users.

Opera had already let slip the shift to WebKit when a company video “leaked” last month depicting a new, WebKit-based Opera browser codenamed Ice that’s going to hit iOS at some point, but the move to the Chromium framework — at the expense of Opera’s own, certainly on the desktop — comes as more of a surprise. Opera is also dropping its own Carakan JavaScript engine in favor of Google’s V8.

I’m going to go out on a limb here, but I think it unlikely that Opera founder Jon von Tetzchner would have let all this happen if he still held enough shares to exert influence on the company’s direction.

“300 million marks the first lap, but the race goes on,” CEO Lars Boilesen said in a statement. “On the final stretch up to 300 million users, we have experienced the fastest acceleration in user growth we have ever seen. Now, we are shifting into the next gear to claim a bigger piece of the pie in the smartphone market.”

Compatibility

In order to claim that bigger piece, WebKit is a smart move, Opera CTO Håkon Wium Lie told me on Wednesday morning. After all, that same rendering engine is what underpins Apple’s Safari and Google’s Chrome, and given the dominance of iOS and Android in the mobile market, it’s become a primary concern for web developers. Said Wium Lie:

“People are using WebKit prefixes for CSS properties and it’s been troublesome for other browsers to render those pages without supporting the WebKit prefixes. That has been part of the shift we’re seeing and it’s also been part of our decision making. What we see as very positive is that we will be able to take some of our best engineers and have them work on common code that many people will use — we will reach more people this way.”

Opera’s statement said WebKit and Chromium would gradually be used in “most of” the company’s upcoming smartphone and PC browser iterations. However, Wium Lie suggested that “our whole product line will be affected in due course by this”.

Those who want to see some competition maintained in the mobile browser rendering engine space had better keep their fingers crossed that Windows Phone gains more traction (Internet Explorer uses Trident) and that Mozilla’s Firefox OS (Gecko) sells like hotcakes too.

According to an Opera developer blog post, the shift to Chromium will mean future versions of Opera have built-in support for the WebM, Ogg Theora and Ogg Vorbis media codecs, but will lack native support for the H.264 and MP3 media codecs. To support the move to the new framework, Opera will also provide a conversion tool for add-on developers.

“The WebKit project now has the kind of standards support that we could only dream of when our work began,” the post read. “Instead of tying up resources duplicating what’s already implemented in WebKit, we can focus on innovation to make a better browser. Opera innovations such as tabbed browsing, Speed Dial and data-saving compression that speeds up page-load, have been widely copied and improved the web for all.”

What’s Opera for now?

Chromium, WebKit and Opera have met before, of course, notably last year when Russian web giant Yandex released a browser that combined Chromium with WebKit and Opera’s Turbo engine, which uses server-side compression to cut down on the amount of data the user needs to download, saving them money in the process.

Wium Lie denied that Opera would be paring down its model to that of a mere feature provider, but hinted that there was some precedent in what Yandex did. He also stressed that Turbo and the “impressive infrastructure” that enables it were integral to Opera’s future:

“We will be using Chromium, but you can do a whole lot of stuff on top of that. Yandex released a browser that does some interesting things and adds features, and changes the UI, and it’s different from the Chromium browser itself. We worked with Yandex on that and we will be doing similar things with our own stuff. The rendering engine is an important part of the browser — it’s not everything.”

Opera’s new Android browser will get a showing at Mobile World Congress later this month (we will be there, naturally), where the company will also be touting its operator-targeting, pay-per-use Opera Web Pass technology. As for Ice and the other outcomes of the shift to WebKit and Chromium, we’ll have to wait a bit longer to see what the new Opera looks like.

UPDATE: In this piece I originally paraphrased Wium Lie to state that moving to WebKit was a “necessity”. He disputed that as a summary of his stance, so it has been changed accordingly.

  1. One browser engine may seem good in the short-term for cross-platform developers, but it is profoundly bad news for both competition and innovation.

    Share
  2. Unfortunately, this will truly move Opera from brilliant but perhaps misunderstood forerunner to an also-ran.

    This is probably a move to increase profits and lower cost – rather than increase quality and standing out as a true innovator.

    Webkit with a shell on it. Well, it probably won’t suck, but it will also be the end of an era.

    Share
    1. Why would this turn Opera into an also-ran? Is Chrome an also-ran because it uses Webkit?

      It’s a move to spend less time duplicating work, and more time doing innovative stuff.

      Chrome is Webkit with a shell on it. As is Safari. Your point being?

      Share
  3. The best browser Opera , did not win Google and Microsoft Big Publicity.

    Share
  4. Anyone remember IE v.s. Netscape? The very reason we have standards in the first place was that we basically had 2 different internets. It is taking so long to get HTML5 out the door that we now have 2 again, WebKit and HTML5/CSS3. Unfortunately, looks like WebKit has won-out. At least WebKit (unlike IE/Netscape) is open source. Of course, the best part is, people may be using WebKit prefixes, but those prefixes dissapear when the parameters are standardized. All these lazy web programmers will have to change their code anyway. It’s a damn shame Opera is having to move away from Presto (the most standards-compliant engine) to WebKit just to make the internet work.

    Share
    1. “It is taking so long to get HTML5 out the door that we now have 2 again, WebKit and HTML5/CSS3.”

      Wrong! Webkit adheres to and supports HTML5/CSS 3. IE is the biggest problems (as far as adherence to standards go). IE 9 is supposed to be standards compliant. Supposed to be.

      http://en.wikipedia.org/wiki/WebKit

      Share
  5. I hope Opera’s team brings renewed focus on areas where Webkit is weak and Opera shines. SVG for instance.

    Share
  6. All who want to tell Opera to open source Presto should sign this:
    https://www.change.org/petitions/opera-software-open-sources-of-presto-engine

    Going by this: https://lists.webkit.org/pipermail/webkit-dev/2013-February/023841.html
    there is hope they might open source Presto but we should tell them we really want it open sourced.

    We should also tell them to open source Carakan (javascript engine-replaced by Google V8), Vega (SVG engine) and Unite (abandoned since version 12) along with it.

    Share
  7. A reason to install it

    Share
  8. Bye Opera. Keep on losing relevance on the desktop.

    Share
  9. Opera is great and comfortable, but its biggest problem always was compatibility
    with different and common features available on different webs.

    I like Chromium and Comodo Dragon browser, it’s relieve and respect privacy,
    just hope Opera don’t begin to track the activity anybody does on internet,
    just like Google Chrome does.

    Share
  10. Why can’t we have both?

    Presto and Webkit. Use Presto where you can and Webkit where it’s obvious Presto will have issues.

    Share

Comments have been disabled for this post