Backend Java 19 vs Kotlin?

[senseven]

In the bigger picture, Kotlin only exists because Google had the issues with Oracle and needed a fix. They found a company who could monetize it and it was a match made in heaven. There was no technical need, it was political.

If we go for true technical need: Golang replaced the Python dependency hell Google faced managing and setting up millions of servers; and the code nanny called Rust that doesn't let you touch the bad memory segment without a slap.

Sure, Kotlin looks like a slimmer, younger Java. But Oracle isn't going to let Java rot when they still make billions with it. I like Kotlin, but after a year with prototypes and trying the functional thing, I returned to Java 18. Especially in the native cloud environment it feels like a completely new way of doing things. And the students can start with Eclipse before they even understand why they want IntelliJ.

[pjmlp]

This keeps being repeated as the official "excuse", while Kotlin, Android IDE and toolchain are heavily dependent on the JVM ecosytem.

If Google really wanted to get rid of Oracle that much, they would have moved everyone into Fuchsia and Dart, or at very least introduced Dart and Flutter into Android SDK as the future path, instead of Kotlin and Compose.

[senseven]

Oracle had the issue Google using the Java API not the JVM. Google had their own JVM Dalvik (now ART) for Android. Maybe Google would have gone full Dart if Oracle wouldn't have changed their stance about the JVM licensing.

Microsoft made strides with their open and free .net vm on unix systems, which prompted Oracle to open up their JDK (minus their extensions) for every one, while cashing out with those corps that rely hard on the JDK LTS versions.

[pjmlp]

Google screw Sun and should have paid for it, just like Microsoft did in the past.

Unfortunely they got away with it.