Linked by Thom Holwerda on Wed 13th Feb 2013 13:21 UTC
Permalink for comment 552463
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
More News »
Sponsored Links



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.