[giggles_giggles]

I'll speak for myself. I just jumped ship from a Scala team and took a pay hit to get out because it was so horrible. No one on the team had a strong command of the language, which made it worse. The application was a ball of mud. The week I left, proposals to rewrite everything in Java were heard. I took a position on a Go team and am much happier.

[wirrbel]

I wouldn't jump ship to a Go project, but I am currently in the situation you fled from. Even the core team who started the project doesn't have command of the language. I have some experience with rust and Haskell (hobby) and JVM experience with Java and clojure so I can get by but it is not pleasant.

I think the situation is similar to c++ where too many features have been added over time.

While with c++ there is a body of compiled recommendations on what not to use and how to write c++, for scala that doesn't really exist.

[pkolaczk]

This has nothing to do with languages. I saw the same happening in a company writing pure Java, JS or Python. Doing a project with people who don't have command of whatever stack they are using is asking for trouble.

On the flip side, Scala can be a very pleasant stack to work with if you have right people on the team.

> While with c++ there is a body of compiled recommendations on what not to use and how to write c++, for scala that doesn't really exist.

Principle of least power is what you need.

[sideeffffect]

> for scala that doesn't really exist

https://nrinaudo.github.io/scala-best-practices/