My friend Jon sent me an invite for Google Wave a few weeks ago. The hype behind this online collaboration tool is that it serves as an alternative to email. In a way, this platform serves almost like a wiki, in which multiple participants can embed content to be distributed to any or all of the members of a ‘wave’.

The confusing aspect of this framework is that most users are accustomed to a linear conversation. We chat via instant messenger in a linear approach, as in emails. With a tree framework, certain topics can branch out into subtopics. The root topics/discussions can also be revised on a later date. This translates into an evolving topic, which potentially keeps old topics accessible.

This idea is not novel to the programming crowd. Version systems a la CVS have been around for decades to maintain proper updates on software. The problem with applying this to laypeople collaboration is that it’s a new system to learn. Given that Wave is still in an invite-only interfact with limited functionality, I don’t see myself collaborating much with my coworkers/peers anytime soon, unless I can muster up some more invites.

In the meantime, you can read “The Complete Guide to Wave” online to get up to speed, written by one of the Lifehacker editors.

computing tech