Reid Draper introduces Knockbox, an eventual consistency toolbox for Clojure inspired by Statebox, discussing some useful use cases, how to perform garbage collection and testing while using it.
Jim Crossley introduces Immutant – an application server for Clojure, inspired by TorqueBox and powered by JBoss AS7 –, showing a demo application, how to use it, and exploring its API.
Alan Whitaker presents a Clojure application that is used in a pilot program meant to help children with ADHD to improve their condition.
Baishampayan Ghose discusses creating custom data types in Clojure, covering: types vs. records, interfaces and corresponding protocol, mutable types, and example implementations.
Amit Rathore discusses DSLs in Clojure along with an example of using Clojure to provide real-time dynamic pricing for online retailers at Runa.
Paul deGrandis examines three startups and their technology needs, risk and tradeoffs, presenting how Clojure did its part in their success.
Chas Emerick makes a critique of Clojure outlining its weak points related to namespaces, declare, dynamic scope, STM, JVM and others.
Kevin Lynagh discusses information design and why he thinks programmers suck at that, and how one can implement great data visualizations with Clojure and ClujureScript.
Alan Dipert discusses the benefits of functional programming in Clojure, suggesting using pure functions to process values and sometimes explicit procedures for needed side effects.
Rich Hickey discusses the design decisions made for Datomic, a database for JVM languages: what problems they were trying to solve with it, the solutions chosen, and their implementations.
Stuart Halloway shares advice on creating evident code that scales. Evident code is software that clearly expresses its meaning and purpose.
Bradford Cross recommends creating custom libraries containing composable abstractions instead of monolithic frameworks, exemplifying with Flop, Store, Graph, and Newsfeeds, all written in Clojure.