[premium-concern]

I develop in Scala and I honestly have never experienced the concerns you are raising.

"OOP" implies none of things you are worried about and Scala is a great example of that.

I wished people tried the language before making assumptions based on emotions that are not supported by reality.

[pmarreck]

What's the largest Scala codebase you've worked on, and what kinds of challenges have you run into?

[premium-concern]

10000s to 100000s roughly.

I think the important part is to think about how to properly modularize your codebase and not overdoing it. That gets you an "internal" library ecosystem and not only ensures that incremental builds are fast (not really a concern anymore on nowadays) but also fast parallel compiles and deploys.

Code reviews are of course important so that developers are on the same page, but Scala is really great about isolating parts that have to be complicated from the rest (not like Java's " oh, you used a wildcard over there, let's infect the whole codebase with it").

So life is pretty good and I don't think there are huge issues you have to keep in mind compared to other languages, despite the goodness Scala provides you with.

I think most outside concerns are largely overblown: E. g. some people coming from Java might be excited in the first week bring able to define some operators, but it doesn't really matter. Most of the symbols you see in practice are pretty standard (+, -, ... for arithmetic, a few collection things like + (add one thing), ++ (add multiple things) etc.). Going overboard with it is considered bad style, so most libraries out there just don't do it anymore.

Tooling is pretty great overall, although IDEs could always be a bit better.

Compatibility is great and releases are rock-solid, even things like Scala.js which hasn't even reached 1.0 yet.