Linked by Thom Holwerda on Wed 13th Feb 2013 13:21 UTC
Opera Software De kogel is door de kerk: as we already talked about earlier, Opera is going to switch to the WebKit engine, leaving its own Presto rendering engine behind. We didn't yet know if they would the switch only on mobile or on the desktop as well, and they cleared that up too: both mobile and desktop Opera Browsers will switch to the WebKit rendering engine.
Thread beginning with comment 552399
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:

Umm... I have. I have done some custom [proof-of-concept] type projects using the Qt5WebKit codebase.

I like it just fine. But that doesn't mean that it will provide 100% of what Presto provides in a convenient way.

I would say exactly the same thing in reverse if someone were trying to take the Presto engine--which I am sure is also a good code base--and stick it into a long-term WebKit project.

Edited 2013-02-13 22:59 UTC

Reply Parent Score: 3

cdude Member since:

Qt5 QWebKit doesn't expose all the functionality and flexibility WebKit offers.

Opera also already started on that. They just pushed patches to improve HTML columns in WebKit. So, this extending where they see need isn't theory but it already is happening successfully.

Reply Parent Score: 2

telns Member since:

Unless they fork it, they can only extend the project in ways that are beneficial to the community in general, and their submissions will have to be approved.

There is a lot of good that comes from participating in a large, free project like WebKit, but it isn't all roses. There is also a lot of uncertainty and loss of control that comes with it.

If you can't see how that works, I'm not really sure how else to convey it. The closest analogy is that it is like renting your house instead of owning it. You can paint the walls (if you get permission), but you can't remodel the kitchen.

Reply Parent Score: 3