That is so not true. HTML5 is not buggy at all.
Agreed; Chaos123x probably actually meant to say that certain web browser' support for HTML5 may be buggy as hell. Specifically in reference to Internet Explorer, given the fact that Microsoft hasn't put any effort into supporting HTML5 at all yet, it should come as no surprise to anybody that websites designed around HTML5 don't work correctly in IE.
That doesn't say anything about whether or not HTML5 is inherently buggy, it's simply an observation of the level of some software vendors' adoption of HTML5.
To be fair though, HTML5 is not actually a ratified Web standard yet, so it may change before it is officially adopted. Thus, anyone's claims of support for it must be interpreted as "interim" or "beta" at best. Ratification might happen this year, or perhaps in 2011 at the latest.
And you don't have to mess with codecs, a browser that supports HTML5 will already have the correct codec installed with the browser.
Not necessarily. As pointed out previously, HTML5 in its current form doesn't say anything about the codec, so different browsers have adopted different codecs so far.
As long as this situation persists, we'll be left with at least two different camps on the codec issue, each with largely valid and correct interpretations of HTML5, but neither of which will properly render content which was coded for the the other camp's browsers.
Right now the only major browser that "does it all" is Google Chrome, which supports both H.264
and OGG Theora in its <video> tags.
Maybe the browsers' plugin architecture could be used to install support for additional codecs in the back-end, while still maintaining a clean, consistent <video> tag at the front-end.
