Google Wave: Information organizing outsourced Posted by Swapnil Pathare on Jun 2

Some may say that it is too late to blog about Google Wave. The applause which started on May 28 can still be heard and the Internet community has done everything but go down on their knees and bow to the awesome concept.

For those who couldn’t manage time to watch the Wave preview, here are just some of the things it does :

  • Acts like email when the recipient is offline
  • Acts like a realtime chat when the recipient is online
  • Maintains a common structure in one place (visible to, and editable by all concerned parties) instead of having copies in every person’s account
  • Allows you to add other recipients to a subset of a Wave or the whole Wave.The new folks can “Playback” how messages were exchanged
  • Allows visual plugins which can take the form of games, polls, etc. For example, instead of sending messages to each other, you can send Chess Moves which the plugin happily records and the game proceeds
  • Allows realtime collaboration on documents with changes tracked. Again, a common copy of document is maintained.

While some skeptical glances are surely cast as to whether people will “embrace” this new concept of communication (as they are still stuck to SNDMSG program and have not been able to comprehend any other way to communicate all these years), the overall mood is that of joy, on having seen something truly profound, and having been promised that this will be available to everyone, for FREE, later this year.

The most obvious thing that hit me while seeing the preview was the way Google relentlessly pursues its mission. Remember Google’s Mission statement?

Google’s mission is to organize the world’s information and make it universally accessible and useful.

This is the way Google earns money: By targeting advertisements suited to your interests. How does it understand your interests? By organizing information about you.

So while the mission is technically about helping the world, it is also a lot about making profit. Of course, there is nothing wrong whatsoever in making profit by developing something which provides value to the user. Microsoft earns by asking users to buy the product, Google earns by providing relevant advertisements.

Thus started the long journey of organizing the world’s information. First they gathered some trends of what we search based on cookie information. GMail was the next big boost as a lot of personal emails meant a lot of personal information. Orkut, Blogger, Google Talk, Docs, Sites, Reader, Youtube; each product added to its suite targets nothing but collection of information from users in exchange for some great services, for free.

Yet, Google would still require to organize bits of information from different applications to understand the “complete picture”. Google Wave, in a lot of ways, has removed that additional effort.

Wave is a communication structure that can be used anywhere. (Potentially) integrated throughout Google Applications and beyond, it provides a single point of communication. Email, chat, organization of albums, blogging, collaborating on documents, everything is either available in the Wave structure or can be derived out of it (by creating a new Wave and importing some specific elements). So now, Google does not need to  organize information about you. You yourself will organize it all using Wave. It is safe to assume that information which might have been dispersed around on a dozen different websites online (Google or others) will now be collected in a common Wave. With little or no effort, your whole life (henceforth) is likely to be captured in a handful of waves. I shudder just thinking of the advertising avenues that follow.

Google, you evil genius, you!

Jaunty: some problems and workarounds Posted by Swapnil Pathare on May 27

OK, so lets have a quick round of what could go wrong post-upgrade to Ubuntu Jaunty and how to fix it, fast. These are some of the problems I faced, and found all the solutions by googling. Just listing them out here. Hope this helps some of you.

1. Proprietary ATI drivers

The first thing we come across is the video drivers which never were. The moment you try to install proprietary ATI drivers for “old” cards (my ATI RadeonExpress 1250 happens to be one of those), you will get a system freeze. No graphics, no inputs, just some random colors on screen, which aren’t very pretty either.

Solution here:

sudo /usr/share/ati/fglrx-uninstall.sh  # (if it exists)
  sudo apt-get remove --purge fglrx*
  sudo apt-get remove --purge xserver-xorg-video-ati xserver-xorg-video-radeon
  sudo apt-get install xserver-xorg-video-ati
  sudo apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri xserver-xorg-core
  dpkg-reconfigure xserver-xorg

You could probably create a script of this sort and save it in your home directory, so that when the system does fail, you can easily get into recovery mode (use the “Recovery mode” listed in Grub) and just run this script rather than attempt googling through Lynx, which I almost always end up doing. In case you plan to run this script in recovery mode, you don’t need the “sudo” command for any line since you will be “root” already.

2. Screen Freeze with Compiz

The open source drivers you install for ATI are known to create hassles for 3D graphics. Jaunty does allow you to enable Compiz (System Appearance -> Effects -> Normal / Best). However, I had a complete system freeze lot of times while I gave Compiz a try. I could easily reproduce the strace gedit bug while 3D effects were enabled.

Solution: Disable Compiz (or downgrade :) )

3. VirtualBox fails to start

The Virtualbox kernel module needs to be recompiled for the newer kernel in Jaunty. This problem is not specific to Jaunty (or even Ubuntu), but no harm in listing it here.

sudo apt-get install linux-headers-$(uname -r)
sudo /etc/init.d/vboxdrv setup

The first line downloads appropriate Kernel Headers for the latest Kernel, which will be used by the “vboxdrv setup” command.

Ubuntu: Releasing software which “Just Works” Posted by Swapnil Pathare on May 26

In my last post, I summarized my problems with the latest version of Ubuntu: Jaunty Jackalope. I’m not the only one cribbing about it, though. Many bloggers out there are doing a better job than I am, posting problems with solutions to them. Forums are abuzz with all the issues right from screen flicker to sudden OS freeze to wireless connectivity. In short, everything is normal.

The problem with Ubuntu, however, is that with the frenzied pace of development and the releases being churned almost twice yearly, I am quite certain that most of the bugs reported for this release will be ignored or will be prioritized “Low”, meaning they are kept for “later” (read: never). While this is an issue with even slow-moving projects, I am (or at least, was) quite impressed with the way Ubuntu maintained quality till Hardy Heron. Most of the packages “Just worked” post installation, with a few hiccups here and there. Hardware, drivers and graphics did remain a concern, but that is something we have to live with for a while, given the low interest of manufacturers for providing Linux drivers.

Anyway, back to the point: The current pace of development for Ubuntu guarantees a lot of loose ends in newer releases. In contrast the Debian community goes for “release when ready” philosophy. However, they suffer from delays and more delays in releases, leading people to believe that Ubuntu is the right way.

Which brings the question, what, really, is “the right way”? Most will consider a “middle way out” but that is easier said than done. Granting developers’ request for more time on the basis of an incomplete feature or a yet-to-fix bug list will eventually lead to a heavily-delayed release. On the other hand, having a strict deadline means that you are ready to compromise on the quality of the release. While this matches the “release early, release often” philosophy*, there’s a slight disconnect when it comes to having a product eager to replace Microsoft Windows, as is described in… Bug #1 for Ubuntu.

Microsoft has a majority market share in the new desktop PC marketplace. This is a bug, which Ubuntu is designed to fix.

Back to the point (again), Paul Graham also corrects the general perspective for “release early”:

By “release early” I don’t mean you should release something full of bugs, but that you should release something minimal. Users hate bugs, but they don’t seem to mind a minimal version 1, if there’s more coming soon.

So far, I don’t see any awesome release philosophy with a strong way to maintain the pace, while maintaining the quality. All we can do, maybe, is to have an in-between release to just “fix more and add less”. This is where developers may find themselves in bug-fixing mode, instead of their favourite “building that cool app”, but its all for the greater good, no?


* I never dreamt I’d link to ESR one day, but anyway I’m disagreeing with him, so no problemo

« Previous Entries