My big problem with the state of web programming at the moment is that people are generating these examples which, despite being based on "standards", are virtually worthless to anyone much outside of nightly build users. Some of these "standards" (i.e. WebSockets) are so ill-concived that they get rolled into one browser release, before being rolled out of the next when found to be flawed. These things are not "standards" - they're browser makers playing around with ideas. Similarly, this example (whilst cool) is not CSS3 - it's CSS 3 plus selection of other supra-bleeding edge stuff that wasn't needed to demonstrate the issue.
Whilst I generally applaud using cutting edge technologies, the entire point of the web (to me) is interoperability. As we seem to move more and more towards "This works fine if you're in Chrome, others may vary", I'm claiming that this is not the web any more than "You need Java 1.X.Y" or "Viewed best in IE 6" was. It's a custom delivery platform for content that happens to piggy-back on HTML, draped in a guise respectability via rushed out and hacked together concepts that many will never implement (as by the time someone's finally got around to doing it, they're onto v(X + 3) of the "standard").
Sigh, I sound about 30 years older than I am. However, having been involved in real standardisation where we strive to create something stable and reusable, these types of examples make HTML 5 look a melange of disparate and barely interoperable concepts. This is not intended as specific slight to the creator of this stuff - it's a cool and admitted hack. It's more a mild rant on the state of web development and the disconect between the technorati and people who actually try and create; not even things for the IE6 users - things for users of browsers less than than 6 months old (and possibly more than 6 months into the future of the browser it currently works on).