On the JVM world not really.
Or is it both at once?
Kotlin is to Java (on Android) as Swift is to Objective-C (on Apple) - the successor primary platform language.
Feels like an environment that moves so quickly (to someone like me anyway). Can barely keep up.
https://talkingkotlin.com/the-first-kotlin-commit-in-android...
Kotlin and Java are the main languages supported on Android.
They are still using Android Java on the system layers, because they aren't rewriting the whole stack.
Even the update for Java 11 LTS subset on Android 13 is mostly likely caused by the Java ecosystem moving forward, than the willingness of Android team to support anything other than what can be desugared into Java 8 / DEX somehow.
You are right in relation to JetBrains, they even acknowledge it on their blog post introducing Kotlin.
https://blog.jetbrains.com/kotlin/2011/08/why-jetbrains-need...
"And while the development tools for Kotlin itself are going to be free and open-source, the support for the enterprise development frameworks and tools will remain part of IntelliJ IDEA Ultimate, the commercial version of the IDE. And of course the framework support will be fully integrated with Kotlin."
Also, Oracle's lawsuit against Google for copying Java APIs.
0 of our recent or current projects still use java.
Google is either moving/extending libs to natively integrate with kotlin (numerous -ktx libs) or they are kotlin-only (Compose) anyway.
I don't really see the Jetbrains lock-in thing, because: Android Studio is free, you can use any other IDE with syntax highlighting and the terminal to run tests & to compile.
If you want to blame someone for locking in android devs into Android Studio, it would be Google, because they build the previews into Android Studio afaik. But you would have the same criticism at Apple/XCode. Supporting one IDE is already tough I guess.
> If only [Oracle] hadn't sued Google, Java would still have been the pre-eminent language for Android development. Sadly Android is stuck at legacy Java 8 permanently now. So, modern Java is stuck as a server-side language with dozens of competitors.
A reply argued that Android is on Java 11 now, and then you noted (hi!) that it's "a subset". Huh.
I'm trying to get a handle on understanding the ramifications of the legal/licensing situation, and the actual concrete impact on Java's use in Android. The subject seems somewhat murky and opaque. Is there possibly a high-level disambiguation about what's going on published anywhere?
The lawsuit was about Sun’s license that explicitly demanded a purchase for use on mobile devices for their Java programming language (as that was the area they wanted to get money from). Google instead copied most of the APIs and called it a day, and Oracle bought Sun and went after the lawsuit.
But since the license changed in the meantime so that OpenJDK is completely open-source and has the same license as the Linux kernel, it was all about an older state of things.
You can check the Javadoc for the standard library, and the JVM specification. Then compare with DEX/ART and the Android documentation for Java APIs.
