AFAIK it’s an excellent language let down by political in-fighting in the ecosystem and subsequent fragmentation of is otherwise ‘standard’ libraries. IMO this kills the language.
Kotlin offers most of what Scala does with a much more solid and supportive ecosystem, it’s the obvious winner in the ecological niche of ‘better JVM languages’, for me.
I don’t think that’s a fair representation. Like for any community, you tend to hear the most about a vocal minority, and drama there was, indeed. That’s not unique to Scala, that doesn’t mean that a majority was engaged in it or was affected by it.
The point about fragmentation holds, though: Scala is a multi-paradigm language, so you tend to have communities assembling around core set of libraries and abstractions that fit their specific needs. It’s not a bad thing from an engineering perspective (you get to pick the most adequate tool for the job), but it will be intimidating at first, and understandably ridiculous when coming from a different ecosystem that you’ve a choice of a dozen or so JSON deserializing libraries. https://index.scala-lang.org/ Is a great help, though.
What makes it that bad?
AFAIK it’s an excellent language let down by political in-fighting in the ecosystem and subsequent fragmentation of is otherwise ‘standard’ libraries. IMO this kills the language.
Kotlin offers most of what Scala does with a much more solid and supportive ecosystem, it’s the obvious winner in the ecological niche of ‘better JVM languages’, for me.
Been a while since I’ve used Scala, but I remember Scala being much more focused on functional programming than Kotlin.
I don’t think that’s a fair representation. Like for any community, you tend to hear the most about a vocal minority, and drama there was, indeed. That’s not unique to Scala, that doesn’t mean that a majority was engaged in it or was affected by it.
The point about fragmentation holds, though: Scala is a multi-paradigm language, so you tend to have communities assembling around core set of libraries and abstractions that fit their specific needs. It’s not a bad thing from an engineering perspective (you get to pick the most adequate tool for the job), but it will be intimidating at first, and understandably ridiculous when coming from a different ecosystem that you’ve a choice of a dozen or so JSON deserializing libraries. https://index.scala-lang.org/ Is a great help, though.
Scala is essentially Java so most of Java criticism applies.