That is distributed through video. There are closs-platform ways of distributing video. I feel that does the job pretty good, and certainly better than "shit".
If I go to the cinema and watch a Pixar movie, I'm quite content that they pre-rendered the thing very expensively at Pixar and I'm watching something that is limited in resolution, but much cheaper to distribute and reproduce: I feel it's OK that the web manages to reproduce that same experience pretty well.
You're totally ignoring the fact that we've got near film-quality, interactive 3D animations, running at 30 to 30 frames per second on 10 year old hardware collecting dust in people's living rooms.
Meanwhile, this simple animation isn't quite getting the minimum 24 frames per second when run full screened on my 30 inch monitor powered by a brand new MacBook Pro.
The thing is, it uses quite a lot CPU power for what it does (and no, it's not "technical issues" with individual systems: it tends to do so in general in every system), and the animation isn't always smooth and far from 60fps.
And the suggestion that he's "using a browser that doesn't properly support some of the required CSS3 features" only reinforces his point, that when it comes to web technology it's a large step backwards from what we can achieve in native systems.
If anything, demos like this serve more to demonstrate the capabilities of the system to people who may not be aware such things are even possible, not the best practices. This wasn't possible a few years ago in this way, period - now it is. Isn't that interesting and/or useful to know?
Jiggling the handle to get these things to work seems like it will be around for quite a while