top | item 46718748

(no title)

pshirshov | 1 month ago

Well, what are the alternatives?

> Small but fragmented ecosystem

You may contribute more! Also, with a language like Scala you don't need that many things readily available, you may just create them yourself tailored to your needs, Scala is expressive enough to be your framework on its own.

> sbt

Write your own build tool, dammit. I'm working on one.

> Language is dying

Not really. It's just not in the spotlight and never has been. But people feel entitled and moving away from Scala instead of making contributions.

> Go

If you are seriously switching to Go, not code-generating Go but writing code manually - that, probably, means you've never mastered Scala.

discuss

order

bunderbunder|1 month ago

I wouldn’t say “never mastered Scala,” but it is a strong sign that Scala was never the right tool for the job on the first place. Go is a non-JVM systems programming language that is proudly procedural and generally eschews most of the key features of both object-oriented and functional programming. Scala is pretty much the opposite of that, so much so that it’s strange to me to think of them as competitors. They are both good languages, but the only overlapping use cases I can think of offhand are implementing command-line tools and Web APIs, which are a use case for almost every language because realistically you should just do both of those in whatever language you were already using for everything else.