using HTML5? So stop it. At least for now. The HTML 5 is still early! About in this sense sounds InfoWorld interview yesterday with Philippe Le Hégaret from the W3C. He quoted more and more media and the Internet begins to spread. And with him the spread misunderstanding. So what's the Philippe from the W3C will actually say? And why? I'll try to explain it. After the bucket.
There is nothing new. Basically it is a different view of the complete specification between those specifications are, and those who use it. Going on three years ago, when the author HTML5 Ian Hickson said that HTML5 completed sometime in 2022 .
whole world when tapped on the forehead. Fifteen years? It really is not done before?
Ian responded to this: You start using it a lot earlier, but for us it will be done until around the 2022nd (For more detail see What about the completion date of the HTML5? of 2007)
He was right. Three years have passed (no fifteen!) And seems to really start using HTML5. Someone this year, maybe another year or two, but basically the issue today. (At least Web site content to use it already for some time on Friday and might not even know about.)
From HTML5 became Buzzword signifying progress and the company is showing off in his inflection on their presentations.
reality, however, remained unchanged. To complete the HTML5 will really be a great many more years (maybe the 10), like CSS2 is still not finished. (Surprised? It really is not!) That it is a different understanding of the completed specifications. And from this perspective, the W3C Philippe truth when notes that HTML5 is not yet finished, it is not quite ready yet.
And something that matters? It may be a problem?
the truth. It does not, but it can. With such a rapid move forward without looking left and right may appear smaller or larger problem. This most famous and largest problem, which in the past for exactly this reason occurred bifurcate the box model. Who do
sites a few years, remember a different box model of Internet Explorer and other browsers? Minor mistake, for which one blames Microsoft, the other W3C, but the truth is that the victim was a rapid progress. This "minor procedural bug" then a good ten years, an irritant to the millions of web developers.
similar errors with a similarly large impact can occur even today. And that is what we Philippe from the W3C is trying to say.
not for nothing that says that progress requires sacrifice. Fortunately, we have come to patch up similar problems in different frameworks. It would be the person mind, if there be 5 different incompatible APIs for HTML 5 when it could use a JS framework, for which he will resolve those differences?
So we can say that today time is ready to face similar problems better than the time some 10 years ago.
therefore have no choice but to Philippe W3C note, thank you for the warning, but we just against chance.
