Hi, I just discovered "wave" via the video of the 2009 Google I/O. It looked super duper but then I discovered that it has been -- what? -- abandoned? slowed down? It is a little bewildering to me why. If Google is open to feedback on this matter, I'd like to speak up. The wave concept(s) look very promising and exciting. I saw someone say it was too complex but that seems like a rather lame reason.
But, what I want to ask if this: it appears that WIAB is "alpha" stage. I *thought* I wanted to set up a wave server internal to our company and try and use it for a tool to help collaboration and teaming. We've tried email, forums, IRC, etc. They all have some problem somehow. The "wave" concept looked very attractive for a number of reasons. My question is, should I or not? Is WIAB too immature to be used as a tool? I'm a pretty good programmer but don't know Java at all -- I'm a Ruby fan and my bread and butter is in C. Sounds like most (all) of WIAB is in Java. The robots and those features are not my primary interest. My primary interest is the idea of a "chat" (like IM) but with history and state so that I can reply to someone who is not online and they will see it when they log in. Also, the idea of threaded chats is really interesting. These would not be "important" -- so if it crashed or whatever, that would be no big deal. Thank you for your help, Perry -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
