Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google Kills Wave

googleblog.blogspot.com

Post reply on HN
Print view View original

121–130 of 246 posts

Re: Google Kills Wave

#121

Post by commandar »

roc wrote: post #69
StavrosK wrote: post #14

Earlier quoted context omitted.

I blame it on never understanding the UI, the way it did things, or its usefulness. It's like a chat you can't delete things from, and everyone sees what you type and all your mistakes? And you can post pictures? I just don't get it.

The incredibly powerful, federated, open protocol/platform was what excited us geeks. The client always sucked and was, at the most generous, a tech demo of things the protocol/platform was capable of.

And the problem is that the client is what Google marketed.

The client should have been nothing but a tech demo. The potential power of Wave was in that it could move totally arbitrary data between independently federated servers, and had support for robots that could manipulate that data in arbitrary ways.

It could have been a Facebook/Twitter/Flicker/Whatever killer, but Google got tied down with working on the bloated UI rather than building out the platform and letting others handle the frontend of it.

Re: Google Kills Wave

#125

Post by ekidd »

thorax wrote: post #46
tc wrote: 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…

We use it exclusively for our meeting status reports, etc. It's just a wicked solid tool for meetings and out-of-band document collaboration. I'd love to see it continue. I'm sad it didn't get the adoption they wanted, but I also wonder what they expected when they didn't even really try to integrate it with GMail. If they could go back and time, exclude Buzz from Gmail but instead add Wave, I think they'd have bette…

I agree. We use Wave for all kinds of communication in our startup, and it's just an amazing tool for small workgroup communications and document drafting.

I'm actually rather peeved it's going away, because (1) I don't want to waste a bunch of time trying to migrate data out of Wave, and (2) there really isn't much out there that can replace Wave in our workflow. We use Wave as a GUI-editable wiki where documents gracefully age out of view, and it's just great for that. I'm really going to miss it.

Re: Google Kills Wave

#126

Post by rwhitman »

thorax wrote: post #46
tc wrote: 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…

We use it exclusively for our meeting status reports, etc. It's just a wicked solid tool for meetings and out-of-band document collaboration. I'd love to see it continue. I'm sad it didn't get the adoption they wanted, but I also wonder what they expected when they didn't even really try to integrate it with GMail. If they could go back and time, exclude Buzz from Gmail but instead add Wave, I think they'd have bette…

Yea I just recently got into using it heavily with my remote devs and it has rocked my world.

Really bummed out about this. But then again when Google "kills" something they rarely pull the plug completely.. it either stays in limbo indefinitely or evolves into something else

Re: Google Kills Wave

#127

Post by ritonlajoie »

in two words : It was a good idea, but badly implemented. I'm not telling I would have done a better job than their engineers, but just have a look at the slow interface they made, and you will get my point..

Re: Google Kills Wave

#128

Post by SandB0x »

alextgordon wrote: post #42

It failed because it was completely invisible. Facebook spams your inbox. They make sure you know that you have an account and that people are trying to reach you (or tell the world about their cat, etc). With wave, it's silent. There was activity on a wave I was following in January. I found out about it in March. Someone replied to something I said on July 21st. I'm only just finding out now . What kind of a commun…

They should have added a small but visible "new blip" icon to Gmail. That would have gone a long way, and nobody would have complained about spamming.

Re: Google Kills Wave

#130

Post by siglesias »

Wave was simply over-developed internally, and by the time it was released it had evolved an esoteric, private feature set and interface that had suited the Google beta testers. I for one was simply bewildered by the interface and found it difficult to incorporate into my workflow.
Post reply on HN