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 552735
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[15]: Comment by ssokolow
by moondevil on Sat 16th Feb 2013 09:10 UTC in reply to "RE[14]: Comment by ssokolow"
moondevil
Member since:
2005-07-08

Exactly!

Not matter how cool it is that WebKit is open source, developers get hired to create applications for what consumers have right now, not in some wonderful FOSS future world.

Reply Parent Score: 3

RE[16]: Comment by ssokolow
by cdude on Mon 18th Feb 2013 11:59 in reply to "RE[15]: Comment by ssokolow"
cdude Member since:
2008-09-21

developers get hired to create applications for what consumers have right now


Wrong. Every developer is hired to produce patches in the future. Nobody expects and can produce patches backwards. Nobody can actually change the past, not in software development, not in anything.

What you mean is that the patches that are produced land in a future product or future update of the product. If the product gets such updates is not a decision done by the developer, the project or the code-license.

In your case iPhones get updates including newer WebKit's at least a certain time till the whole product is EOL. Thats 100% an Apple decision.

Reply Parent Score: 2

RE[17]: Comment by ssokolow
by moondevil on Mon 18th Feb 2013 20:04 in reply to "RE[16]: Comment by ssokolow"
moondevil Member since:
2005-07-08

From your comment I can understand that either you don't sell software for living or have very nice customers...

Reply Parent Score: 2