Opera moves to WebKit

[Arthur]

One less browser to test your websites in now.

 

Source: Opera

 

Time to say goodbye

Today, we announced that Opera has reached 300 million active users. At the same time, we made the official announcement that Opera will move from Presto to WebKit as the engine at the core of the browser.

 

With this, Opera will be the first major browser to switch to a completely new rendering engine.

 

Presto is a great little engine. It's small, fast, flexible and standards compliant while at the same time handling real-world web sites. It has allowed us to port Opera to just about any platform you can imagine. And unlike what some people seem to believe, Presto was actually designed from the ground up with compatibility in mind. It was always a goal to be compatible with the real web while also supporting and promoting open standards.

 

That turns out to be a bit of a challenge when you are faced with a web that is not as open as one might have wanted. Add to that the fact that it is constantly changing and that you don't get site compatibility for free (which some browsers are fortunate enough to do), and it ends up taking up a lot of resources - resources that could have been spent on innovation and polish instead.

 

It's the right thing to do

Although I was skeptical at first when I started hearing about the switch, I am now fully convinced that it is the right thing to do. Not only will it free up significant engineering resources at Opera and allow us to do more innovation instead of constantly trying to adapt to the web, but our users should benefit from better site compatibility and more innovative features and polish.

 

This move allows us to focus even more on the actual user experience.

 

Contributing to a monoculture on the web?

Yes, monoculture is bad, but Opera was never really in a position to prevent it in the first place. Even with Opera as the dominant mobile browser and more than 300 million active Opera users in total across all platforms, web developers still designed just for WebKit.

 


If switching to WebKit allows us to accelerate our growth and become an important contributor to the project (we will contribute back to WebKit, and have already submitted our first patch (bug)), we may finally have a direct impact on the way web sites are coded. We want sites to be coded for open standards rather than specific browsers.

 

At the very least, there will be more competition in the browser space, and competition is always good news.

[SYNACK]

Another one bites the dust, we'll be back to 'designed to only run on...' in no time.

[Arthur]

we'll be back to 'designed to only run on...' in no time.

 

http://i.imgur.com/HFC9XuM.gif http://i.imgur.com/SHMJX6W.gif

[Norphy]

One less browser to test your websites in now.

 

 

 

Not necessarily. I've seen Safari and Chrome return different results before despite both being based on Webkit.

[Arthur]

I think in Opera's case in might, since they are taking the entire rendering engine from Chromium (Chromium Embedded Framework?).

[CyberNerd]

Opera and Chrome are now moving to Blink

 

Blink - The Chromium Projects

[Arthur]

Opera and Chrome are now moving to Blink.

It should be interesting to see how this turns out, especially with Mozilla and Samsung also working on a new rendering engine called Servo.

 

Blink's out-of-process iframe's looks like it could be related to the new HTML tag the Chrome Apps team are working on?

 

One change we’re planning is adding "out-of-process iframes". These allow Chromium to separate individual parts of a page into separate sandboxed processes. Implementing this will require large restructurings of how iframes are handled in WebKit. Some of these restructurings are incompatible with other WebKit ports and have thus been delayed until now.

 

Chrome Apps Team has started to work on a new HTML tag named to embed Ads inside Chrome Apps in a separate process which will enforce some separation between ad networks and app code for security and privacy.

 

If you wanna test it, you can run last chromium build with these two switches --enable-adview and enable-adview-src-attribute, load an unpacked chrome app with "adview" permissions and play around with the tag. (Source)

Edited April 3, 2013 by Arthur