[pjmlp]

Google abused Sun, took advantage that they were in a critical financial situation not able to sue, and when they crashed, did not move a finger to rescue the company assets.

Now Android has Google's own J++, limiting what kind of Java libraries are portable to the platform.

At the same time, some OEMs are adopting Android instead of Embedded Java, thus increasing the fragmentation about what Java libraries are actually portable.

Google just though they could let Sun close doors and get away with how they created their own J++.

[onli]

That's Oracle propaganda. Sun was perfectly happy with Google using Java and the free entry into the mobile market they got from that. See https://www.zdnet.com/article/a-google-android-and-java-hist..., https://www.zdnet.com/article/sun-ceo-explicitly-endorsed-ja....

[pjmlp]

That is Google propaganda.

Sun did what they could to save their face.

"Triangulation 245: James Gosling"

https://www.youtube.com/watch?v=ZYw3X4RZv6Y&feature=youtu.be...

Also doesn't change the fact that even with Android 8.1, I as Java developer cannot take a random jar from Maven Central and be certain it won't crash and burn on Android, regardless of the version.

[onli]

Good link.

But I don't see how you can tolerate that contradiction. Either you agree with Oracle that the Java APIs were copyrighted and Google should not have been allowed to reconstruct them. Or you worry about fragmentation coming from an incompatible Java implementation. Doing both is nonsensical.

[pjmlp]

What contradiction?

Google should have paid Sun instead of playing a Microsoft's move fostering Sun's downfall, period.

And in doing so, Android would have been JavaSE compliant plus whatever additional libraries they would think to drop on top of it.

[onli]

How do you come to the idea that having more Java devices available, even if not 100% compatible, would have in any way caused harm to Sun? And then even that much that it killed the company?

On top of that, I don't see for what google would have had an obligation to pay.

Contradiction: Google broke some imaginary copyright by re-implementing APIs, but Google is bad because the re-implementation was not 100% equal to the original causing fragmentation. Either the fragmentation was harmful, then the API copyright was the problem. Or the API copyright violation was the problem, then fragmentation was the explicit goal and Google's try to minimize it the problem. Both can't be true at the same time outside lawyer lala land.

[pjmlp]

Because those devices run Android Java, which Sun saw $0, thus not able to capitalize on it to pay their bills.

1 - Google did not pay for Java licenses, when it should. Even Andy Rubin admits that on his emails.

2 - To this day Android is not Java SE compliant, thus creating a fragmentation between Android Java and Java. Just like Sun managed to prevent with J++

3 - Being a Java license as Google avoided to be, and still isn't (many Java APIs are not yet available on Android), would have required Android to be fully Java SE compliant

So to conclude, Google tricked Sun and fragmented the Java eco-system.

They should pay and provide a 100% Java SE compliant implementation, or be honest about it and fully migrate to Kotlin, Dart or whatever they feel like it.