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… Continue reading Clojure 2015 Year in Review
My unscientific, incomplete, thoroughly biased view of interesting things that happened with Clojure in 2014.
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. For 2013, where do I even start? So much has happened this… Continue reading Clojure 2013 Year in Review
I signed off my Clojure 2011 Year in Review with the words You ain’t seen nothing yet. Coming back for 2012, all I can think of is Wow, what a year! I’m happy to say that Clojure in 2012 exceeded even my wildest dreams. 2012 was the year when Clojure grew up. It lost the… Continue reading Clojure 2012 Year in Review
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: Clojure 1.3.0 was released, bringing better performance to numeric applications, reader syntax for record types, and other enhancements. ClojureScript was unveiled to the world, leading to universal confusion about how to… Continue reading Clojure 2011 Year in Review
From 2011 to 2015, I wrote an annual Clojure Year in Review post, attempting to summarize all the interesting things that happened in Clojure in the last year. After 2015, I gave up. There was just too much happening, and I couldn’t keep track of it all. A couple of years ago, I got tired… Continue reading Clojure Start Time in 2019
Quick link: Stuart’s ns Style Guide Everyone has their own personal quirks when it comes to syntax. No matter how hard you try to lock it down with code review, IDEs, scripts, or check-in hooks, individual differences will emerge.