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 552320
To read all comments associated with this story, please click here.
Comment by ssokolow
by ssokolow on Wed 13th Feb 2013 15:17 UTC
ssokolow
Member since:
2010-01-21

I have mixed feelings about this.

On the one hand, I'm concerned about whether three engines is enough variety to ensure that APIs and standards don't codify implementation details too readily when one of them has Trident's reputation for being something we only support because we're forced to.

On the other hand, I'm eager to have one less closed-source program sitting on my system just because I need to do compatibility testing.

Reply Score: 5

RE: Comment by ssokolow
by lucas_maximus on Wed 13th Feb 2013 19:07 in reply to "Comment by ssokolow"
lucas_maximus Member since:
2009-08-18

Actually modern version of IE needs less shims than Chrome and Safari.

It seems the boot is on the other foot now.

Reply Parent Score: 3

RE[2]: Comment by ssokolow
by cdude on Wed 13th Feb 2013 21:32 in reply to "RE: Comment by ssokolow"
cdude Member since:
2008-09-21

Only in a parallel universe. Microsoft themself spoke out loud just recently that please, please web-designers, not forget the IE.

Firefox and WebKit. That's the landscape. Both working together well on all platforms (including Windows) and usually if it works in one it does in the other too.

Its IE being far behind like still not supporting for example WebGL, still not working on THE major platforms Android and iOS.

Edited 2013-02-13 21:39 UTC

Reply Parent Score: 2

RE: Comment by ssokolow
by woegjiub on Wed 13th Feb 2013 21:25 in reply to "Comment by ssokolow"
woegjiub Member since:
2008-11-25

Three engines? Trident isn't worth testing, nobody uses IE except to download chrome or Firefox, unless they are forced to use it at work.


...I would love to be able to say.
I wish MS would make it multiplatform already, so I didn't need to virtualise just for their engine.

Edited 2013-02-13 21:26 UTC

Reply Parent Score: 1

RE[2]: Comment by ssokolow
by Adurbe on Wed 13th Feb 2013 22:24 in reply to "RE: Comment by ssokolow"
Adurbe Member since:
2005-07-06

I am currently testing a UK Very large client's customer-facing website.

Their usage stats looks something like below;

IE8 ~15% of all traffic to the site
IE9 ~20%
Firefox ~20%
Chrome ~30%

The rest is made up of other browsers or variations inc Opera and IE10. We simply can't justify the resource as a business to test theses browsers at this time.

I WISH I could stop testing IE8 (as does tend to throw up a number of issues on more advanced features) but the commercial reality is you cant ignore them.

I hope you actually look at the business requirements of your customers before deciding the the irrelevancy of a rendering engine

Reply Parent Score: 5

RE[2]: Comment by ssokolow
by lucas_maximus on Thu 14th Feb 2013 08:12 in reply to "RE: Comment by ssokolow"
lucas_maximus Member since:
2009-08-18

Tell that to 40% of our users.

Reply Parent Score: 2