A commenter on that article pointed to one of the many document sharing sites out there as an alternative. This prompted me to think deeper on why Google Wave has me so intrigued, when there are plenty of collaboration services which I could implement in a way that would meet my needs.
My initial thoughts were - with my subsequent thoughts in italics:
- I'm looking for something to collaborate on docs (ie edit too) not just share them - the commenter pointed to a sharing site;
- Wave is from Google and therefore much more likely to become more pervasive if it succeeds - as a consultant working with an ever changing array of multiple customers and partnering organisations I collect too many systems, UserIDs and passwords as it is, if Google Wave takes off and removes a need for a lot of them (I don't expect it to replace all of them) that would simplify my life and hopefully enable me to deliver value to my customers quicker - rather than being distracted as I often am now by having to learn yet another system with yet another pair of UserID and password credentials;
- because it is designed ground up as an open protocol - very soon other providers will be able to provide Wave servers, and waves will federate among them so it won't be a closed system like too many of the current alternates - as well as the points made in 2 this one is particularly relevant to my work as a consultant working with an ever changing array of multiple customers and partnering organisations - I don't always get to choose which systems I have to work with as my customers, and sometimes my partner organisations, often choose the tools to be used for a particular project - Google Wave offers the potential of using a system that might become as common as email, without the frustrations of email (which are why we are all looking for new options anyway!).
My business partner now has a Google Wave account and I will blog my real world experience of using Google Wave in the context of running our consulting company.