Welcome to the second decade of the 21st century. As we usher in a new year, it feels appropriate to discuss new and exciting technologies, so we shall turn our sober attention to HTML5.
While we’re on the subject, let’s dispatch a few other myths and misunderstandings regarding HTML5:
As of this writing, HTML5 is only just ready for implementation on most mainstream websites. The primary reason for this is that no browser yet supports the complete HTML5 spec (although some, such as IE 10 and Chrome, get very close).
HTML5 is not yet a done deal: while most of the specification is nailed down, there are aspects that are still open to interpretation. This makes some HTML5 modules a moving target, just as CSS3 is. This may mean more revisions for a site coded in HTML5 as the specification changes.
HTML5 does not replace XHTML, or make it obsolete. The two languages will be used alternatively (and in some cases, side-by-side) for at least the next five years. The lessons and habits you learned in XHTML are still entirely applicable to HTML5. HTML5 expands and improves upon XHTML; it does not kill it.
If this is the current state of play, why are we learning HTML5?
Employers will be looking for knowledge and skills in the language (even if they are not yet clear on how it may be applicable to their business).
If you are making a website that will primarily be interacted with on smart mobile devices, such as iPhones, Android, Palm Pre and recent Blackberries, HTML5 may be a very good strategic decision: the browsers on those devices (mobile Safari and Opera) have strong support for HTML5. (Naturally, Windows Mobile does not do so natively).
localStorage, forms and audio-video.
Before we start into what is different about HTML5, it might be instructive to take a moment to ponder how we got here, and answer a few questions: what happened to XHTML2? How was development of the language taken from the W3C? And where is the role of XML in all of this?