|Authored by: Ian Al on Friday, May 25 2012 @ 06:17 AM EDT|
|I bet you guessed where I'm going with this. |
Java is useless for smartphones and yet it is great for Android smartphones.
Python plus Tkinter is not going to be a replacement for Java plus Dalvik, but
you have signalled what needs to be done.
A language must be chosen that makes it easy to program applications with
windows and buttons. The actual windows, buttons and intermediate code
environment must be Dalvik. Python seems a good candidate. I suspect it would be
up to Google to choose the language.
Just because Python is supplied with an interpretive executing platform and uses
existing versions of GUI library support does not mean that it always has to be
that way any more than the Java language has to have JRE.
It needs Google to settle on the object oriented language (because that lends
itself to GUI applications) and then use their skills to 'compile' python to a
form that can be efficiently executed directly in the Dalvik run-time. There is
little reason why both the .dex executing libraries and the .pyx executing
libraries cannot co-exist since we know that some major applications do not use
Google wrote loads of APIs that compile indirectly to Dalvik. They have the
skills to do the same for a Python language API set that replaces javac and dx.
Just give Josh Bloch the choice of interminable court cases about whether the
Java language can be copyright protected (that was only stipulated and not
conceded in this case) or doing a Python API.
At the end of the day, it has to be Google's decision and choice because they
have to efficiently support the language in the Dalvik environment.
Software Patents: It's the disclosed functions in the patent, stupid!
[ Reply to This | Parent | # ]