[osdev]

The Scala language is great but the ecosystem sacrifices simplicity for pure FP. Scala has always suffered from complexity problems due to libraries. For example, using Http/JSON/Database libraries have always been a lot harder than they need to be due to a die hard approach to pure FP.

Scala 3 looks pretty good, but I just can NOT see myself using Scala again, after having worked with it for 4-5 years at work and on personal projects. I write mostly/reasonably FP code without using Cats/Category theory. I’ve recently moved all my code from Scala to Kotlin and I’m loving it, found the perfect balance with Kotlin.

[hocuspocus]

> For example, using Http/JSON/Database libraries have always been a lot harder than they need to be due to a die hard approach to pure FP.

Hu? There are plenty of alternatives to the pure FP ecosystem.

HTTP: Dispatch, Requests-Scala, literally any Java client if that's still too FP for you

JSON: uPickle, Play JSON, or simply Jackson

DB: ScalikeJDBC. Quill and Slick do a lot more but are not particularly die-hard FP either.

[edem]

Same here. Kotlin is a pragmatic language and it is a much better fit for the "Turbo Java" role that Scala originally wanted to do.