Live data from Hacker News

Save Google Wave

savegooglewave.com

61–65 of 65 posts

Re: Save Google Wave

#62
post #59
post #52

Funny. I wouldn't want to be in Novell's shoes now after having invested in building a product on top of Wave: http://www.novell.com/products/pulse/

Pulse is not in top of Wave and really is a separated product that doesn't depend on Wave at all. And in fact is what a lot of people are asking: Wave behind your firewall. (Disclaimer: I'm a Novell employee but I don't speak for them).

Thanks for the clarification. This blog post is also helpful: http://www.novell.com/prblogs/?p=2836

Re: Save Google Wave

#63
There's nothing left to save. Google has already added collaboration capability into their Documents and Buzz is what they went with for microblogging in their mail app. http://it.toolbox.com/blogs/future-of-work/google-wave-rip-4... goes into 6 reasons why killing off Wave is the right thing to do.

Re: Save Google Wave

#64
post #19
post #3

I know the protocol is a bit complicated, but didn't they say a while back they're going to open source a reference implementation of the server? Is this it?: http://code.google.com/p/wave-protocol/ I do not know if that's a complete Wave server, or if it's missing a piece. But if it is a complete Wave server, there's nothing to "save". It's already been saved. You just need to run it yourself, and possibly support f…

What people want to "save" is Google's backing, proselytization, and continued investment into the project. The demand was never there—because Google never gave Wave a big marketing push, the way they did with, say, Chrome (no Wave TV commercial?) Wave is a new and unadopted protocol, and as such it won't grow organically; it needs a big company to force it down people's throats. People want to "save" the unfulfilled…

Well said!

If a company like Google is not going to invest in such technologies who will. This makes me think if Google is turning into a company which jumps on to a bandwagon once it starts rolling rather than be a creator of new ideas and technologies.

Re: Save Google Wave

#65

The most obvious feature Google should have invested 5,000 man hours in: making Wave seamless in GMail as a standard. If you are talking to another GMail user, Wave should be automatically turned on for that message. I do not understand why this wasn't deathly obvious to them from the day that they announced Wave at Google IO 2009.

One reason this might not have happened is because you don't fuck with gmail. That's 180 million users right there. Repeat: you don't fuck with gmail. (But I would have liked the wave/gmail rollout, yes.)
Post reply on HN