The truth is, if you're a .NET programmer, you're going to find Clojure slightly painful because you're switching ecosystems. Using it for work will encounter

The truth is, if you're a .NET programmer, you're going to find Clojure slightly painful because you're switching ecosystems. Using it for work will encounter the same problem and ClojureCLR is a second class citizen. That's not to say it isn't great and useful, it is. I'm noticing a couple of trends in Clojure development: big data and esoteric. Take a look at Storm (twitter's data processing engine) and Overtone.