Linked by Thom Holwerda on Sat 19th Jan 2013 14:22 UTC
Permalink for comment 549465
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
More News »
Sponsored Links



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