3 ms·

* If you use even half of Scala's functional capabilities, Kotlin isn't really an alternative. * What Google does with Kotlin and Android is completely irrelev

* If you use even half of Scala's functional capabilities, Kotlin isn't really an alternative. * What Google does with Kotlin and Android is completely irrelevant to the Scala ecosystem and its users. * On the back-end side, Kotlin doesn't intersect that much with Scala. I haven't met anyone migrating from say, Play to Spring thanks to Kotlin's support. * In the big data world, if you rely heavily on Spark, Scala is still the preferred option on the JVM. Python is a much bigger threat there. * Lightbend and the Scala center have been seriously working on tooling, which is the biggest issue to address compared to Kotlin (Jetbrains has a huge advantage here).

EdwardDiego 7y ago
> I haven't met anyone migrating from say, Play to Spring thanks to Kotlin's support. Hi, now you have :) Well, Vert.x and Ktor, not so much Spring Boot. It's mainly because effective and readable Scala requires a lot more discipline and experience than effective Kotlin for a Java developer. If we'd started solely with experienced Scala devs then I suspect we wouldn't have had an issue. There is, also, the problem of footguns - we've inherited a large Scala codebase from a sister company, and they, unfortunately, let the devs run free. So there's large amounts of hard to debug, hard to read, Scala magic going on. Implicit classes, inherited three levels deep! Macros! Why? Because they could!