top | item 3911529

(no title)

Sun/Oracle had OpenJDK (published under GPL) which is supported by everyone including IBM (after it abandoned Harmony).

>you're going to have to expect non-"Java" open source forks.

yes, licensed under GPL not ASL.

Here's what Andy Rubin had to say about GPL:

"The problem with GPL in embedded systems [such as smartphones and tablets] is that it's viral [...]"

"Sun chose GPL for this exact reason so that companies would need to come back to them and take a direct license and pay royalties."

discuss

magicalist|14 years ago

You forgot to mention the years that Sun strung Harmony along (since JCP decisions at the start of OpenJDK development in 2006!), a behavior that Oracle came out vocally and publicly against until they acquired Sun.

> yes, licensed under GPL not ASL.

I feel like you don't really read the posts you respond to. That kind of thinking was exactly the impetus for the non-"Java" forking I was referring to. Hypothetical: someone forks OpenJDK and makes incompatible changes to the APIs. They have no interest in passing the TCK or following the restrictions in the OpenJDK Community TCK License Agreement. Are they able to release this as long as they don't call it Java? More concretely, should GNU Classpath be shut down?

Precedent up to this point says that that both are fine and have to be tolerated. Jonathan Schwartz said both bothered them but had to be tolerated, but you've made clear that his opinion couldn't possibly be relevant. We'll just have to see how this case turns out.

jimmyvanhalen|14 years ago

>Jonathan Schwartz said both bothered them but had to be tolerated, but you've made clear that his opinion couldn't possibly be relevant. We'll just have to see how this case turns out.

His "endorsement" is not a license or a permission to break copyright/license agreements.

ZeroGravitas|14 years ago

Quotes out of context might work on juries where anyone with technical experience has been excused, but he's clearly talking about their GPL code (which they went to great lengths to not use) because no-one in the industry thinks API's are copyrightable or should be. If they did they'd have worked around it like they did the GPL code.