And Kotlin makes this debate irrelevant anyway.
And Kotlin makes this debate irrelevant anyway.
Never had a project OK'd to use it, probably never will. They obviously need a PR and marketing department; otherwise they end up being the CouchDB to XYZ's Mongo.
Kotlin is bundled with Intellij Idea. And Kotlin has smaller adoption barrier.
It's not until you've had to hire Java devs that the mystery of why so many people feel the need to ask a question as facile as FizzBuzz becomes clear.
Android is arguably Kotlin's killer app and it is seriously good. The PR for Kotlin is /r/androiddev ;)
OTOH Scala does not have a killer app.
Most spark projects that I have worked on have been in pure java or pyspark. And kafka has been .. well, everything from python to php to ruby.
Spring is adding dedicated Kotlin support in 5.0 which is likely to give it a huge amount of credibility and make companies running on Spring more comfortable with adopting it.
And the collection libraries is where Scala shines comparing to Java. Handling collections in Scala is just so much easier and more fun than in Java. Please try it out if you haven't done it yet.
I worked with Scala collections for 9 years, last 5 years I implement collections for living ;-)
Scala collections are behind in implementation. JSR166 (java.util.concurrent) made large performance progress in Java 8 and 9. It was never back ported to Scala.
Nothing like `ConcurrentNavigableMap` is in Scala. Or Set with weakly referenced keys?
But that hasn't stopped people from writing amazing software in it, which to me says a lot about the power of the language.