News for hackers. Stuff that matters.
Re:Web Standards by voyou on Friday February 10, 2012 @06:28PM (#3577973)
I don't really understand this objection. Sure, HTML 5 isn't officially a standard, but neither is -webkit-whatever; in both cases, you can use whichever non-standard you like, subject to browser support. The advantage of the W3C draft is that it is a non-standard that the browser makers are all working towards.
Re:Web Standards by tjogin on Saturday February 11, 2012 @09:14AM (#3579267)
The objection is that the standardization process is too slow. Not a little bit too slow, but so glacially slow it's almost indistinguishable from abandonment. So, progress of key web technologies needs to be put into vendors's hands.

CSS border-radius is still not a W3C recommendation. It's been a draft for nine and a half years. So far. It was last updated one year ago.

With a standardization process that broken, vendors need to take things into their own hands, and them doing so, especially webkit doing so, has been an astounding success, IMHO.

Re:Web Standards by voyou on Saturday February 11, 2012 @04:03PM (#3580149)
Yes, but why does it matter that the standardization process is slow? What is the practical relevance of something moving from "Candidate Recommendation" to "Recommendation" status? Why are draft standards any worse than vendor extensions?
Re:Web Standards by tjogin on Sunday February 12, 2012 @04:48AM (#3581482)
Prefixed attributes bring features to developers while they are still experimental, which means we don't have to wait a decade before trying them out.