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.
Surely it's OK to deploy anything that works acceptably for your audience. With sensible fallbacks and graceful degradation there is very little downside to using 'bleeding edge' features.
Most of html5 and related standards have been constructed with careful attention of backwards compatibility.
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.
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.
8 comments
[ 4.4 ms ] story [ 31.6 ms ] threadMost of html5 and related standards have been constructed with careful attention of backwards compatibility.
Refer to http://diveintohtml5.org/introduction.html
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.
I don't know if that means the validator or HTML5!
Then BOFH's can brush everyone off with "The site is valid Nhtml, please contact your vendor regarding this issue"
Seriously now, alot of the standard is fairly stable and can be used.