O'Reilly Radar has a piece echoing a common sense of excitement for the collection of standards now traveling under the moniker HTML5. The piece argues that we can "finally" be excited about the web again due to all of the new possibilities that features like canvas, local storage, CSS3, and multi-threaded Javascript engines bring us.
While I too am excited for the promise of HTML5, it seems like the fervor is too much too soon at this point. First of all, it will take a few years to get consistent implementations across all of the browsers, especially when you consider a bear like CSS3 (or even what Microsoft might do). Second, while canvas and the video tags are great ways to finally kill off Flash, they aren't delivering new capabilities per se, since we've had Flash, Silverlight, and Java for years now.
And finally, while I love the idea of HTML5 as the default dev environment for the emerging smartphone ecosystem, it seems hard to believe, when even very prominent open web developers have moved over to the native dev kit for their work projects. Sandboxed though it may be, the iPhone SDK is still a lot more powerful than any approximation from Mobile Safari, and, unlike the desktop, there aren't spare CPU cycles and gigabytes of RAM to spend on a mushrooming web browser process.
Instead of hailing HTML5 as the cure-all, I wonder whether we might not be about to revisit the X-Windows system in a major way. That is, native applications that run virtualized processes on some server when they need to do compute and memory intesive stuff, but which receive a pixel-rich interface over the wire and send back clicks/gestures/keyboard entries. Google's Chrome OS is using an X-Windows replacement which is supposed to be faster and more efficient over the wire, so this may point the way forward.
Then we could have a gradual adoption of HTML5 features for the functionality that is mostly form-driven (looking up restaurants), native apps for games and other interactivity-rich or resource-constrained applications, and this new kind of native shim for running virtual blobs in the cloud for everything else.
While this approach seems like a bit of a throwback, it is worth noting that there are main grey-haired beards from the mainframe era running around (especially where I now work) talking about how the web with it's textual interface and request/response paradigm is really not that different from their VT3270 terminals. So maybe it's time we advanced from the 1950s into the glorious X-Windows 1970s!