Google Wave Reviewed
Michael_Curator writes "Developers are finally getting their hands on the developer preview of Google's Wave, which means we can finally get some first-hand accounts of what it's really like to use, unfiltered by Google's own programmers. Ben Rometsch, a developer with U.K. Web development firm Solid State, blogged that, it's 'probably the most advanced application in a browser that I've seen.' Wave is like giant Web page onto which users can drag and drop any kind of object, including instant messaging and IRC [Internet Relay Client] clients, e-mail, and wikis, as well as gadgets like maps and video. All conversations, work product and applications are stored on remote servers — presumably forever. 'It's like real time email. On crack,' he wrote. And unlike the typically minimalist Google UI, 'It feels a lot more like a desktop application that just so happens to live in your browser.'" User molex333 has already written a Slashdot app and shares his initial reactions here.
I've participated in a wavelet writing hack-a-thon and was impressed by the scope of the collaboration that it provides. I saw it as an email, shared docs, blogs, instant messaging, photo sharing in one protocol. It certainly wasn't perfect and some parts were rather underwhelming but overall it seemed like the beginning of a new way of doing things. I was talking with one of the devs in the Sydney office and he said that they use it internally and are surprised by the way that the more they used it the more they discovered new ways to use it. I took that as a good sign that it was a technology/protocol that was at the beginning of the discovery rather than one that is released with every usage known. Would I use it commercially - not yet, but I can imagine it becoming a core tool to organising/interacting my social circle. I could easily see it being a great tool for collaborative programming and/or a new generation of remote role playing (build a dice rolling tool, a mapping tool etc.)
I just can't be bothered.
This is missing the point of Wave. It's not patented. It's open sourced. It's federated (with no central authority). There is nothing preventing a company, or an individual, from setting up their own wave server (either the one given away for free by Google, or another one developed by a third party), and not sharing one piece of data with Google.
That's what makes the proposition so compelling. Google is not trying to lock in your data. It's doing everything it can to do the opposite actually.