That is good but I have used Scala before and would not recommend it for an enterprise project. It was rather convoluted and had lots of concepts that just would not make sense to the java programmers in our company. There would be teams that could have used it and thrived but overall the complexity of the language seemed to outweigh any reasons I could give to use it. I wish them the best but I think they will have…
This really just amounts to vague hand-waving that language complexity somehow impacts productivity. Do you have any evidence to back up this fear? C# seems to have done reasonably well in the enterprise, and it has much greater complexity than Java. It doesn't have all the flexibility of Scala but for common use cases I think they are actually pretty comparable. Same goes with F#, which is not tailored to everyone's…
Really, the "unsuitability" of Scala for the enterprise says as much about the common problems with enterprise development (What, expect developers to learn something new?) as it does about Scala.
I say that as someone who currently does C# work in an enterprise environment in which there is a ban on using "var" to declare variables with type inference.
Apparently
Dictionary> dictionary = new Dictionary>();
makes it really clear what the variable type is, but var dictionary = new Dictionary>();
makes people's brains hurt.Sigh.