Kotlin solves most of the problems for us while leveraging the benefits of the JVM.
They cannot fully embrace the JVM while targeting ART, JS and native at the same time.
That 3D graphics library using SIMD and value types from JVM on ART or JS?
Good luck achieving the same perfomance and memory semantics.
Kotlin/Native has already been rebooted as its memory model was incompatbile with JVM libraries.
From the app side you just don’t use classes that you can’t use?
It will be interesting to see how things like Valhalla and Loom will pan out.
The main company behind Scala changed its name and now also offers Java consulting.
Unless the project requires Spark, there is little reason to even care Scala exists.
Then there is the version 3.0 where they started having brain damaged ideas like changing the whole syntax.
Scala today is Kotlin in 10 years.
One benefit of being old in this industry is having survived multiple fashion waves of guest languages on each platform, then watching how those guest languages fade while the platform languages adopt some of their features.
Or even how whole platforms become irrelevant making it a complete moot point regarding whose languages are on the platform.
There has been a consistent increase in Scala jobs in the last 12 months according to Indeed.com
We are talking about Java as a language, not the JVM as a platform.
You can also run Python on the JVM.
Although, some Java compromises are definitely linked to the JVM.
Jython is stuck on 2.7 and unmaintained.