|
|
|
| Authored by: Anonymous on Friday, April 27 2012 @ 07:33 AM EDT |
Its completely in the spirit of the GPL:
"If you don't like our lisense terms, go write your own code."
And what has google done?[ Reply to This | Parent | # ]
|
| |
| Authored by: Anonymous on Friday, April 27 2012 @ 08:16 AM EDT |
Dalvik is a general-purpose virtual machine; a software-emulation of a CPU.
The Java compiler produces "byte code", machine code for a different
(somewhat higher-level) CPU (also emulated).
For Android, Java byte code is then compiled to Dalvik code.
It's a bit like using GCC to compile C to an Intel CPU, then using a second
compiler to compile Intel instructions for execution on ARM (or TransMeta in the
old days).[ Reply to This | Parent | # ]
|
| |
| Authored by: hardmath on Friday, April 27 2012 @ 09:31 AM EDT |
Java was not GPL'd at the time Android was announced, and
Google has presented testimony that switching to the OpenJDK
would have required rework and delay.
In fact Sun was not able to fully release Java under the GPL
without a bit of a switcheroo. There were too many
components of Java 1.5 to which they did not own the
copyrights and which they could not negotiate an agreement
with the copyright holders to allow their contributions to
be compatibily licenses.
Instead the IcedTea JDK implementation was adopted as the
"reference implementation" for OpenJDK6 and OpenJK7.
Oracle continues to distribute as a proprietary binary the
version of Java SE that contains those unGPL'd components.
So point in fact, there was really no opportunity for Google
to use OpenJDK for Android.
---
"Prolog is an efficient programming language because it is a very stupid theorem
prover." -- Richard O'Keefe[ Reply to This | Parent | # ]
|
|
|
|
|
