In my last post, I said I was in Italy on vacation and you may be thinking to yourself (most likely not, but just go with it) “what high tech gizmos did he bring with him on his travels?” and I would happily reply “A book!", yes a paper book. Being a software developer, I have access to tons of technology, more so when it comes to paper book replacements but there is just something about a real book that makes reading and learning for me better than using a computer, tablet, or doohickey.
Another really great advantage of a paper book is if you happen to lose a book when traveling its much less money to replace than a fancy gizmo. Also, I’m guessing that most people will not be interested in stealing a book on the next hot programming language, but you never know.
So, all this is a long about way to talk about the book I’m reading right now which is “Clojure For the Brave and True” by Daniel Higginbotham. Why Clojure? Being a functional programming language, I always had it in the back of my mind as something to learn but sadly never on the top of the list. After hearing a good number of people talking about Clojure I figured I would boost it up the list and give it a look and I’m happy I did! They’re tons of good reasons to learn Clojure, I’ll talk about some interesting points I have found so far.
Besides the unique syntax, Clojure has immutable data structures that are useful for anyone that has worked on a large application before and found it hard to understand the flow of data. Immutable data structures typically forces an application structure that creates easy to understand flow by using pure functions that take inputs and return outputs. Because pure functions are easier to reason about and to test, we are starting to see similar ideas appear in other languages along with libraries for languages without immutable data structures.
Clojure also has something that I have only played within Haskell before, lazy evaluation. This is a very interesting concept where you can hold off on evaluating a value until the point it’s needed, so if you have something that takes a significant amount of computational time you will only pay the cost when you use that value in your code. This also lets you create sequences of infinite length but only use what you need, this is something that really fascinates me because you really start thinking about solving problems in different ways.
Clojure embraces a lot of the ideas found in other functional programming languages but it is also more of a pragmatic language which makes it easier to do real work and get things done quickly. To contrast this, I enjoyed learning Haskell but I couldn’t get past solving small exercises on Exercism due to its pureness, but with Clojure, I have already been able to build some small real-world apps. (Haskell is a great language but does focus on different values then Clojure)
So, Clojure is great but how is the book? (As you ask in this theoretical conversation) The book is great, I would say it’s one of the greatest programming language books I have read in some time. There is a good mix of humor along with step by step learning of Clojure along with functional programming. So far, every chapter has a fairly good size program that you create as you read through the chapters, along with exercises to do on your own. Overall reading Clojure For the Brave and True has been very enjoyable, and I would recommend this book to anyone that wants to learn Clojure but also anyone that would like to know more about functional programming.