<i>Wave didn't wash outside a few early adopters like Novel, SAP, and, er, the US Navy, and it looks like Google's still having trouble conveying exactly what Wave is and what it does.</i><p>Just wondering what the plans of these early adopters are. You can't make money off something if nobody uses it. Isn't this why Google scrubbed the project in the first place?<p>Don't get me wrong. I think that Wave is/was an interesting project and I tried really hard to use it, I really did. But somehow email/IM/whatever was always faster and more practical, in the sense that people responded to my requests. When using Wave I always had to remember people: "It's in Wave", "Haven't you checked Wave?"...<p>I, and the other people I worked with, just couldn't get Wave into our workflow and someday we just forgot about it completely.<p>It would be really interesting how the Navy uses Wave and for what. A kind of best-practice report on how to use Wave productively would be very interesting and motivating (at least for me). Tell me how to use it and I'm ready to give it another shot.
Wave was a paradigm shift with too many paradigms.<p>Had they integrated only the functionality you could find in etherpad into Gmail the story would have been very different IMHO.
I have been really happy with wave and would like to thank Google for releasing it. I am sure they use it internally, and will keep using it at Google in 2011. Although, they might have something better going on.<p>Kind of reminds me of Google Answers that they closed down (I think prematurely,) which was in a segment that is and has become highly demanded.