Slashdot Mirror
Ray Ozzie Calls Google Wave "Anti-Web"
TropicalCoder writes "Ray Ozzie says that Google Wave is 'anti-Web,' by which he seems to mean that it is too complex for its own good. In the video he complains about its complexity in relation to Microsoft's Live Mesh: 'If you have something, that by its very nature is very complex, with many goals... then you need open source to have many instances of it because nobody will be able to do an independent implementation of it.' That's its weakness to Ozzie, apparently — that this complexity that can only be overcome by open source. While he heaps high praise on the Google team that came up with this, he feels that the advantage of Microsoft's approach is that '...by decomposing things to be simpler, you don't need open source.' The Register's author summarizes it like this: 'In a way, this is classic Microsoft meets what is emerging as classic Google. Microsoft gives you an integrated stack but all the moving parts are anchored on a single company's vision. Google frees you to work out the bits yourself, but you must rely on your own smarts or those of your chosen tools.'"
Talk about being anti-web. The wave google tool is something you can use on the web. The Microsoft tool is something you have to download and then install before you can even start using. The wave google tool can be used with anyone with an email address. And the Microsoft tool can be used only with other people if those other people registered, downloaded, and installed their software. Yeah, I really wonder who's anti-web now.
Lotus Notes = Ray Ozzie
if this man is speaking, I am not listening
That's not the issue at hand here. The site linked from the summary, Live Mesh (Beta), supports sharing and discussing documents. It does not do it in real-time, but, realistically, the real-time part of Google Wave's colloborative document editing is not that important.
The real issues are design and openness. I am a bit confused about where Ray Ozzie is coming from: I think he means that the problem with Google Wave is that it is too simple and web-like, not that it is too complex. That is, Google Wave has a lot of potiential, but much of that potiential depends on people writing gadgets/add-ons for it, as opposed to its features being limited to those Google/Microsoft can think up but already layed out in a structured way. The same issue is often referenced as one of the web's greatest strengths -- and weaknesses.
There is another large issue related to openness: privacy. With Google Wave, you can get all of the features running it on your own server, fully controling the software and hardware. Live Mesh is just yet another web service like Dropbox, etc. which depends on Microsoft's Live Mesh servers. Then again, Microsoft may plan on making it part of Windows Server, which gets rid of the privacy issue.
I think the web has shown quite clearly that leaving a protocol open allows for wide-ranged, unexpected innovations to be based on it. Google has shown off some of its ideas on what Wave is useful for. The Wave groups and various blogs have plenty more. Most likely, if Wave actually catches on, at least some of the common/mainstream uses 5 years from now will bare only passing resemblance to the ideas being thrown around today.
Centralization breaks the internet.
There are already good solutions to this problem: it is called revision control and the Subversion system is a high-quality open source solution to most common version control / sharing scenarios. Visual Source Safe wishes that it could be as good as Subversion, but the open source crowd beat them to it.
That misses why Google Docs was actually popular. If two people edit the same document at once, using a revision control scheme, then there's a significant potential of a merge conflict or of a nasty "someone else has the lock on this document" message, both of which are a usability nightmare if your users are non-technical -- the user is stopped in their tracks, gives up, and goes away. Google Docs does use a revision control method behind the scenes (google-diff-match-patch), but because the commits and updates are happening automatically every 30 seconds, the changes are kept very small and the chance of a merge conflict is very much lower. To show just how simple it is technically, Docwit is a very small hobby open source project that ties TinyMCE to google-diff-match-patch to do the same thing, but because you can run your own server you don't have to give Google your data.
Google Wave essentially just goes "Hmm, why don't we shrink the update period even further, and (like SubEthaEdit, and also quite like a few other projects that have involved working on XML documents remotely) send operational changes when they happen rather than polling every 30 seconds?". The change size gets even smaller, and with it the chances of having to show a user a "merge conflict" or "lock conflict" scary box are also reduced.
You see, it turns out not many people use Google Docs for "proper" documents (of the corporate kind) but a heck of a lot use it for collaborative note taking, as a cheap-and-easy wiki, and for lots of other "low-fuss" tasks.