[ghostwriter]

> Even the best Scala IDE (IntelliJ IDEA) is poor and nothing better is to be expected in the next years. This is basically the point where you could cross out Scala from your short list of programming languages!

What do you mean? I use Community version of Idea for Scala3 and syntax highlighting, refactorings, jumping to definitions, javadocs, usage points, sbt integration, and build targets are all working as expected. The only thing that I noticed as issues are module reloads: sometimes a tab has to be re-opened for the inference engine to notice changes, but that's not a deal-breaker when it comes to IDE experience to me. What else do you need from it?

> I'd say that Scala is not a good citizen in the Java world. This is problematic in existing code bases. Kotlin is a much better fit there.

The current version of Kotlin is lagging behind Java 19 features like improved pattern matching. Why would anyone bet on Kotlin if there's a mix of modern Java+Vavr[1] and Scala3 to be had instead?

[1] https://docs.vavr.io/

[cryptos]

The point to tooling was based on the original authors assessments. My own experiences are a bit dated, but I had problems with valid Scala code that wasn't understood by IntelliJ. The reason was probably that this IDE relies on its own analysis and not on the official compiler and nothing has changed in this regard. But I'm happy to hear that you are satisfied so far.

The problem with Java/Scala interop is that you can hardly use idiomatic Scala code from Java, while this no issue with Kotlin.

You're right about patter matching. It is sad that Kotlin doesn't have more to offer. But Kotlin has some nice things not present in Java like named parameters with default values, (limited) reified generics, proper covariance / contra variance, extension methods, first-class functions and what not.