[gfodor]

I've been in enough code reviews of Scala that did simple things like string processing that inevitably got sidetracked into a navel gazing discussion about type theory, pattern matching, and functional programming to not go near the language again anytime soon. You simply couldn't understand the code without understanding tons of incidental complexity about the language.

The Clojure community has its navel gazing of course, but every time I've been exposed to some crazy idea in that community it was always through the lens of providing real leverage for real problems. Most of the time when I've dealt with people trying to explain concepts to me for Scala code, I've walked away wondering what the point of it all was (beyond the fun Computer Science.)

[pkolaczk]

Maybe you should first learn the language? It would save your time, really. You must know the language to understand programs in that language. Simple as that.

If you don't want to learn FP or you don't value type-safety, Scala is simply not for you.

[geoka9]

> Maybe you should first learn the language?

Is it actually possible? I've been using Scala for over a year and still have to spend more time learning about the language than writing code in it.