4 ms·
I'm a big fan of Scala, though I think the sweet spot for Scala is for a small team with pre-existing Scala's expertise. For a one-person project, I definitely
by tanin 6y ago
I'm a big fan of Scala, though I think the sweet spot for Scala is for a small team with pre-existing Scala's expertise. For a one-person project, I definitely use Scala. I used to use Ruby a lot.
You can move fast with safety with the caveat that the code quality is harder to manage/control.
Contrasting this with golang where they really take the guard rails to the other extreme (e.g. can't compile if a variable is unused, not even compiling just to test it out locally).
Another weak-point of Scala is that the learning curve is steep, especially when it involves SBT, the defacto build system for Scala.
- lihaoyi 6y agoWe're scaling out Scala to a larger team here at work, and part of the effort is certainly about putting in guardrails. In fact, a lot of it is putting in thr guardrails people like from Go: enforced autoformatting, banning unused variables, fatal warnings, etc. are all just a flip of a switch these days (though we only enforce these things on-merge, people are free to test locally regardless, which I understand is a big pain point in Go!)
- tanin 6y agoYup, golang's guardrails are great, but they should be enforced on CI... not while coding locally.