Clojure: The Language That Will Change How You Think About Programming
Clojure will affect the way you think about programming (2017)

Clojure is the ideal language for expanding your programming mind, argues Eli Bendersky. As a modern Lisp with full macro support, persistent data structures, and built-in concurrency tools like core.async, it forces you to think about code as data. Even if you never use it in production, learning Clojure will positively affect how you write code in other languages.
A language that doesn't affect the way you think about programming, is not worth knowing.
- TN1ck
There was a time in university where I started my days with doing some 4clojure puzzles. I became so obsessed, I managed to solve almost all of them. It's wild what an impact these few weeks had on my programming abilities. It's a beautifully designed language that makes you think in data structures and their transformations.
As a side note: I code Clojure in Lightroom. It was so cool to see your code instantly evaluate and trace through your functions.
- ajasmin
I love the thoughtful approach to programming that Clojure exemplify.
MVP churn and AI fatigue is getting to me. Need some good Hammock Time!
- darksaints
By a weird stroke of luck, clojure was one of the first languages I learned. And yeah, I guess it left a lasting impact on me in the form of an appreciation for immutability and dataflow programming.
Unfortunately it also left me with an extremely deep distaste for dynamic types, and in particular, the blind usage of lists and maps for everything. The ML family of languages finally gave me a paradigm worth keeping around.
- tikotus
In the era of LLMs, I often stop to think of Clojure. I believe it had a significant role in popularizing the concept of immutable data structures. Immutability simplifies the required context for understanding and solving problems. This benefits both humans and LLMs.
Would an LLM, or a person solely coding using them, have had the insight to work out that immutability is the way to go, and we should revolutionize software develoment? If LLMs had happened 15 years ago, would all code still be "place oriented programming", with higher token counts and less reliability than we have today thanks to better practices we've learned in the recent past?
If so, what are we missing out on in the future, now that stopping and thinking about code is frowned upon?
- sourdecor
I recently found out you can use Malli type providers[0] with Typed Clojure[1] to get instant feedback when developing!
So you can do this when programming:
(m/=> foo [:=> [:cat :int] :int])
(defn foo [t] (inc t))
(foo 1)
[0]: https://github.com/typedclojure/typedclojure/tree/main/examp...