Live data from Hacker News

Google Kills Wave

googleblog.blogspot.com

171–180 of 246 posts

Re: Google Kills Wave

#171
Is it just me or is the source not easily discoverable? I found the wave protocol sources, but i can't really find the individual components. If anyone could point me to the right repo it would be much appreciated!

Re: Google Kills Wave

#172
post #161
post #12

Wave has not seen the user adoption we would have liked. Did Google believe that this was going to succeed as a consumer product, à la Facebook? Wave, as it exists today, is a great tool for corporate communications. With the right interfaces, integration, and extensions it could definitely displace Exchange and Lotus Notes. Eventually, as a protocol, it had the potential to transcend email. Maybe Google just hoped W…

Wave, as it exists today, is a great tool for corporate communications. With the right interfaces, integration, and extensions it could definitely displace Exchange and Lotus Notes. Aren't these two sentences contradictory? 'Wave is a great product if you changed the interface, integration points and, really, if it was a different product'. I think there's a tendency to over-analyze the reasons Wave was not a success…

Whatever the merits of the over-arching idea, the actual implementation and the thing you got to use, frankly, blew. An interesting technology demo, maybe but as an actual product it was a horrendous, inscrutable, clunky mess. [] This remains true despite the fact that there exist a few merry bands of hyper-intelligent and/or masochistic mutants who have managed to get some use out of it.

I think you've just described >50% of all software.

Re: Google Kills Wave

#173
post #137
post #65

If Wave was launched with the Gmail integration of Buzz I think we would be discussing a completely different outcome.

Is buzz doing any better?

I think the problem is two-fold both with Buzz and Wave. First the implementation and the adoption.

I think Wave idea is awesome, but their implementation (and performance) has been always an issue. My communication is already fragmented over so many places I don't want another domain for another form of communication. They should have added wave into Gmail by default. Wave always had horrible performance issues (still does).

Buzz doesn't solve any communication problem that I can't use it on any other popular services. So Buzz adoption doesn't make sense to me whether its integrated to Gmail or not.

Buzz is a "me too" product. Wave was not.

Re: Google Kills Wave

#174
post #161

Earlier quoted context omitted.

Wave, as it exists today, is a great tool for corporate communications. With the right interfaces, integration, and extensions it could definitely displace Exchange and Lotus Notes. Aren't these two sentences contradictory? 'Wave is a great product if you changed the interface, integration points and, really, if it was a different product'. I think there's a tendency to over-analyze the reasons Wave was not a success…

Whatever the merits of the over-arching idea, the actual implementation and the thing you got to use, frankly, blew. An interesting technology demo, maybe but as an actual product it was a horrendous, inscrutable, clunky mess. [] This remains true despite the fact that there exist a few merry bands of hyper-intelligent and/or masochistic mutants who have managed to get some use out of it. I think you've just describe…

Or more. But most software doesn't get the coverage Google Wave had. We tend not to theorize at length why obviously terrible software fails, we just say 'oh that thing? yeah it sucked' and move on. I'm just making a simple point - Wave wasn't successful because it wasn't very good.

Re: Google Kills Wave

#175
It seems that at their scale, Google doesn't bother to (is unable to?) evolve individual products, rather they pivot by launching and killing entire projects.

The same thing happened with Google's 3D world product, Lively, and the following comparison of Lively with IMVU by Eric Ries is pertinent:

"By the time they [Google] actually managed to launch something, they were building the product that we had already discovered was not the right product 100 iterations ago.

"But they launched it with such high fanfare and expectations; they were so convinced they got it right, that it was actually the mismatch between the expectations that Google--one of the most public companies in the world--put behind this product, and then its pathetic results...

"The product wasn't a bad product and it's not like nobody wanted to use it (of course they wanted to use it for stuff that embarrassed Google) but it was the mismatch that really caused them to have to pull it; it was very embarrassing for them...

"Even after they launched they really didn't give it enough time to learn and iterate because they had set the wrong expectations, a classic big-company [inaudible]."

[http://venturehacks.com/articles/lean-startup -- starting at 6:35 in the audio]

Re: Google Kills Wave

#176
post #15
post #4

I feel bad for the Etherpad guys, who as I understand it, sold AppJet to Google to work on Google Wave: http://news.ycombinator.com/item?id=977015

I still miss etherpad. I use some of the alternatives, but it's not the same :( alternatives: http://etherpad.org/etherpadsites.html

They released the code, host your own (I have a friend who does):

http://github.com/ether/pad/tarball/master

Re: Google Kills Wave

#177
post #12

Wave has not seen the user adoption we would have liked. Did Google believe that this was going to succeed as a consumer product, à la Facebook? Wave, as it exists today, is a great tool for corporate communications. With the right interfaces, integration, and extensions it could definitely displace Exchange and Lotus Notes. Eventually, as a protocol, it had the potential to transcend email. Maybe Google just hoped W…

When they got the right interfaces, integration and extensions they will re-release it as another tool (It will be another tool then).

Re: Google Kills Wave

#179
google wave is dead because of google.

google provided limited accounts and google wave requests was being sold, so the hype got created.

overcommit and underdelivery, 2009 was not 2004, gmail style launch for wave was the first nail in the coffin

though you have your account, your friends dont, you were waiting alone, it was not the realtime communications I expected. what do I do, leave google wave, this has happened with so many people whom I know.

Post reply on HN