undefined | Better HN

0 pointshhandoko9y ago0 comments

I don't think this analogy is accurate.

It uses Java as the development language, but it has different runtime, not simply a different platform / target, and thus different rules apply.

In regards with the Java libraries, I think this is pretty much already covered in the Google vs Oracle case. Android provides a system implementation that matches the interface, thus these code can work almost seamlessly. Similar to how .NET and Mono works.

0 comments

edblarney9y ago

The Google case showed that they had the right to implement the interface - legally, but that doesn't mean it's not Java.

Syntax = Java Standard Libs = Java 3rd Party Libs = Java Fully interoperable with Java Java IDE's Java Toolchain

= It's Java.

There can hardly be a pragmatic argument against this.

The Google case is a weird one that ultimately involved the nature of APIs and if they can be copyrighted, but by any reasonable definition ... it's Java.

Note that they don't give it 'another name' - so what programming language do you use for Android?

Ask 1000 developers and they will say 'Java'.

They won't say 'something that is exactly like Java, but not actually Java, and which has no name'.

If they deviated the syntax, used a totally different set of core libs, wasn't interoperable with other JVM's and libs ... then I think we could say 'it's not java'.

j / k navigate · click thread line to collapse