D
Deleted member 7164
Guest
What matters are the licensing terms of the Java API and whether the licensing terms are legal. My understanding is that the API license doesn’t allow you to implement subsets of it, and there are other conditions as well: https://www.oracle.com/downloads/licenses/javase8speclicense.html
Seems pretty clear that Google violated those terms. If the licensing terms specced by Oracle are illegal, then you’d have to believe that the terms of licenses like the GPL would also be illegal, and there’s precedent showing that to not be the case.
1. All statements written in license are void if not aligned with the actual consumer or business laws in the jurisdiction
2. GPL is the wrong licence, LGPL would be analogous because it's used for libraries (and hence APIs). It is permissive down to a point where you only need to repeat the copyright statement in your copyright manifests. Therefore there's little for court to take away in the first place.
Using GNU as argument for software copyrights is really novel, I can say that for sure...
I don’t think copyright means what you think it means. If the licensing terms allowed you to repurpose the code, then this sort of copyright declaration would be correct. If the licensing doesn’t allow this sort of repurposing, then you still wouldn’t have the right to do this.
I don't think you got my point. This is the main point
“Just a language runtime” is a big statement. If it does nothing smart or special, then why steal it? It would be perfectly legal to make your own API that aped the Java API one-for-one and just named things in your own way. Google specifically didn’t do that, because people’s familiarity with the Java API has intrinsic value, and they wanted to directly leverage that rather than forcing developers to learn their own clone API.
Because it isn't stealing. Google targeted the biggest open technology, made its own implementation. Oracle did not make Java, Sun made Java, Oracle is just leeching on the IP. Let's just jump here
My understanding is that tools like WINE get around this by reimplementing system APIs at a low enough level that they’re not reusing any code at all to even present the interface. This is different from literally copying another company’s higher-level code without permission and using it in your own product.
Wine implements all Microsoft specifics including PE binary format, memory layouts, and the entirety of the Windows API. This all is Microsoft's intellectual property", PE, NTFS, FAT, API specifics. Wine/ReactOS are free to implement them.
Where I fail to understand you is 'at all to even present the interface'. The interface is clonable, as attested by it being there in Wine. The implementation isn't. However, on the other end there are low level interfaces, the ones controlled by BIOS/EFI from ring0 that kernel typically manages. When you require specified interface A on the one side and specified interface B on the other side, the logic in between gets narrowed down as to what typical design and programming patterns are going to be used. Especially considering virtually all operating systems are written in C using the bulk of same design choices.
You can apply all that to Java and the domain of managed languages.
As for copyrights I know exactly what I'm talking about, and what code can be copyrighted and what code can't. There are no issues even if you have to rewrite the implementations yourself because you lost the permissive license of some code base. Software architecture is not practically patentable/copyrightable (because it relies on open engineering principles of open architectures) and it carries 90% of the weight of the good software product. Not the meat in the methods. Example : 386BSD
Last edited by a moderator: