I am a brand new Clojurist, having just finished reading ‘Clojure for the Brave and True’ this past weekend. I come from the not so distant land of Common Lisp, where it occupied nearly all of my free time for 10 years, and before that I dabbled in Python for a couple years.
I have heard lots of nice talk about Clojure in the last 1-2 years, and I always dismissed it as “just another Lisp”, not bothering to look into what it was about. For the same amount of time, I have read multiple books on about a dozen different languages, hoping to find one that interested me enough to use in addition to Common Lisp. While there were a lot of languages that interested me, most of them were either too immature, or too difficult to use in a practical manner, so it left me continuing to use Common Lisp exclusively for a long time.
Last week, about half way through a book on Haskell, I decided it wasn’t what I wanted, and decided to look at a language closer to home: Clojure. I just so happened to have a copy of “Clojure for the Brave and True” that I bought not too long ago, and over the weekend I read it.
After reading that book and viewing a few Clojure keynotes on the Internet, it pretty much changed the way I think about programming and how code should be written. Clojure is the nicest language I have ever seen, hands down. At this point in time I have only written about 100 lines of code, and I can honestly say that Clojure is not going to become my secondary language alongside Common Lisp – it is most definitely going to become my primary language.
I still have a lot to learn, coming from Common Lisp, a language which has encourages me to write in a mutable fashion, and which is lacking lot of constructs of Clojure, but that is a journey I look forward to.