Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The examples you listed died because of marketing, more than technology.

Wave was essentially a social network that your friends couldn't get invites for if they wanted. It was a hugely hyped ghost-town. Wave was a tech preview because it was ungodly slow and made some questionable UX decisions (like badly reimplementing the scroll bar) - Google would have been embarrassed to call it a fully-fledged product. At the same time, they hyped it up like one, which led many people to pass judgement on it too soon, while the ones who wanted to use it either couldn't get access or didn't know anyone who had access to write to.

webOS, from everything I've heard, was quite good. Unfortunately, the history of Palm didn't leave them enough resources to grow it organically - it was a high pressure do-or-die launch with rushed hardware that was universally panned. They didn't have enough resources to wait for good hardware to pair with it. They also banked on Verizon covering the marketing budget, but Verizon famously used Motorola's Milestone to launch the DROID brand instead. (There's a really interesting article from the Verge about it.)

I don't know enough about Linux or Zune to comment on those, but you got excited about webOS and Wave because you saw the promise of the vision. The execution is what bungled both.



Google Wave didn't die because of marketing.

It died because it was sloooooooooooooooooooooooooooooooow.


My problem with Wave was not that it was slow, but that it made me feel slow. I never got my head around the concept - I was never sure what it was trying to do, or why you would want to use it to do that. It felt like a tool designed by super-geniuses for other super-geniuses, something I was just too dumb to understand. I've heard many people say things like that about various computing-related technologies over the years, but Wave was the first time I could actually relate to it.


I thought Wave sounded amazing when it was first announced. When I finally got an invite to it, I have to admit, I was deeply underwhelmed with the user-facing implementation. It's probably the slowest, least responsive, web app I've ever used. It also felt way over engineered, with far too many unrefined ideas crammed into it.

That being said, I ended up being a big fan of it, hoping Google would eventually get around to fixing some of the obvious issues (they mostly didn't, though it did get slightly more responsive before it died).

Why was I fan? I didn't think of Wave as a thing to do, like Twitter (you tweet), or Facebook (you friend and post), or a blog (you write a journal)...there never was a way to "Wave", just like there isn't one way to "e-mail". It was just a new set of communication tools that you could assemble however you wanted.

It's no different than using e-mail to plan a party in one case or send photos to your mom in another case or applying for a job in another. E-mail is just a tool, the use-cases fall out of how you use that tool.

For some reason Wave seemed to look like a solution in search of a problem, but I ended up finding several existing things that were better solved in Wave than with the existing workflows. The most notable was organizing a group around collaboratively writing a large document. Structured correctly and the work just kind of "fell out".

The mistake with trying to use Wave was always in trying to use all of the features in Wave.

I really miss it and am very glad to see bits and pieces of the idea slowly percolating into other Google products (Drive for example).


Exactly that. I never understood what wave was supposed to do when it was released with much fanfare.

And I was at google then :-(


It died because even techies couldn't figure it out


It died because it denied the way human communication actually works.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: