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





Member since:
2005-07-08
How does it help?
Right now we have a code base with browser specific hacks for:
- Safari on Windows
- Safari on MacOS X
- Mobile Safari
- Chrome
All using different versions of Webkit.
How does Webkit being open fix the bugs between those browsers?