Ep 036: Why Do You Recommend Clojure?

Functional Design in Clojure

It's summertime, and that means it's time for something new. Each week, we will answer a different question about Clojure and functional programming.

If you have a question you'd like us to discuss, tweet @clojuredesign or send an email to [e-mail].

This week, we're starting off with "Why do you recommend Clojure?". We take turns sharing our favorite reasons, and we can't help but have fun riffing on how enjoyable Clojure is to use. Come along for the ride.

Selected quotes:

• "Question everything else. Clojure is the answer."
• "Once you discover structural editing, you'll never go back."
• "Data is inert. It can't act."
• "When dealing with mutable data and side effects, it's like trying to add a domino in the middle and make sure to not break the chain."
• "Most of the time, running with scissors is considered to be a bad thing."
• "Somebody in Java has done all that plumbing that you don't really want to do."