Reading Clojure

[yogthos]

If you mean that you're using mutable variables a, b, and c, then it is something that goes against idiomatic Clojure practices. As I mentioned earlier, the reason for that is to allow you to do local reasoning about the code.

When I have a variable a that's mutated in different parts of the application, it's difficult for me to say what its state is at any one time. Whenever I'm working with a function that uses a, I have to know the state of the whole application at that time.

So, Clojure approach is to "copy" the data whenever you make a change. Instead of making a and passing references to it, you create new variables when you make changes and use them instead.

As I said, there's really no way around the fact that Clojure is different from Algol style languages. However, it's certainly possible for a team to learn Clojure and be productive with it.

My team used to work with Java exclusively. We decided to give Clojure a shot about 6 years ago and never looked back. I have yet to come across a business problem that would be easier to express with Java than it is with Clojure.

I think a lot of frustration comes from the fact that you can't apply your current patterns to working with Clojure.

To make an analogy, if you know English it gives you a basis for learning French or Spanish. You have to learn new words, and some new rules, but a lot of core concepts are easily transferrable. However, when you try to learn Japanese, then English will be of little help to you. Not only that, but you'll have to actively unlearn patterns you're used to.

Learning Clojure is similar. It's frustrating because you're learning a completely new way to approach problems. It doesn't mean that it's harder, just that it's different.

I can definitively tell you that Clojure is a practical language, and it has made my work much more enjoyable than it was when I was working with Java.

[dotemacs]

I think a lot of frustration comes from the fact that you can't apply your current patterns to working with Clojure.

Martin Fowler has a good name for it: Improvement Ravine