[pianoben]

Android folks have good reason to have anti-Java bias. Their bias, as it happens, is against old Java, which they are constrained to use as fallout from the Oracle lawsuits of yore. Kotlin breathed new life into Android in a meaningful way.

On backend teams, I've not personally encountered much anti-JVM bias - people seem to love the platform, but not necessarily the language.

(yes I know there's desugaring that brings a little bit of contemporary Java to Android by compiling new constructs into older bytecode, but it's piecemeal and not a general solution)

[pjmlp]

Lies, damm lies.

They cherry pick whatever they feel like from OpenJDK.

And even though Oracle was right, given that Android is Google's J++, in this case they had better luck than Microsoft.

They don't take more from OpenJDK because then their anti-Java narrative doesn't work out.

But there is some schadenfreund, to keep Kotlin compatibility story relevant they are nonetheless obligated to keep up with is mostly used on Maven Central, thus the updates up to Java 17 subset.

[pianoben]

Maybe I'm wrong about the state of Java in Android today - it's been a few years since I did that work full-time. But I do remember when Kotlin broke on to the scene in 2015, and most of us were thrilled to finally move beyond Java 7! The embrace of a non-Java language was grassroots and genuine; Google's adoption came several years later.

J++ though, now that is a blast from the past! I think I still have a J# book from my student days, somewhere :)