Mysterious Android codebase commit

Google has made a point of not using GPLed code (except Linux) or Sun/Oracle code in Android, for technical and legal reasons. There's even a lawsuit about it. So it's surprising to see GPLed Oracle OpenJDK code being committed anywhere near Android.

Re: Mysterious Android codebase commit

#6

Post by grizzles » Mon, Dec 28, 2015, 11:28 PM UTC

To explain if you are just joining in: This pretty much means Oracle v Google, a case with major ramifications for the industry has been settled out of court. I don't see how this can be interpreted any other way.

Re: Mysterious Android codebase commit

#7

Post by 0x0 » Mon, Dec 28, 2015, 11:36 PM UTC

grizzles wrote: post #6

To explain if you are just joining in: This pretty much means Oracle v Google, a case with major ramifications for the industry has been settled out of court. I don't see how this can be interpreted any other way.

Also, why are the two timestamps so far off? Authored in February 2015 (almost a year ago!), but committed only in Nov 2015.

Re: Mysterious Android codebase commit

#8

Post by temac » Mon, Dec 28, 2015, 11:47 PM UTC

0x0 wrote: post #7

grizzles wrote: post #6

To explain if you are just joining in: This pretty much means Oracle v Google, a case with major ramifications for the industry has been settled out of court. I don't see how this can be interpreted any other way.

Also, why are the two timestamps so far off? Authored in February 2015 (almost a year ago!), but committed only in Nov 2015.

Maybe because this has been ready for a long time just in case and they just decided to actually switch to that strategy right now?

Re: Mysterious Android codebase commit

#9

Post by grizzles » Tue, Dec 29, 2015, 12:11 AM UTC

grizzles wrote: post #6

To explain if you are just joining in: This pretty much means Oracle v Google, a case with major ramifications for the industry has been settled out of court. I don't see how this can be interpreted any other way.

If this inference is right, I hope this means that Google will enable the web community to use the JVM with or as an alternative to WebAssembly. Hotspot is absolutely incredible technology, and it's competitors are still many years away from coming close to matching it's capabilities.

Re: Mysterious Android codebase commit

#10

Post by 0x0 » Tue, Dec 29, 2015, 12:31 AM UTC

grizzles wrote: post #9

grizzles wrote: post #6

To explain if you are just joining in: This pretty much means Oracle v Google, a case with major ramifications for the industry has been settled out of court. I don't see how this can be interpreted any other way.

If this inference is right, I hope this means that Google will enable the web community to use the JVM with or as an alternative to WebAssembly. Hotspot is absolutely incredible technology, and it's competitors are still many years away from coming close to matching it's capabilities.

Embedding the JVM to run code within webpages you say? Hasn't that been tried before? :-S