Updated October 6, 2010Doc Sheldon
I picked up some interesting chatter on Slashdot tonight, about W3C telling the world not to implement HTML5 on websites, essentially because it doesn’t work across browsers.
I don’t know how many developers are really trying to convert to HTML5 already, but surely there must be some that are. And according to the cross-talk at Slashdot, there’s at least a few that have no intention of holding off, waiting for W3C to work it out in 5 or 6 years.
One comment made was, “Essentially, we are seeing a big beta test of the HTML5 spec”, referring to the present scenario. He went on to say, “It helps ensure what makes it into the spec is what people are actually building sites with and what user’s are actually using, rather than simply what the workgroup thinks people would like”.
Makes a lot of sense, if you ask me. Even if you don’t ask.
It’s unfortunate that there wasn’t a better look taken at it, before it was touted as the next great thing. False starts like this don’t do any industry any favors, particularly one as fraught with knee-jerk reactions as web development.
And I’d be really interested in hearing your comments here.