Google Wave Out of Beta 255
googlePLEXS writes "Google Wave is open to all users at wave.google.com, as a Google Labs product — no invitation needed. Google Apps administrators will also have the option to add Wave as a Labs feature for their domains, helping groups of people communicate and work together more productively." If you haven't played with it, it's worth your time just to try to think beyond the bounds of IRC/Email. It's not going to change your work flow, but I still think it's worth a bit of your time to see it.
Re:Heh... (Score:4, Insightful)
Re:No email integration (Score:3, Insightful)
The Wave is a federated protocol. You could easily write an email gateway.
But Google themselves should do it, I agree.
Re:So why should I care? (Score:5, Insightful)
I can already send data through the US Postal Service, so what exactly makes email worth my time?
Re:Great! (Score:3, Insightful)
Moreover, just because it can be, it does not mean it actually IS.
Wake me up when someone has built an interesting application/solution using the Wave platform.
So far I see a bunch of applications that are nothing more than gimmicks.
Re:No email integration (Score:3, Insightful)
Re:No email integration (Score:2, Insightful)
You miss the point: Wave should include email functionality so that people have a "one stop shop" not waves should be forwarded to email to read.
Re:No email integration (Score:3, Insightful)
No email integration == no future for wave.
Why would wave integrate with email? Or, rather, in what way do you think it should?
IRC doesn't integrate with email. AIM doesn't integrate with email. HTTP doesn't integrate with email. BitTorrent doesn't integrate with email.
Wave is a new protocol. It isn't really supposed to replace email. It's supposed to be a different way to communicate and collaborate. Somewhere between Microsoft Word and WebEx.
Comment removed (Score:3, Insightful)
extensions? (Score:3, Insightful)
But what you wind up with is something that looks like an interactive chat session - you can put together ideas that way but there's no structure to the end result
Isn't that where extensions would come in? I'd prefer that Wave itself not define what an end product would be and impose that on me.
Re:Dupe? (Score:3, Insightful)
Re:Great! (Score:3, Insightful)
I just don't think people should dismiss it; I understand people not using it, which is a chicken and egg problem Google need to figure out and probably won't figure out, but don't dismiss it out of hand.
Re:So why should I care? (Score:2, Insightful)
Just like there are advantages to email over postal mail (speed, ability to easily send to multiple people, etc), there are advantages to Wave over email (the ability to see what the others are saying as they type, gadgets and robots that can be embedded into the Wave, etc).
People seem to be dismissing it before actually checking it out just because what they have seems good enough. That kind of thinking is not really good for technology.
Great but nobody still knows what to do with it? (Score:2, Insightful)
Re:why you might care (Score:3, Insightful)
Somehow I had the misconception that all API data went through Google. My mistake. Thank you for clarifying! :)