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 552460
To view parent comment, click here.
To read all comments associated with this story, please click here.
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

cdude Member since:

They can own the house but need to open it so others see how they improved and can take over changes they find useful.

Just like with Linux distributors WebKit distributors have a release-branch for there version and full control. They can put patches on top, can maintain, do changes without anybody preventing them. More own patches not upstream means higher maintainence sovits in there interest to get patches upstream.

No WebKit-vendor builds its webkit based browser out of trunk. All have branches and maintain them and patches on top not in trunk or not yet in trunk.

Reply Parent Score: 2