Tony Morris

No, I am dead serious. We all take it extremely seriously. I have no idea how you reached a conclusion otherwise. Because of "projections of personal opinions and preference"? What do you think the rubbish documents contain?

Thats fair, a coc generally contains community preferences. I was mainly referring to “Don’t use scala. Not even then.” The rest is strait forward, actionable and useful. I don’t think this is a technical position, but rather a personal preference based on passes disputes.

It is very very very very very very very very very definitely a technical position. It is a widely held position, though if you are relatively new to Scala, you probably don't know that. I had zero contribution to that part of our CoC.

I know there are some people who hold that opinion. Mainly by people who think pure FP is the one true way. Scala doesn’t really shine for pure FP, so I can understand the reasoning for those people. From what I’ve seen, I wouldn’t say it’s a widely held opinion though.

No. From people who know Scala well. This division into "people who think pure FP is the one true way" is a part of the narrative that you have fallen into adopting. It doesn't exist. It's entirely a fabrication. You believe it's not widely held due to an understandable bias.

Ok, so what are the key technical points that make scala unusable in your opinion? (I’m truly interested in knowing if there is something I’m missing)

Well, again, twitter cannot do justice to such an excellent and important question. Here is a *very generous* run down. https://www.reddit.com/r/haskell/comments/1pjjy5/odersky_the_trouble_with_types_strange_loop_2013/cd3bgcu/ …

I have seen that post before. @kemtt is squarely in the pure FP camp, and the issues mentioned primarily arise when doing pure FP. I don't agree that those limitations make Scala unusable. There are many successful companies that use Scala heavily, with great success.