4 ms·
> Google admited several times that they haven't done a clean room reverse engineering > It is undisputed that Google copied verbatim the declaring code of the
by shakna 9y ago
> Google admited several times that they haven't done a clean room reverse engineering
> It is undisputed that Google copied verbatim the declaring code of the 37 Java API packages—11,500 lines of Oracle’s copyrighted code. It also copied the SSO of the Java API packages. Google then wrote its own implementing code.
The only problem with Google's implementation is the copying of the API.
---
> If Google cared so much, they could have bought Sun, but they were expecting it would just crash and burn, while the company would get away with it.
> The parties were unable to reach an agreement, in part because Google wanted device manufacturers to be able to use Oracle’s APIs in Android for free with no limits on modifying the code, which would jeopardize the “write once, run anywhere” philosophy.
> in any event that the jury must have found that Google did not act in bad faith
Google tried to get a reasonable license.
---
Even CAFC has said that if Google had not received advertising revenue from Android, their use of the APIs would have fallen under fair use. They are not a Java vendor.
- pjmlp 9y ago> They are not a Java vendor. Last time I checked https://developer.android.com/ https://developer.android.com/ and https://developer.android.com/guide/platform/ https://developer.android.com/guide/platform/ has the word Java written all over the place. So apparently they license an operating system, that makes use of Java, the language, and a subset of its standard library, to the point that it affects the sales of other Java vendors. On my naivety it makes them a Java vendor to me.
- shakna 9y agoStrangely I can only find 'Java API'. > The entire feature-set of the Android OS is available to you through APIs written in the Java language. > Build toolchains, such as Jack, compile Java sources into DEX bytecode, which can run on the Android platform. Seems they make no use of the JVM... Which would be required to vend it, no?
- pjmlp 9y agoA JVM is only one possible implementation of the Java language. A few Java vendors on the embedded space also provide their own implementations, where .class files are converted either into their special VM format or straight into native code, before generating the firmware image for deployment. Android uses Java the language, alongside a partial implementation of Java the standard library. The way it is implemented, is like any other programming language, a detail. The fact that I can pick any Java library that compiles under that subset and use it on Android is expected by any Java developer. Likewise embedded vendors that sell C compilers, even if they aren't fully ANSI C compliant, still acknowledge they are selling C compilers.
- shakna 9y agoYou seem to be confused on a few points. The court case is that Android infringes on Java SE, not the Java language. The question is if it infringes on the platform, not the language. > Android uses Java the language, alongside a partial implementation of Java the standard library That's not what is being disputed. They use an API written in Java, afterall. > Likewise embedded vendors that sell C compilers, even if they aren't fully ANSI C compliant, still acknowledge they are selling C compilers. And Android has a compiler for Dalvik and AR. That's not up for dispute either. That doesn't make them a vendor for Java SE. No more than the compiler in GCC makes the GNU project a vendor. > A few Java vendors on the embedded space also provide their own implementations, where .class files are converted either into their special VM format or straight into native code, before generating the firmware image for deployment. Usage of the Java brand requires any platform you ensure compatibility between your implementation and all other implementations [0]. The Android SDK is not compatible to the letter of that trademark license, as the Android SDK is both a subset, and also extends the Java API, so Google followed their license by not claiming it. --- The only thing being disputed, is if their Java-written API is allowed to reflect Java SE's API. Google is a library vendor for a library that reflects a subset of the host language. They also have their own compiler for a subset of the language. > Likewise embedded vendors that sell C compilers, even if they aren't fully ANSI C compliant, still acknowledge they are selling C compilers. This is more akin to claiming that a C++ compiler is infringing on a C compiler by both being compatible with a subset of the C language. [0] > This resulted in a legal dispute with Microsoft after Sun claimed that the Microsoft implementation did not support RMI or JNI and had added platform-specific features of their own. Sun sued in 1997, and, in 2001, won a settlement of US$20 million, as well as a court order enforcing the terms of the license from Sun. As a result, Microsoft no longer ships Java with Windows.