Clojure's big idea however is not FP or OOP+FP+Lisp, it's data. All idiomatic Clojure programs will attempt to represent their app state via Clojure data structures (vectors, sets, and hashmaps). Functions are then the simplest way to do transformations from one dataset to another. Bonus points to those who also make those functions composable via more data. Then you start to build a system with real power.
But on a different note, the reason why I program in Clojure rather than Haskell is that Clojure is so pragmatic. The JVM gives me access to almost every library I need, the JIT and GC are the fastest on the planet (for this sort of language). But most of all, Clojure trusts me. Clojure doesn't attempt to slap my hand when I make an impure function. It doesn't say "hey we can't figure out what type this function returns". Because at the end of the day, I don't care about that stuff. I only really care about writing good software, that fulfills my goals. If that means certain parts of my code are impure...I don't give a crap.
At least that's the way it's been for me for 4 years working with the language.
But on a different note, the reason why I program in Clojure rather than Haskell is that Clojure is so pragmatic. The JVM gives me access to almost every library I need, the JIT and GC are the fastest on the planet (for this sort of language). But most of all, Clojure trusts me. Clojure doesn't attempt to slap my hand when I make an impure function. It doesn't say "hey we can't figure out what type this function returns". Because at the end of the day, I don't care about that stuff. I only really care about writing good software, that fulfills my goals. If that means certain parts of my code are impure...I don't give a crap.
At least that's the way it's been for me for 4 years working with the language.