A very nice person sent me an invite to GoogleWave, which I’ve been wanting to play with, ohhh, only since they announced it, pretty much. Not many people I know have it – and it is in many ways a kind of specific tool, so it’s not something you necessarily just sit and play with, especially not on your own, because that removes the point.
However, @Sunsetmog and I spent some time on Thursday playing with GoogleWave, trying to explore it’s possibilities and potential. The verdict so far is, as above, ‘Hrroomm, Hmmm’ – lots of potential, not quite there yet.
The first (and main) problem is that it is very slow. Typing into GoogleWave feels a lot like typing on a computer without enough RAM – your fingers go faster than the letters can come up on screen. I think this is mostly because of the live-type function that allows all the people on the wave to see exactly what you’re typing. I have to ask – why is this feature necessary or good? Is it just so that people can start responding to you as you go, without waiting you to finish your train of thought and absorb it before replying? Because I’m not convinced that that’s a good idea; much better to see your fellow-waver’s full thought before you reply to it. Additionally, the nature of GoogleWave means that a lot of people will probably end up using it for project work, quite often with people who are colleagues rather than friends. I don’t need or want the people I might end up working with to see that I am constitutionally unable to type ‘constitution’ fluidly and correctly with any regularity (all those ‘t’s confuse my fingers). They probably don’t want to see it either – it’s quite painful. Delete isn’t a bad in this situation. Making the text input the same as that of IM would make GoogleWave faster, I think, and also less embarrassing!
