建立CN-Clojure群组，对clojure有兴趣的朋友都可以加入，希望在国内能有一个交流的场所 (here, via @killme2008) -- Cool! A Chinese clojure email list. Here is a short post that describes the intents of the cn-clojure list (here is the non-translated version)
Clojure wrapper for OpenKinect! (here, via @jonromero) -- Man, doesn't this look like a fun project?! "The advantage of having a REPL is HUGE. You can play around, experiment and test many libraries on-the-fly." REPL + Kinect = Win!
Non-breaking error handling in Clojure: Part Deux (here, via @kumarshantanu) -- Here is part one. What if instead of throwing an exception, you just returned it as a value? What could you do with it?
When an Agent Calls Another Agent in Clojure (here, via @ralfbn) -- It is actually quite cool how clojure handles this; and you get to write stuff like @@ref
Анафорические макросы на Clojure (here, via @fproblogs) -- Anahporic macros are macros that let you refer to the results of a previous calculation. Writing an anaphoric 'if' in some lisps is relatively easy, but Clojure makes it harder because macros in clojure can't capture a variable name. This article proposes a solution. Here's the English google translation in case you Russian is not that great.
A tour of the Clojure landscape (here, via @ycombinatornews) -- "I am working on an automatically-generated, browseable directory of Clojure libraries. If I am viewing a library in such a directory, the directory should be able to give me a list of other libraries that I should consider instead, as well as a list of libraries that work well with this one. The directory application could infer such information automatically based on how often various libraries are used together on Github." The article comes with a good summary of the findings while graphing the clojure project relationship map.