Google Wave is not dead yet - now at Apache

http://www.waveprotocol.org/

by markokocic • 15 years ago

39 13 15 years ago

I hope they change the interface. The first thing I found odd about Wave, was that it needed a 1 hour demo when they first showed it. That was probably because it was focused towards developers, though, which is another mistake they made.

But I think the UI was 60% of the problem. When I first started using it, my brain started to hurt. They didn't even follow the golden rule. They had 2 same width columns in there. And everything looked cluttered and complex. Not very intuitive at all.

Another issue with it was confusing marketing. They called it e-mail 2.0, when it was nothing like that. People used it more as a collaboration tool. I had to use it every day for 6 months, too, and I didn't like using it at all.

Now, whoever even compares Google+ with Wave and says Google+ might fail the same as Wave, simply doesn't get it. They are worlds apart. From the moment I even saw the video ads, I had the opposite feeling about it than I had about Wave - a very positive feeling. And I keep having it after using it many hours a day.

ChrisArchitect• 15 years ago

to this day I have yet to see any major UI problems -- and I have used Wave alot in real collaboration situations. It has worked excellently for just that, collaboration. Only thing missing is a gTalk chat window/which the original Etherpad has so I will probably move to that as a wave replacement.

lucian1900• 15 years ago

I don't share your feelings about Wave's UI. I quite liked it, with the exception of the scroll bars.

tseabrooks• 15 years ago

I'm a huge fan of Wave's UI and wave in general. My friends and I have used it every day since it's release. We love it and our only complaint is that it is occasionally sluggish.

ddfall• 15 years ago

Yup, been in the Apache Incubator since last year: http://www.h-online.com/open/news/item/Google-Wave-accepted-...

andrewl-hn• 15 years ago

Is Apache becoming a graveyard for dead or dying projects? First OpenOffice and now Google Wave. What's their reasoning behind these moves?

Both Wave and OO.o are fairy complex projects and I'm afraid that the pace of their development will suffer severely without a strong company backing.

JoachimSchipper• 15 years ago

I think the reasoning is that Apache is about the only place where you have a strong open-source community that is acceptable to/has experience with "the enterprise" (see: their various Java projects).

Gorbzel• 15 years ago

Exactly?

Wave, OpenSocial, OpenOffice: a bunch of great open ideas that never got support from their original corporate overlords. So they're dumped into the Apache Incubator, where they die a slow death.

It's really a shame. I remember investigating a project that would have solved a big need I had at the time, but was worried about a couple of bugs. I remember almost going with it, since I had faith that an Apache-backed product wouldn't langish. 18 months later still no commits.

nodata• 15 years ago

Google Wave is dead. Time will tell if Apache resuscitates it.

billpg• 15 years ago

Curious that Apache call it "Google Wave", if it's no longer part of Google. (Or is it?)

belthesar• 15 years ago

Wave isn't dead, period. If you watch traffic sources while accessing Google+, you can see wave.google.com being called. The underlying tech has been incorporated, if only at an API level, in Google+.

d136o• 15 years ago

Has anyone taken a look at Piazzza, the new blackboard type collaborative tool for college classes? I have a strong hunch they're using google wave.

AdamGibbins• 15 years ago

This was announced by Google here: http://www.google.com/support/wave/bin/answer.py?answer=1083...

Google Wave is not dead yet - now at Apache

Related Stories