I am going to semi-quote Rich Hickey (the creator of Clojure): You can do everything in any language, it's about what the language makes idiomatic. So from a v

I am going to semi-quote Rich Hickey (the creator of Clojure): You can do everything in any language, it's about what the language makes idiomatic. So from a very utilitarian perspective, language doesn't matter. However, that's like saying "I can use a square peg for a round hole, just give me a sledge hammer". Clojure, for example, makes concurrency an idiomatic part of the language. In Java, C# or most other mutable OOP languages, that's very much not the case. However, if you seek the utmost concurrency performance on the JVM (and you know how to do it correctly), Java might be a good option for you. So it really depends on what your problem domain is. From my experience, application backend web dev is a perfect fit for Clojure with current hardware since you're most likely utilizing multiple threads in one process. Erlang is also a good language to explore, especially OTP and the way it handles distributed concurrency (the "let it fail" model).