The number of people using Linux (and I mean Linux the kernel) and
free software in general has exploded in the last 2 years thanks to
Android and Google. Even if you want to discard phones and only count
the tablets (which are starting to get very close to laptops in terms
of what you can do with them), the number of new users is huge. And
yet, we are all hostage of a choice -- a bad choice, in my humble
opinion -- that Google made: Java.
Reason #1: Android came with Java! To be fair, it wasn't Google's
choice as such: Google bought Android in 2005, and I can only suspect
that Android was well entrenched in Java at that point.
Reason #2: In 2005, Java was still pretty much your only choice if you
wanted to write applications once, and expect them to run regardless
of what CPU you used.
Reason #3: Java was (and is) well known and widely used.
It's all about timing
In 2005, it probably made a lot of sense using Java. So, what has
Chrome beta was released in September 2008. The first version of
Android would be released a couple of months later (!). While Android
was being created, Chrome simply wasn't around.
What's so important about Chrome?
turned: it went from being a sluggish scripting language, to being
something that could be used for real applications. Google was
interested in a browser that people could use to run their emerging
online applications (Google Docs was around in 2006). I am not sure
maybe it caught Google itself by surprise.
In the end, if Google had to decide how to build Android in 2008
rather than 2005, I have little doubt that they would have picked
embraced Java -- although they tried to bypass some of the patents and
issues with Java by using Dalvik. At the moment, to develop an Android
application you write Java code, compile it into a .class file (Java's
compiled code), and then convert that .class file into a Dalvik file
(which will be then interpreted by Android's internal Dalvik virtual
Is it too late?
At the moment, if you want to write an application for Android you are
pretty much stuck with Java. There are ways around I must say: one of
them is Phonegap which is released under a free license and is indeed
very exciting. PhoneGap is essentially a browser application that will
is not native: it's a custom browser that has access to the device's
hardware, and that runs your web-like code.
What about native Applications?
However, things are not easy: the Dalvik virtual machine doesn't work
nicely with dynamic languages . It's a pretty messy business.
The possible solutions
Since Google is about to include V8 into Android 4 (or so it seems),
we would have a situation where your phone would include two very fast
only write native applications for one of them.
My idea is that Google should provide, natively, a bridge between the
code. To me, it's looking less and less likely that this will ever
The other option is quite involved: it would require Google to make it
them to access the system libraries (System C library, Media
Libraries, Surface Manager, SGL, LibWebCore, 3D libraries, FreeType,
come with an overhead as big as a full browser for a start (there
would be no need, since all you are using is the V8 virtual machine,
like Node.JS did).
Am I dreaming? Maybe. I wonder if I am the only one who thinks that
being locked to Java deserves a solution -- a real one.
|Thread||Thread Starter||Forum||Replies||Last Post|
|What is native and what is exotic?||VtSkier[_2_]||Mountain Biking||1||April 28th 10 04:15 PM|
|Best Android apps||DoTheHustle||Australia||2||February 28th 10 10:37 AM|
|jamie paolinetti and native productiions||B||Rides||0||May 13th 05 08:24 PM|
|Mention unicycling on college applications?||tennisgh22||Unicycling||15||January 12th 05 08:53 PM|