The main point of the article as I read it is that HTML5 is made up of a variety of technologies, which have different levels of completeness and readiness for the general public. To say that HTML5 is not ready to be deployed therefore makes no sense.<p>HTML5 is just a buzz word to describe recent advances in web technology which should be used in the same manner as us web developers have used web technologies for many years: consider the target audience and provide adequate fallback mechanisms if necessary.
the amount of people that do not understand that html5 is not a point release is depressing, under the same rules that disregard html5, ajax/xhr isnt ready for the big time yet.
HTML5 is not one cohesive thing, so it's hard to make a blanket generalization about it like "it's not ready to use".<p>Refer to <a href="http://diveintohtml5.org/introduction.html" rel="nofollow">http://diveintohtml5.org/introduction.html</a>
<a href="http://validator.w3.org/" rel="nofollow">http://validator.w3.org/</a> has an entry for HTML5 (Experimental)<p>I don't know if that means the validator or HTML5!<p>Then BOFH's can brush everyone off with
"The site is valid Nhtml, please contact your vendor regarding this issue"