Slashdot Mirror


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.

2 of 365 comments (clear)

  1. Too Bad by tpstigers · · Score: 0, Offtopic

    I was going to link to this post from another forum that's been discussing Wave. Then I read the comments. It took me five minutes to find one that wasn't juvenile. Is this what Slashdot has come to?

  2. Re:Tried it by BitZtream · · Score: 0, Offtopic

    Sounds neat. Too bad its done using a bunch of sub-standard 'apps' (and I use the term loosely) that don't have half the features of any desktop equivilent. gmail is okay if you don't have to integrate with other apps. Docs sucks, period. blogs work fine already, we don't need any more retarded one entry blogs from people who think they have something to write about, same goes for photosharing.

    The idea that one protocol is a good idea is rather retarded, especially considering how it isn't one protocol. All of these protocols are built on top of IP, mostly using TCP and possibly some UDP (thats 3 and we can't even talk to it in any way yet). You view the presentation layer over HTTP, server communications is done on top of XMPP, then on top of that you use several other new protocols to do all the other crap. Go Google! Bringing new meaning to reinventing the wheel. You just built a complete OSI model on top of an EXISTING COMPLETE OSI model. But we'll call it one protocol.

    So tell me, why is it a great idea to invent new protocols and stack them on top of existing protocols already designed to do the job just as well? Just because a Google engineer spewed it, doesn't make it actually true or 'great', regardless of how much you look up to them.

    I for one am obviously not impressed, even if a bunch of geeks at Google love it, doesn't mean its anything useful to the general public.

    --
    Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager