Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Java will never "catch up" to Scala (for example, the type system / generics will not evolve in the foreseeable future).

But once Valhalla lands, with some additional JEPs, Java will be very close to the core of what Scala offers. Where there are gaps, some of these can be filled via libraries (think immutables.org, or others providing persistent data structures).

As a matter of fact, these days at most companies that I see the typical deployment model is "micro"services, which you can quickly develop via Spring Boot or the alternatives. No need for ultra complex code or asbtractions, Java does it just fine. And you have all the tooling you need for the enterprise world.

I think Scala is an excellent language for teaching ML-style programming. I would still recommend it for that purpose. But there is no longer a killer app or need for Scala, that would convince most people to use it for new projects.



Just like Scala by virtue of being a guest language on the JVM ecosystem, never will replace Java on the minds of JVM architects.

Kotlin has an advantage here, because ART nowadays is effectly KVM from Google's point of view, where they grudgingly update Java support to keep up with Maven central.

Scala has nothing like this, and the update on Python alongside native libraries, kind of stole its demand in big data, hence why this kind of scenarios is described on the article.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: