Kotlin vs Java
Cluster focuses on debates comparing Kotlin favorably to Java as a more modern, interoperable alternative, especially for Android development and new JVM projects, with endorsements for switching from Java.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Why not just java? I thought it caught up to kotlin in the past few years
Kotlin is a great option, and isn't a big jump from Java!
Do you see much evidence of Kotlin eating Java's lunch as some have predicted?
Why not Kotlin instead of Java? I feel Kotlin is very underrated.
Thanks for the suggestion! Kotlin looks great under many perspectives, way better than Java probably for my needs
Kotlin is simply a much more modern option than Java in general, and doubly so for the old version of Java used for Android. Giving Kotlin some official backing gives it a lot of credibility. The big argument favour of using Java over Kotlin until now has been that Kotlin was seen as more of a fringe language than the one (Java) officially endorsed by Google. Now that has changed. As a Scala developer I'm quite happy that Kotlin is getting this much attention as I see it as Scala-lite. I do
Kotlin is very similar to Scala, but far less ambitious and not as focused on functional programming. In fact there have been various posts pointing out the similarities between Scala and Swift. It's rather pragmatic but there hasn't been much interest in it so far. Perhaps things will pick up after hitting v1.0. Pitching it as a Java substitute for Android would be a clever move. Java 8 is a poor substitute for Kotlin or Scala, and on Android you're stuck on even more archaic syn
Kotlin is very much threatening Java's dominant position in Android development
> I am sceptical that Scala/Kotlin and many others started in last decade stand chance against Java/Rust/Swift/GoIn contrast to Scala, Kotlin has a much stronger focus on Java interop so its able to much better leverage the JVM ecosystem. In particular, Kotlin hits a really good sweet spot for Android development, where it can still be compatible with older JVM versions, the language features can really increase readability and reduce bugs, and the overhead isn't
I'm a long time Java user. If you are not using Kotlin at this point, you are doing it wrong. That's of course a blunt/provocative statement and there are of course perfectly good reasons for continuing to use Java on some projects. However, most of those reasons are non technical. And I'd argue that 1) Kotlin is a drop in replacement in those projects 2) it's running far ahead in terms of language features that aren't even on the roadmap for inclusion in Java (whic