I write Scala for my main job and I find it very hard to recommend. This talk is a hopeful, but brutally honest about some of Scala’s shortcomings. Good watch 👍
Are there other reasons, not covered by the talk, that make it hard for you to recommend Scala?
In one word (and I’m cheating a bit here because it was alluded to in the talk), sbt. I feel like it’s almost every other day where I’m debugging some dependency issue.
Also, is your workplace planning on sticking with Scala?
That’s kind of a controversial topic at the moment. We have one service written in it, so we have to maintain a Scala service at the very minimum.
TL;DR:
(Best effort, corrections welcome.)
for extra clarity - sacrifice the object-oriented half of the community in favor of the functional half (with the OO half going to Kotlin)
I write Scala for my main job and I find it very hard to recommend. This talk is a hopeful, but brutally honest about some of Scala’s shortcomings. Good watch 👍
Are there other reasons, not covered by the talk, that make it hard for you to recommend Scala?
Also, is your workplace planning on sticking with Scala?
In one word (and I’m cheating a bit here because it was alluded to in the talk),
sbt. I feel like it’s almost every other day where I’m debugging some dependency issue.That’s kind of a controversial topic at the moment. We have one service written in it, so we have to maintain a Scala service at the very minimum.