JavaFX Runs On Raspberry Pi 147
mikejuk writes "Oracle seem to be concerned that the Raspberry Pi manages to run Java properly and they are actively working on the problem. To prove that it more than just works, what better than to get a JavaFX app up and running — what could be more cutting edge? Unfortunately the trick was performed using a commercial version of the JDK with JIT support and some private code, but it is still early days yet. Java and JavaFX on Raspberry Pi takes us into a whole new ball game." Watch the video at the linked report to see it in action.
Re:How is this news? (Score:3, Informative)
http://icedtea.classpath.org/wiki/ZeroSharkFaq [classpath.org]
"What architectures do Zero and Shark work on?
As of December 2008, Zero is known to work on Alpha, ARM, IA-64, MIPS, PowerPC, x86, x86-64 and zSeries.
Shark should be able to build on any Zero-supported system that LLVM has a JIT for. As of October 2009, this is ARM, PowerPC, x86 and x86-64. "
Re:Foot, meet bullet. (Score:5, Informative)
>Please, the vast majority Java was open sourced in 2006 under the GPL
The code was. But if you want to write any Java code you need to use Java APIs. Those are copyright and subject to Oracle's terms of use. Go to http://docs.oracle.com/javase/7/docs/index.html [oracle.com] - see that link to a copyright statement at the bottom: http://docs.oracle.com/javase/7/docs/legal/cpyr.html [oracle.com]. That document says:
So what is the license agreement: Try to download the documentation (http://www.oracle.com/technetwork/java/javase/documentation/java-se-7-doc-download-435117.html [oracle.com]). That has a click though agreement to http://download.oracle.com/otn-pub/java/licenses/java-se-7-spec-license.txt [oracle.com], which in turn says:
So - you can use the APIs for internal evaluation only. In other words - if you wish to use them for any other purpose you need another license from Oracle.
This is exactly the case Oracle has advanced against Google (who violated clause (i) above by implementing the specification).
But, they could advance a case against any Java developer, because no matter how they learned Java, these licenses do not extend third party rights, so each developer has to officially learn about Java through the Java specifications. And if you are using Java for any purpose other than evaluation, you are in violation.
If you use something other Java SE, then you are even worse off, because the APIs are not actually published. The licenses for various versions of Java have changed slightly over the years (the one for Java 5 - which Google is being sued under - says that the license overrides all other statements from Sun, although Oracle's lawyers didn't read that far into the license else they would have used that clause to nullify the damaging testimony about Sun's approvals of Google's actions.
Before you accuse people of astroturfing, learn the turf.
Regards,
-Jeremy
Re:No to Java : not trustworthy: (Score:4, Informative)
Oracle went total asshole, but I don't believe they can pull off that API copyrighting stuff. (In Europe it's already thorwn out.) Also, the whole debacle is unlikely to affect J2EE and J2SE developers.
Re:Foot, meet bullet. (Score:3, Informative)
So - you can use the APIs for internal evaluation only. In other words - if you wish to use them for any other purpose you need another license from Oracle.
Did we red the same piece of text?
means exactly that you can develop all applications you want using the Java APIs, how do you interpret that as "they could advance a case against any Java developer"?
No, Google
1) did NOT use the GPL OpenJDK, and therefore they're not covered by the GPL license; and they expressly chose not to use the OpenJDK because they dislike the GPL, as Google said explicitly in their published emails;
2) violated this part, of the license, that you omitted to quote:
In other words, Oracle claim that Google created a Java-based platform that is not compatible with Java, and called it Java. Which is what Microsoft did in the 90s (and has nothing to do with the developers of Java applications). A judge will decide if this is the case, but saying that every Java user could be sued for writing Java applications is frankly not true.
Again, you're omitting to say that the license explicitly allows you to:
1) develop applications for Java (ANY Java platform implementation)
2) develop complete implementations of the Java platform.
There is only one thing you can't do: develop an incompatible implementation of the Java platform and call that thing Java. You can create incompatible implementations of the GPL code of course, but then you can't call it Java. Oracle thinks that Google did that.