[sigy]

I'm quite surprised by this request, given that Kotlin doesn't really improve on classic Java language problems to a quantifiably better degree than later JLS improvements. Further, Kotlin seems to bring along its own design baggage from the very beginning which makes it little more than a distraction for most users I've seen try to pick it up.

[Snacklive]

Disagree. Have you ever use Kotlin? Because it's such a wonderful and simplified experience compared to Java

[justbaker]

Java is moving in a much better direction compared to when Kotlin first came around.

[andrekandre]

as someone who has used both (on android) a bit, i also prefer kotlin, but not by such a huge margin that java makes me feel bad.

aside from nullability and a few conveniences, what are some examples that really push it over the top for you?

[muzani]

Java 8 has nullability plus some of the sexy functional programming stuff like map and filter.

I think Kotlin's real selling point is things like lambdas. You get stuff like Jetpack Compose, which become much more readable with it. Stuff like combine() mixed together with coroutines, which helps a lot with anything async (UI, local and remote DBs).

A practical example is combining multiple different sources into one LiveData or State variable. It's a way to asynchronously update stuff without a lot of mental overhead.

[andrekandre]

  > I think Kotlin's real selling point is things like lambdas. You get stuff like Jetpack Compose, which become much more readable with it. Stuff like combine() mixed together with coroutines, which helps a lot with anything async (UI, local and remote DBs)

that makes a lot of sense, and yes, i'd miss that if it wasn't available in java as well, thanks!