5 ms·
You certainly write Android apps using the Java API, which is Sun/Oracle IP. The argument there is no "real" Java in Android actually hurts Google's case. Becau
by throwawaykf05 11y ago
You certainly write Android apps using the Java API, which is Sun/Oracle IP. The argument there is no "real" Java in Android actually hurts Google's case. Because Dalvik uses non-Java byte code, these apps are not interoperable with "real" Java apps. This completely undermines some of Google's legal arguments as a defense for API copyrightability, because the cases they cited (Sega etc) explicitly held that copying certain things was OK for maintaining binary interoperability.
- Zigurd 11y ago> "You certainly write Android apps using the Java API" So Oracle should go after Eclipse and other IDEs? Or Apache Harmony? > *" This completely undermines some of Google's legal arguments as a defense for API copyrightability, because the cases they cited (Sega etc) explicitly held that copying certain things was OK for maintaining binary interoperability." That binary compatibility is required by javac, which is in the toolchain. Then the Java bytecode gets translated to Dalvik bytecode and packaged as an APK.
- throwawaykf05 11y agoOracle can go after who ever they want as long as the law allows them to. I don't see how they can target IDEs, though. IDEs don't provide the Java API. One way translation of byte code is not interoperability. Android apps cannot interoperate with "real" Java apps.