5 ms·
The court has made the point now that literally just the class and method names are subject to copyright.
by monocasa 9y ago
The court has made the point now that literally just the class and method names are subject to copyright.
- EGreg 9y agoI thought Google used the implementations!
- guelo 9y agoThey mostly used Apache Harmony's implementations.
- deleted 9y ago[deleted]
- ghayes 9y agoI thought one of the main issues was that there was only one natural implementation of many API functions. Like when you assign students a coding question, you will see many answers come back identical even though no one cheated.
- monocasa 9y agoEven then, there were only a couple trivial places that saw literal copying. The code that checks for array out of bounds was the main one.
- deleted 9y ago[deleted]
- ninkendo 9y agoDevil’s advocate here... the method signatures, the layout of the classes, what inherits from what, what bits are private vs public, are all pretty non-trivial. Moreover it’s where a lot of the subjective decision making happens, whereas the actual implementations are straightforward once you know what the method signatures should be. I don’t necessarily agree with the decision but I can see where they’re coming from.
- monocasa 9y agoTriviality isn't the determining factor of what's copyrightable. Edit: And particularly there's tons of case law that this stuff isn't copyrightable, see Sony v. Bleem, where a company literally wrote an emulator of a PS1, and courts said that was fine. Even to straight up sell as a competing product, and for running on competitors machines. Edit2: And the otherwise shitty DMCA even has explicit exemptions for software interoperability purposes.
- deleted 9y ago[deleted]
- treis 9y agoIn Sony v. Bleem they used blackbox testing and created their own original code from that. If Google had done the sam they would have been fine.
- monocasa 9y agoBecause of Java's reflection, a black box approach would have given you the same API names that are being discussed here.
- hcknwscommenter 9y agoNot necessarily. You don't have to "look" at the reflection.
- monocasa 9y agoYou do to be API compliant.
- hcknwscommenter 9y agoBleem did not copy. An emulator is not necessarily a copy.
- justonepost 9y ago
- AgentME 9y agoIsn't Java open source? (Does this not include the APIs that are part of it?)
- fapjacks 9y agoWhen it comes to Oracle, it doesn't matter. There's a reason MySQL was forked into MariaDB basically the second Oracle bought it.
- alok-g 9y agoOpen-source does not mean there are no restrictions. AFAIK, Java's open-source license did include some provisions that Google violated. PS: I am not a lawyer. Above piece of knowledge is coming just from what I read, perhaps on HN during the previous ruling on the case.
- ben509 9y agoOpenJDK is presently under GPL 2, with the "classpath exception" at the end: http://hg.openjdk.java.net/jdk9/jdk9/file/a08cbfc0e4ec/LICENSE http://hg.openjdk.java.net/jdk9/jdk9/file/a08cbfc0e4ec/LICEN... At the time, though, I don't believe it was open source and OpenJDK originated as a cleanroom rewrite of it, and has since been integrated.