Google Wave
Nov. 10th, 2009 11:55 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
lostcarparkI've been playing with Wave for a couple of weeks now, and I think it's a pretty good idea, but it's going to be a while before it's ready for serious use.
First, while the software is pretty good, there are clearly some gaps around the edges, a few features that say "not implemented yet", and a few nice-to-haves. Obviously it's a preview version, so this is to be expected, and I'm sure it will keep getting better and better.
Second, browsers need to develop. Wave can get quite sluggish at times, especially on big Waves (we've got one with 142 messages plus maps, photos and collaborative drawings (using a plug-in called Canvas). It can be a bit of a drag to navigate. Google Chrome has a pretty fast JavaScript engine, which definitely helps - it's noticably faster than Firefox. However, Wave is a protocol as well as a webapp, so I expect it won't be long before we see desktop Wave apps, just like we have desktop email apps, and these will remove Wave from the browser, and make things a bit easier.
Third, Wave has a lot of potential for corporate use, potentially taking business from Microsoft Office Communicator. However, a lot of companies won't want their content on Google's servers. Fortunately, since Wave is a protocol, they'll be able to set up their own Wave server. I'm not sure when the server software to do this will be released.
Finally, as long as the number of users is restricted, it's going to be of limited use. I presume that this is just to facilitate the preview, and as it develops, it's going to be more generally accessible. For now, we seem to be left feeling, this would be great if only Dave was here...
So I think it has huge potential, but it's probably going to take a couple of years to reach it. For now, it's a lot of fun to play with, but playing is all that's really feasible.
Having said that, if you want to come join us and play with it, I have some spare invite codes. Reply here or drop me an email if you'd like one.
First, while the software is pretty good, there are clearly some gaps around the edges, a few features that say "not implemented yet", and a few nice-to-haves. Obviously it's a preview version, so this is to be expected, and I'm sure it will keep getting better and better.
Second, browsers need to develop. Wave can get quite sluggish at times, especially on big Waves (we've got one with 142 messages plus maps, photos and collaborative drawings (using a plug-in called Canvas). It can be a bit of a drag to navigate. Google Chrome has a pretty fast JavaScript engine, which definitely helps - it's noticably faster than Firefox. However, Wave is a protocol as well as a webapp, so I expect it won't be long before we see desktop Wave apps, just like we have desktop email apps, and these will remove Wave from the browser, and make things a bit easier.
Third, Wave has a lot of potential for corporate use, potentially taking business from Microsoft Office Communicator. However, a lot of companies won't want their content on Google's servers. Fortunately, since Wave is a protocol, they'll be able to set up their own Wave server. I'm not sure when the server software to do this will be released.
Finally, as long as the number of users is restricted, it's going to be of limited use. I presume that this is just to facilitate the preview, and as it develops, it's going to be more generally accessible. For now, we seem to be left feeling, this would be great if only Dave was here...
So I think it has huge potential, but it's probably going to take a couple of years to reach it. For now, it's a lot of fun to play with, but playing is all that's really feasible.
Having said that, if you want to come join us and play with it, I have some spare invite codes. Reply here or drop me an email if you'd like one.
Education, not Technology
Date: 2010-03-03 08:13 am (UTC)Just as a counterpoint to your need for browsers to develop,
we're already pretty much there with the latest swathe. The problem with Wave currently , as I see it, is user education - I've never personally participated in an email exchange that was 142 messages long, so I'm not sure a Wave needs to be so long either...
Having seen that particular Wave it seems obvious to me that it consists of multiple threads that maybe should have been spun off into new waves.
Wave facilitates working this way and reviewing the release video shows that intent, imho.
GMail Buzz is something to watch closely with regard to how Google intend to persuade/introduce users to this new way of communicating...
Luke