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 552452
To view parent comment, click here.
To read all comments associated with this story, please click here.
cdude
Member since:
2008-09-21

You still hack browser specific hacks against a certain version and then wonder the break if a new version appears? Why not use one of the many js-frameworks available for that? Then it usually works cause vendors check against them but not against your little webkit-version hack homepage.

Reply Parent Score: 1

Nelson Member since:
2005-11-29

Because this destroys the premise of the unified web that many clamor for (or at least did, when it was IE doing the non-standard BS).

The reason for IE's dominance and subsequent subversion of the standards process isn't really because it wasn't developed in the open, but because it gained enough clout what web developers stopped bothering with anything else.

WebKit and IE are in the exact same situation. It is mildly amusing how many of the blind fanatics don't see it.

But it merely underscores a point a lot of people have been making: The web is fundamentally broken. Design by committee is broken.

This is what a decentralized authority on the direction of the web means to developers. Write multiple times, test everywhere, use a JS framework, and likely shoot yourself.

This is the bullshit that people wish we'd replace our native app platforms for? Ha.

Reply Parent Score: 2

lucas_maximus Member since:
2009-08-18

Nailed IT!

Reply Parent Score: 2

cdude Member since:
2008-09-21

Because


You not answer my question.

This is what a decentralized authority on the direction of the web means to developers. Write multiple times, test everywhere


And it became now one lesser case to test and special case. Good point why Opera dropping Presto and going WebKit is good for us!


use a JS framework


And? You are using JS so why don't you use a JS framework? Why do you or your other mate keepon to add browser-engine and browser-version checks with different code-paths and then wonder it breaks?


This is the bullshit that people wish we'd replace our native app platforms for?


NOBODY but you in all of the threads here wrote something related to that. This isn't about any false claims native apps are dead nobody did. Its about Opera switching from Presto to WebKit.

So, what was your point and how its related?

Edited 2013-02-15 00:53 UTC

Reply Parent Score: 2