map is one of the staples of functional programming. It’s totally useful and also surprisingly simple. Let’s look at some examples and annotated code.
If naming is one of the two hardest things in programming, it follows that every other possible solution (except those few involving cache invalidation) should be attempted before naming something. As a corollary, bad names are a code smell.
The Google Closure Library provides a nice interface to the HTML5 History API. Coupling it with Secretary is very easy. But not all browsers support HTML5 History. In this post I’ll talk about one way to make sure you have client-side routing in all browsers.
The world may be mutable, but people have been using the notion of immutability to build reliable systems for a long time.
I made a clojure.test cheatsheet that you can get for free.
Zachary Kim will talk about mobile development in Clojure.
Soren Macbeth will talk about data crunching in Clojure.
Timothy Gardner and Ramsey Nasser will talk about Arcadia.
Sean Johnson will talk about pattern matching.