@doomlaser - it's interesting to hear the argument put that way, because nothing I use flash for involves video delivery (or very little of it). Video delivery is to flash what hot topic was to...whatever my favorite bands were in 1995. It's the generic mass market application of something arguably meaningful, useful, appealing and capable of changing the world. Below that are the banner ads. But in the middle, it's true, there's this wide audience for streamed video that should have been served by browser technologies long ago, and that Flash really should never have been a part of, except that it filled a void as the only plugin widely enough adopted to support cross-platform video.

The loss of video to native browser technologies takes nothing away from the things Flash has to recommend it as a method for blitting graphics to the screen. It's one thing to try and do it with canvas and divs in Safari -- it's a joke getting things to line up, but it's not impossible. But if you want it to look the same in IE? A guy's supposed to run a startup and worry about Firefox reversioning every 4 weeks at the same time? Realistically, if I wasn't running my app in Flex I wouldn't have a company; I'd have a giant pile of IF IE statements and a bigger list of complaints.

So this clock is where the rubber meets the road, in a funny experimental way. It's got "no flash" in the title, so we can assume this is where an HTML5/JS proponent with some coding savvy thinks the line should be drawn; this is what can be achieved with the technology available cross-browser given the state of the DOM art. And I'm not saying it's bad. I'm just saying that it's nonsensical to throw out good tools to prove you can do something with bad ones.