This is the biggest appeal for me as well. I find that Clojure hits the sweet spot between being simple and flexible.
It has small and consistent syntax coupled with pervasive immutability. I find that when I work with Clojure, I'm rarely thinking about the language itself.
Since the core language is very small, it's un-opinionated. This makes it easy to extend it in the way you need for your particular domain.
Many languages today have the same features and allow you to do everything Clojure does and more, however most of these languages are also far more complex.
I've come to realize that language complexity has a huge impact on productivity and code quality. It's incidental mental overhead that distracts you from the problem you're solving. The more syntax and rules you have the harder it becomes to tell whether the code is doing what you think it's doing.
We also use Clojure at work alongside Ruby, and I'm continually pleasantly surprised to find the benefits of using an immutable-by-default language. I like the functional programming aspects of programming in the large and small, but those advantages pale in comparison to the idea that data should be immutable except when absolutely necessary.
I dabble in Elixir in my spare time, and that language appears to yield similar benefits. Again, immutability is the key, not necessarily the functional focus. While immutability is more difficult to implement in OO languages, I would be curious to see what that looks like.
It has small and consistent syntax coupled with pervasive immutability. I find that when I work with Clojure, I'm rarely thinking about the language itself.
Since the core language is very small, it's un-opinionated. This makes it easy to extend it in the way you need for your particular domain.
Many languages today have the same features and allow you to do everything Clojure does and more, however most of these languages are also far more complex.
I've come to realize that language complexity has a huge impact on productivity and code quality. It's incidental mental overhead that distracts you from the problem you're solving. The more syntax and rules you have the harder it becomes to tell whether the code is doing what you think it's doing.