Tag Archives: OpenOffice.org

Who writes GNU/Linux?

You may have thought GNU/Linux was written by idealistic Unix Gurus camped up with a bunch of Jolt-Colas in their mom’s basement, but a recent report from the Linux Foundation states the opposite. Since Linux kernel version 2.6.11 in Mars 2005 the number of developers has grown from 483 to 1,057 in version 2.6.24 (January 2008). However, the number of sponsoring companies has also grown from 71 to 186 in the same time.

The major contributors aren’t Mom’s Basement Inc. either. Companies like Novell, IBM, Intel, SGI, Oracle, Google and HP rank among the 20 largest contributors (counted in number of sponsored changes, and here sponsoring means paying employees to program those changes).

This is just the Linux kernel (some 8.5 – 9 million lines of code). However, the Linux kernel in itself is of little use to anyone. You have to add the GNU part of GNU/Linux, consisting of commands like fdisk, aspell, bison, ghostview, and wget to that, and you’ll be looking at a much larger number of lines of code. If we go even further adding programs from other projects (like the Mozilla project’s FireFox web browser, or the OpenOffice suite) more lines of code are added (for exact numbers see ohloh.net), and we’re still talking about programs supported by large companies (IBM, Sun, etc).

To sum it all up: no, GNU/Linux is not being written by enthusiasts in the basement anymore. It’s being written by large corporations for competitive reasons. Hardware manufacturers wants to make sure Linux will work on their hardware, software companies can be anything from Linux distribution owners (Red Hat, Novell, MontaVista), use embedded versions of Linux in their consumer hardware (Sony, Nokia, Samsung), or for other reasons (for instance Volkswagen uses Linux for in-car networking between different components).

Office 2007: Microsoft shoots itself in the foot?

I have the somewhat dubious pleasure of working at a place where the migration from Office 2003 to 2007 is halfway done. Now, usually this should be no problem, but a couple of factors have cooperated to make it one.

Office 2007 uses a new (and improved?) format (they added an x to all their file name extensions, read more about them here). This could be all good and well if it had not been for the fact that new versions of Office now uses these formats per default. Okay, a user a bit savvy might sooner or later notice the “x” at the end of all filenames… but only the users that have disabled the setting in Windows to hide these formats…

This leaves us with senders, running Office 2007, unable to tell if they saved the file in docx or doc format, and the recipients with Office 2003, unable to read these files. Even though there is an update, a lot of users aren’t comfortable with doing that… heck, I’m scared of doing unneccessary stuff to my wobbly M$ installation!

The end result becomes pretty predictable: chaos, disillusioned users, and … a great day to start talking about OpenOffice.org? (even though it does not yet support the Office 2007 format).