Darwin's Theories - Open Source Software category

Android on FreeRunner

Sat, 13 Feb 2010 19:26:00 GMT

Android or FreeRunner, that is the question for those who want a mostly-open-source cell phone. At least it used to be. Now that Openmoko have all but discontinued development on the Freerunner hardware, the future looks more and more like Android. And while I had hoped someday to be able to run OpenBSD on the Freerunner, it looks like that won't happen. Fortunately, there is a good implementation of Android for the FreeRunner, available for free download from this Android on Freerunner site at GoogleCode. I've been using this for a few weeks and, while it's not 100% rock solid, it is very close. I think I've had to do the battery-out-to-reset two or three times in three weeks (not counting the time I used the Android as an alarm clock and woke up from such a slumber that I couldn't remember how to shut it off).

Another Top 10

Mon, 25 Jan 2010 17:29:00 GMT

Here we go again:

OpenMoko: Beginning to End

Thu, 31 Dec 2009 00:13:00 GMT

This article has been withdrawn from the blog; a revised version of it is hopefully going to be published on a commercial web site this month.

OpenMoko and Android

Tue, 21 Apr 2009 17:35:00 GMT

A few people have asked me at various times for a comparison of the OpenMoko and Android cell phone projects. Given that I advocate for the former, and also for Java which is (and is not) the base language of the latter, I am expected to be able to say something intelligible by way of comparison. So here goes.

Android is a project spearheaded by Google to make an open-source phone. It uses Linux and its own Dalvik virtual machine, and applications are written in Java against the Android API and compiled down to Dalvik bytecode. Android does not expose the rest of the Linux services and does not support other programming languages. Android phones are available from a few carriers.

Openmoko, funded by Openmoko.com, is at the other end of the spectrum: it also uses Linux, but exposes all of it to the developer. The "main" stack of phone apps has been re-written several times, using various X-based toolkits. The "official" OM2009 stack is in large part written in Python. C/C++, Java and Perl are all available. Openmoko phones are available from Openmoko.com. However, because it is all open source:

you can run Android on Openmoko hardware;
you could (people have) run Openmoko software on other devices, including Palm PDAs, other Linux phones, and software emulators;
you can probably run Openmoko software on Android hardware;
you can run QTopia on Openmoko hardware;
you can run one of half a dozen Linux distributions on your Openmoko hardware;
you can (eventually) run other OSes such as OpenBSD on Openmoko hardware;
etc.

From one point of view, they are not enemies. Both support the open source model. But as Openmoko developers have pointed out some time back, Android sits on top of Linux, abandoning most of the open source world and reinventing its own universe. Openmoko embraces all existing open source projects and any new open source comers. As a single example, communicating to your Openmoko phone from a desktop/laptop computer consists merly of running the industry-standard ssh and scp programs, included with every *Nix and readily available for those other OSes that need them. Talking to your Android phone requires finding, installing, and figuring out how to use an ad-hoc program called "adb" (at least the third use of this name, after Unix' Algol/Another DeBugger and Apple's Desktop Bus).

From another point of view, of course, they are competing. Competing for market share (neither has made much inroads in the consumer space). Competing for developer mindshare. Android tends to get a lot more press, partly because of the "big G" lineage.

People sometimes ask if I think Openmoko should just fold up and go on to something different, given how far ahead Android has moved? I've never been a fan of quitting while you're behind. Imagine if Linus Torvalds had quit while Unix was ahead; his then-little school project would never have seen the light of day, and we'd all be running BSD and System V. Nothing wrong with those - BSD was already on its way to becoming a full open source *Nix, as represented today by OpenBSD, FreeBSD and NetBSD - but things would be rather different in what is now the Linux community, to say the least. Or if Bill Gates had quit while IBM was ahead. Or if Steve Jobs had quit while MS-Windows was ahead. Or if the U.S. had quit the space race when the Russians launched Sputnik. You get the idea. Don't quit while you're behind, nor when you're ahead. As Nathaniel Branden once put it, "a beating heart is a living heart" - so keep on pumping!

And, at any rate, the "real" release of Openmoko software, OM.2009, is almost upon us; I am running a beta of it on my Freerunner (GTA02), and it's actually usable as a cell phone. Butt-ugly compared to some of the earlier releases, but it "just works". Formal release is expected this summer.

Site Modernization

Thu, 26 Mar 2009 14:49:00 GMT

Every web site needs to keep improving, and your obd't servant is no different. I started almost exactly a year ago by replacing the old blog software with Pebble. Then I got busy with real work, and had to put aside site maintenance. Around the beginning of this year I was able to modernize both the home page of darwinsys.com (making it new and graphical) and the layout of the rest of the main site. This week, I re-did the Java Web Frameworks site, which has gone from coyote-ugly to fairly modern looking, after being re-implemented using the Seam framework. So, I am now running Seam ("war deployment" option) on Tomcat in production.

At the same time, I had to upgrade the Tomcat web server from 5.5 to 6.0, which went fairly smoothly, although there may be a few little bits that need a boost.