Openmoko vs. Android

[swifty]

I found a brilliant summary on Openmoko compared to Android written by Wolfgang Spraul on the Openmoko mailinglist:

Let me use this opportunity to talk a bit about Openmoko and Android.
First of all we really like Android! We don't see Android as
competition, it is complementary to what we are doing and may help us
in many ways.

If you look at the Android software stack, you will notice that they
basically only use the Linux kernel and a few traditional 'helper'
libraries, written in C (jpg, png, etc).
But the bulk of the system is written from scratch. They even have
their own libc! Their own Java virtual machine, their own graphics
system, etc. etc.
I do believe all of this is very healthy. Fresh blood. Take the Dalvik
virtual machine for example. Basically they kick Sun somewhere, but
that may turn out to be a nice wake-up call for something like HotSpot
and similar established Java projects. IcedTea, GNU Classpath, etc.
At the same time they ignore pretty much everything the FOSS community
built over the last 10-20 years.
No X, no d-bus, no standard packaging system, ...
It's a fundamentally different approach from Openmoko.

From outside you first have to decide: Do you go with Android and
step outside of 90% of what the FOSS community has built? Or do you go
with Openmoko, which is a lot closer to something like Ubuntu?

There are many things to learn from Android. I like their 'intent'
system for example. Lots of great software will become available as
Open Source, and will find its way into many places, one of them being
Openmoko.
Getting the complete Android to run side-by-side with GTK or
Enlightenment will be a lot harder than it is with Qtopia for example.
That's because even though Qtopia can be seen as one large monolithic
code base, it is still relatively well connected to many other FOSS
standards. Android is not connected at all, just sitting on top of the
Linux kernel, and several times larger than Qtopia.

Bottom line: We hope the Android sources will be releaesed soon. We
think Android is a great piece of software, will become really
successful, maybe even become the long-awaited 'Linux desktop' one
day? The future looks good for Android.
Openmoko will benefit in many ways, from Google pushing chip vendors
to become more open to lots of high-quality Apache-licensed source
codes being set free, allowing us to cherry-pick from Android into
Openmoko.
Additionally, you can either play with Android itself, or run Openmoko
software on hardware that was opened up thanks to Android.

Hope this helps, everything is moving so this is just a snapshot in
time.
Feedback very welcome, a lot of this is driven by what the community
wants to do. Often people show us how things should be done, not the
other way round
Wolfgang

source:
http://lists.openmoko.org/pipermail/...il/014813.html


sorry, for posting this in 2 forums.
i wanted to know wich one gets more vies/replys

[aksd]

Wonderful swifty, the article is very enlightning on the Linux on mobile front .

I have a question, Google claim that external apps on the phone can be given the same permissions or access as the built in apps, but external apps being only in Java how can this be possible due to the limitations of the JVM?

[swifty]

Wonderful swifty, the article is very enlightning on the Linux on mobile front .

I have a question, Google claim that external apps on the phone can be given the same permissions or access as the built in apps, but external apps being only in Java how can this be possible due to the limitations of the JVM?

Dalvik is often referred to as a Java Virtual Machine, but this is not strictly accurate.
found:
Dalvik virtual machine - Wikipedia, the free encyclopedia

[aksd]

conversion to .class to .dex wont that make it a little bit slower?

[swifty]

conversion to .class to .dex wont that make it a little bit slower?

here is a JAVA expert needed, not me