I have played with Wave myself, and here's my initial impressions of it: It's cool, but for a conversation, it simply sucks.
Where I work, we use thin clients (and I hate it, but that's another rant for another day). Anytime I load up a wave with more than about 15 entries in it, the entire interface slows down to an unusable crawl while it replays the history. When it's used in a similar fashion to an IM session, where replies go back and forth, the specific wave must be kept open, or the whole system becomes horridly unusable for IM. Finally, what Wave seems best for is collaborative document editing. If you want to develop some sort of document to help guide people through something, Wave is a good choice. A group of people can work on separate segments simultaneously, and that seems to work well. But for changing the face of communication amongst developers? I've got to disagree with using it. Wave does not seem to be a good choice for that, not to my mind. Unfortunately, I don't have anything better as a suggestion. On Tue, Dec 1, 2009 at 12:52 PM, Derick Eisenhardt < [email protected]> wrote: > Well, if you guys would like to experiment with it, I've got a few > invites lying around (regular developers only) ;) > > On Dec 1, 9:49 am, "Diez B. Roggisch" <[email protected]> wrote: > > On Tuesday 01 December 2009 15:58:57 Christopher Arndt wrote: > > > > > Diez B. Roggisch schrieb: > > > > Having just been invited to Google's new cool kid on the block, Wave, > I > > > > wonder if - at least for development-centric discussions, not for > > > > "normal" support - this couldn't be an alternative to make those > kinds of > > > > discussions more valuable, approachable and ultimately allows us to > > > > provide a forum for discussion everybodies needs are catered for. > > > > > It's still beta and invited people only, isn't it? Also, from what I've > > > seen so far, it's a security nightmare. > > > > yep, it's beta & invite only. I don't consider both an issue though - > beta > > isn't bad for google apps (dunno how long gmail has been beta), and the > > invites seem to be enough out there. If that *would* be a problem, I'm > pretty > > sure we as an open source group could convince google to shell some > invites > > out (for developers, that is). > > > > > > > > > Also, I'd rather take away our infrastructure from Google than move > more > > > of it to them. E.g. the spam filter for our ticket and commit > > > notification lists is starting to seriously annoy me. Not only have I > to > > > moderate every single message, because Google thinks is spam, even > > > though it only comes from one address, which is the only one allowed to > > > post on the list, now, since a few weeks, without warning, I only get > > > moderation requests every in batches with a few DAYS delay... > > > > While I agree that this is annoying, I fail to see how this translates to > > wave. > > > > I'm all ears for a better solution though. Or maybe I'm preceiving > problems > > that aren't there. > > > > Diez > > -- > > You received this message because you are subscribed to the Google Groups > "TurboGears Trunk" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<turbogears-trunk%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/turbogears-trunk?hl=en. > > > -- Michael J. Pedersen My IM IDs: Jabber/[email protected], ICQ/103345809, AIM/pedermj022171 Yahoo/pedermj2002, MSN/[email protected] -- You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en.
