Clojure 2014 Year in Review
My unscientific, incomplete, thoroughly biased view of interesting things that happened with Clojure in 2014.
Visit stuartsierra.com → RSS feedOn Hacker News Apr 2009 – Mar 2018
My unscientific, incomplete, thoroughly biased view of interesting things that happened with Clojure in 2014.
Another year, another year-in-review post. To be honest, I feel like any attempt I make to summarize what happened in the Clojure world this year is largely moot. Clojure has gotten so big, so — dare I say it? — mainstream that I can’t even begin to keep up with all the interesting things that are happening. But it’s…
This is a guide on naming Clojure functions. There are exceptions to every rule. When you’re defining something based on natural language, there are more exceptions than rules. I break these rules more often than I follow them. This guide is just a starting point for thinking about how to name things.
A new year is upon us. Before the world ends, let’s take a look back at what 2011 meant for everybody’s favorite programming language:
Laziness is often useful. It allows you to express “infinite” computations, and only pay for as much of the computation as you need.
This is my third Clojure year-in-review post. In 2011 I was excited about Clojure 1.3, ClojureScript, and the second Clojure/conj. By 2012 I was blown away by four Clojure conferences, two O’Reilly books, reducers, Datomic, Immutant, and a partridge in a pear tree.
There’s a big ‘ol thread going on down at comp.lang.lisp about Clojure vs. Common Lisp. I’m biased, of course, but I have to say that Clojure and Rich Hickey are holding their own against some of the top c.l.l. flamers.