Google Kills Wave • Hacker News Board

Re: Google Kills Wave

#71

Post by brown9-2 » Wed, Aug 04, 2010, 9:50 PM UTC

kenjackson wrote: post #30

evansolomon wrote: post #28

Earlier quoted context omitted.

They launched Wave in May of 2009. It's not like they yanked it all that quickly.

Microsoft announced, then released, spent $250M on advertising, and then killed a new phone in that time.

To be fair, Google did the same thing in the same time frame with the Nexus One, minus the ad budget.

Sometimes disrupting existing markets and paradigms takes time, patience, and several iterations.

(I'm still disappointed at how quickly they stopped the direct-sale idea with the Nexus One)

Re: Google Kills Wave

#72

Post by DTrejo » Wed, Aug 04, 2010, 9:51 PM UTC

spydez wrote: post #24

zandorg wrote: post #3

They blew it big time by hyping it for RPGs, which never went anywhere. Get the RPGers on board, perhaps, and you can succeed.

My little group of friends is using it for a DnD RPG. It's orders of magnitude better than the IRC chatroom we were using before. It's going to be annoying having to go back to IRC.

http://pygowave.net/

Re: Google Kills Wave

#73

Post by DotSauce » Wed, Aug 04, 2010, 9:53 PM UTC

vidar wrote: post #62

Everything that distracts from Google Me is obviously being shut down.

I don't know what other services you're referring to, but that was my first thought.

Re: Google Kills Wave

#74

Post by pgbovine » Wed, Aug 04, 2010, 9:53 PM UTC

BobbyH wrote: 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

who as I understand it, sold AppJet to Google to work on Google Wave

somehow i don't think they need your sympathies ... they probably got a decent amount of money from their acquisition, so they're probably not crying right now ;)

Re: Google Kills Wave

#75

Post by j_baker » Wed, Aug 04, 2010, 9:53 PM UTC

I wanted to like wave. It just always seemed like a solution looking for a problem.

Re: Google Kills Wave

#76

Post by shikhar » Wed, Aug 04, 2010, 9:54 PM UTC

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…

it's not like twitter ever sends/sent an email when someone you follow tweets.

Re: Google Kills Wave

#77

Post by ig1 » Wed, Aug 04, 2010, 9:56 PM UTC

Given there seems to be real demand for this product, it may well be an opportunity for a startup to build a competitor.

Re: Google Kills Wave

#78

Post by runT1ME » Wed, Aug 04, 2010, 9:57 PM UTC

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…

You pose an interesting problem. It was (eventually) supposed to replace email, so I'm assuming it was envisioned everyone would check wave every day, or have it constantly open, etc.

Except it hadn't replaced email, so would the better alternative been to have Wave spam your email with updates? Seems kind of hypocritical..

Re: Google Kills Wave

#79

Post by pjscott » Wed, Aug 04, 2010, 9:57 PM UTC

wmf wrote: post #70

tessro wrote: post #36

Earlier quoted context omitted.

All the protocols were open-sourced as part of the initiative. I think they envisioned a world in which inside-the-wall installations existed in the same way the companies have Exchange servers today.

Except Microsoft is willing to sell you Exchange Server but Google wasn't willing to sell you a Wave server. Writing your own is very difficult; no one has managed to match Google's implementation.

Do you know what the problems are that make Wave servers hard to write? I'm writing something similar right now, and if there are enormous problems coming up, it would be nice to know about them now.

Re: Google Kills Wave

#80

Post by c1sc0 » Wed, Aug 04, 2010, 9:58 PM UTC

This makes me feel a little better about the time when I sat on tons of invites & never really got around to using Wave. I'm one of those who never grokked wave.