Crap. How can I host my own?
Google Kills Wave
81–90 of 246 posts
Re: Google Kills Wave
#82When more people say "I tried it, haven't really used it though" than "I use it regularly" you know your product has failed.
You could say that about Twitter, though, and it's difficult to find anyone today who considers Twitter a failure.
Re: Google Kills Wave
#83I liked it, just didn't like the interface. I was an early adopter and very excited about the protocol. When I was looking at it, there wasn't enough client specification to bother working on an alternative client (ie: emacs). Hopefully that has changed (or will change before Google drops support).
I found it really useful for collaborating with multiple parties. It allowed us to work on a document and keep the conversation all in one place yet clearly separated. Sometimes email can make that distinction difficult or unclear.
At least it's not entirely closed source. :)
Re: Google Kills Wave
#84It 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…
Just an FYI, sometime in the past few months they implemented email notifications.
Re: Google Kills Wave
#85You can't make people solve problems they don't have. If Google failed with the Hype Winds at their backs, then I doubt anybody can do it.
While I agree that a large part of the blame for Wave's failure falls on Google, I think its hard to make the case that it "solve[s] problems [people] don't have".
Anyone who's ever dealt with the horror of a multi-user email thread (>>>>>This sort of thing, or perhaps "My_Doc_CASEY'sVERSION.doc")knows that Wave at least solves that problem fairly well.
Of course, no one really cares about that if you can't get your whole team onto Wave in the first place.
Re: Google Kills Wave
#86Wave may have been an idea whose time is yet to come. When I played around with the beta my brother and I agreed that it was too slow to be useful. That was the last time I touched it. This was mostly because I was working in a company where getting people to document was enough of a difficulty without introducing new software. If I'd worked somewhere with a bunch of early-adopters, it would have been a fantastic too…
> When I played around with the beta my brother and I agreed that it was too slow to be useful. That was the last time I touched it. Slow? I can only assume people who said this weren't using the latest FF or Chrome. I've never considered Wave slow at all.
At the beginning, on Firefox, it was soul-deadeningly slow.
Re: Google Kills Wave
#87Earlier quoted context omitted.
I still miss etherpad. I use some of the alternatives, but it's not the same :( alternatives: http://etherpad.org/etherpadsites.html
Google Docs seems to support a very Etherpad-like interface, but it's a little too bloated for what I used to use Etherpad for.
A while ago Google Docs even switched to using Etherpad-style operational transformation instead of diff-match-patch. Some pretty mind-bending technology here:
http://www.codecommit.com/blog/java/understanding-and-applyi...
Re: Google Kills Wave
#88Earlier quoted context omitted.
I still miss etherpad. I use some of the alternatives, but it's not the same :( alternatives: http://etherpad.org/etherpadsites.html
Google docs is very similar to what etherpad used to be. All be it far less user friendly you can watch others edit and update in real time.
There's two main differences for me.
a) It takes some work to create a new Google doc and set it up for sharing. Etherpad was as simple as pasting the URL.
b) Etherpad shows changes from different users with a different background color. Google Docs is invisible.
Re: Google Kills Wave
#89It 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…
it's not like twitter ever sends/sent an email when someone you follow tweets.
Twitter is ephemeral. You can quite easily leave it for a month and miss nothing important. Nobody will care, nobody will miss you. Twitter will continue to function as long as people have egos, which is to say forever. (not trying to bash twitter here even though it sounds like it.)
Wave is quite different. It's designed for conversations and collaboration. In order for it to function, users need to be able to know when the other has responded quite quickly. Wave itself does nothing to ensure this.
Re: Google Kills Wave
#90It 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…
agreed. if this had been integrated as a new type of message in gmail that had some interoperability with regular email, I think the results here would've been completely different. google never gave wave a fighting chance.