Re:Geeks Try Google Wave, Have Mixed Feelings
by elblanco on Friday October 02, 2009 @10:40AM
(#857091)
Wave is simply too new. Appropriate conventions, best practices and basic netiquette haven't yet been communally agreed on.
Most of the other problems reviewers have identified appear to be almost purely basic software issues (new or updated waves don't float to the top for example, can't draft a response yet, etc.), things that Google could just silently update tomorrow or next week.
In addition, we've only seen one Wave client. The protocol itself seems sound, but alternate clients could easily solve many of the identified "problems".
The importance of Wave is and always has been the protocol. The client is just an example or reference app.
For myself I'd love to use it to co-author papers and collaboratively write technical specifications and design docs with my (across the continent) colleague.
Most of the other problems reviewers have identified appear to be almost purely basic software issues (new or updated waves don't float to the top for example, can't draft a response yet, etc.), things that Google could just silently update tomorrow or next week.
In addition, we've only seen one Wave client. The protocol itself seems sound, but alternate clients could easily solve many of the identified "problems".
The importance of Wave is and always has been the protocol. The client is just an example or reference app.
For myself I'd love to use it to co-author papers and collaboratively write technical specifications and design docs with my (across the continent) colleague.