Michael Pedersen schrieb: > 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.
Well, if it's not working at advertised (and that is very much about IM-style communication), it's not suitable. As I said, I've just been invited, and haven't played with it. Especially not in a larger context. I'd love to give it a shot though. 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]. For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en.
