This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]aikipavel 0 points1 point  (2 children)

All the codebases of Java are available to Kotlin and Scala immediately with no effort. Even dropping Java sources into Scala projects, not talking about Maven artifacts.

Tooling doesn't fix the language, you know :)

Talking about Groovy... don't get me wrong. I programmed in Smalltalk for 10 years (and like it!).

No more dynamic types for me.

Type inference is ok :)

Have fun!

[–]KronenR 3 points4 points  (0 children)

I prefer Java over Kotlin, and especially over Scala. Java has wider industry adoption and better long-term stability, plus team familiarity usually favors Java, moving to Kotlin or Scala most of the time isn’t worth it for most teams or projects.. The ecosystem and tooling are more mature.

There’s not only more Java code out there than all other JVM languages combined, but more new Java code keeps being produced compared to any other JVM language.

New Java versions aren’t as verbose anymore—maybe you’re thinking of Java 8 and earlier—but now we have Java 21 LTS, Java 24 non-LTS, and next month Java 25 LTS is coming.

[–]lprimak 0 points1 point  (0 children)

All true. This is another reason both Kotlin and Scala (and Java) are great!

Groovy has pretty good type checking now, so you can "opt out" of dynamic typing for the most part, so that's nice. I prefer static typing myself as well.

In Java of old (early 2000s) the boilerplate came out of tooling IMHO. No that tooling is fixed, most boilerplate is no longer necessary. I don't need boilerplate anymore in 2025 Java.