• Video-materials about Clojure (here, via @alexott_en) -- Yesterday I wrote about the Russian version of this page with links to all sort of clojure-related videos. Alex Ott, as promised, posted an English version of this page.
  • in cambridge and interested in #clojure or lisp? #camclj at the kingston arms 8pm tonight (here, via @fmu) --  That's in Cambridge, UK. This might come a little late though.
  • Performance characteristics of functions operating on different Clojure data structures (here, via @stilkov) -- A very helpful summary of the how each of Clojure's data structures perform in relation to the number of elements contained in them and the operation performed.
  • Number of monads in Clojure 1.0: Zero. In 1.1: Zero. In 1.2: Zero. Monads are not idiomatic (via @stuarthalloway)
  • ProtoTurtle gives a gentle introduction to Protocols in Clojure (here, via @LauJensen) -- A fun exercise that will help you solidify your knowledge of the new Protocols in Clojure; a knowledge, no doubt, acquired after watching this recent and nice video from @stuarthalloway)
  • In two weeks time next #amsterdam #clojure meetup, that is Wed 12th of May. Proudly hosted by #sourcesense (here, via @neotyk)
  • #clojure 1.2 gets some new seq fns! (here, via @stuarthalloway) -- group-by, flatten, partition-by, rand-elt, reductions, shuffle, frequencies and includes? have moved from clojure-contrib to clojure.core. Some saw their name also changed in this transition: rand-elt -> rand-nth and includes? -> seq-contains. This was to better reflect their applicability an their performance characteristics. Read all the rationale in the linked post. (Also, check out this post for more info about what might be broken if you upgrade to the latest 1.2 build)
  • #clojure philosophy: right data structure for the job via semantics. (here, via @wmacgyver) -- Interesting pointer to a mailing list entry by Rich Hickey summarizing the reason why not all data structure operations exists for all data structures. A hint? Performance; why would you want to perform an operation on a data structure that is very slow for such operation? Data structures matter. Consider their performance characteristics when choosing them.