Doing some exploratory thinking about the possibilities opened by Google Wave, I came up with this very early idea of something that could turn out to be pretty interesting. In explaining it, I’ll assume you’ve watched that huge 1h20min video they have about it (it’s worth every minute, but there’s an abridged — 10min — version).

Motivation

People have been doing code review through email for ages. It’s the easiest, dead-simple way of doing it. Just add a post-receive-hook to your repository and make it email a diff of every new commit to a mailing list. People answer to that email, inlining comments where needed. Great, you say. But… It’s not 2.0. Bummer.

Everyone’s been talking about it: Google Wave. Google’s super communication tool has been a top trend on Twitter, a focus of media speculation, and was even able to knock Microsoft’s Bing from the top of the news cycle. But almost all the hype has been based on the demos - almost nobody’s actually got to try out Google Wave.

Well, thanks to a few of our friends, we had the opportunity today to try out the alpha version of this groundbreaking new service. From creating waves to joining in on discussions, we put the newest Google sensation through the ringer. Does Google Wave stand up to the hype?