Wave is great, but where’s my HTML 5?

The big buzz since yesterday is surrounding Google Wave. After having read a rundown of this thing, I find it to be rather cool. I’m not alone in this as a great many people feel the same way. The best thing is that they stole Microsoft’s thunder over their Bing release, which is always cool.
One of the reasons that I’m rather fond of what Wave is doing is that while doinking around with Facebook’s API and Connect systems, I’ve been a bit lazy to really dig in to them as much as need be. Sure, I know enough to get in there in program up an App, but why? I have nothing on this site that’s worthwhile to spout about. Maneno could maybe use an app, but it’s in its infancy and needs a lot of things before it needs a Facebook App. And this is why I think Wave will be cool in that it will crush Facebook’s proprietary system. It will be open source and do just about everything that Facebook is currently trying to do. I like that. I can get behind that. I can develop for that. Oh, but wait…
Wave is going to need HTML 5 support before it really takes off. As I can see, we’re screwed when it comes to HTML 5 support. Firefox 3.1 has it, but we’re still officially on Firefox 3. Safari 4 in theory has it, so that’s good, although Apple, as super early adopters often crap up standards, so I have a feeling it won’t be until Safari 5 that the support will be trustworthy and 4 still is in beta. Explorer is just out in the cold altogether with not even Explorer 8 having support these days and I hope that this is the think that ends up killing off Explorer use. Lastly, Chrome doesn’t have support in version 2, which is the current version. I find that odd given that Google is pushing Wave, Wave would like to have HTML 5, and Google makes Chrome. I assume that support will shortly be forthcoming.
So, Wave does appear to be the future, but it’s a future we’ll have to wait for. Personally, I’ll be thrilled to not have to use that damned swfobject JavaScript hack to get Flash working correctly on my sites, since the “video” tag will handle. It’s going to be a long day in coming though…