4 ms·

So you admit that there was copying. /s But, in all seriousness, the 9 lines + 7 files are damning. It also shows that the engineers who implemented Google's p

So you admit that there was copying. /s But, in all seriousness, the 9 lines + 7 files are damning. It also shows that the engineers who implemented Google's project had been tainted by exposure to Java.

NeutronBoy 11y ago
> But, in all seriousness, the 9 lines + 7 files are damning. It also shows that the engineers who implemented Google's project had been tainted by exposure to Java. I think that's one of the key points. How can you claim a clean-room implementation, when there are (small) portions that have been directly copied? It weakens the case for the rest of the code.
- Oletros 11y ago
  Nobody claimed a clean room implementation because it had nothing to do with the case
- Zigurd 11y ago
  Android uses code from Apache Harmony for many basic Java classes. If any code was copied from Java 6, it would have happened in the Harmony project. Android's use of Java also ends in the toolchain. Android never used a Java(tm) runtime, nor Java bytecode in the runtime. by the time an app hits a device, it's in Dalvik bytecode and either interpreted/JIT-compiled by the Dalvik runtime or pre-compiled to the target system ISA for the ART runtime.
Oletros 11y ago
Implementation was never a problem in this case
dd9990 11y ago
It's more interesting than that. The engineer who wrote those 9 lines was employed by Sun working on Java APIs before working for Google. According to his testimony it was a "fix later" copy/paste mistake he made when improving Sun's OpenJDK code while working for Google.