Oddbean new post about | logout
▲ ▼
Alex Nedelcu | 1 years ago (raw) | export | reply | flag 
 With #Java's evolution (discriminated unions, pattern matching, virtual threads), are #Scala/#Kotlin still worth it?

Scala & Kotlin have a culture of doing things at compile-time, the former more so than the latter. 

This yields safety & expressiveness, and is reflected in features that Java will never implement, in platforms that it will never target well, or in paradigms it will never embrace.

Java is still Java, and you're stuck with Spring, Hibernate, and Jackson, sorry.
▲ ▼
f8542214 | 1 years ago (raw) | root | parent | reply | flag 
 @54814b2f that sounds rather ominous 😄
Jokes apart, in terms of expressiveness I fully agree. But what about the features that will never be implemented? Getting pattern matching, for example, on Java seemed already an astronomical leap forward. So what could be the ones that will never make it?
▲ ▼
3c1b5818 | 1 years ago (raw) | root | parent | reply | flag 
 @54814b2f I'm enjoying Kotlin, but I have to venture into Java just as often, and I can say I still appreciate developments there. I once heard Brian Goetz explain InvokeDynamic in the JVM at a DevOxx congress, which was instrumental in Scala and Kotlin even existing, and for Lambda expressions, and I was impressed with how they make these feature puzzles, with Java acting as a custodian of compatibility.

#Java #Scala #Kotlin #jvm