- Check out #ClojureScript talking to #Clojure over #WebSocket (via @neotyk) -- It's a web chat application.
- Ahead-of-time function scheduler for Clojure (via @maclausen) -- This is a library extracted from Overtone that let's you schedule the calling of a function for some time in the future. A nice way to freak yourself if you have a memory like mine (The computer is alive! It's calling functions on it's own!)
- Document Repository written in Clojure (via @maclausen) -- Well, clojure and clojurescript. This is a product that's been opensourced and that will have also a commercial offering.
- #Heroku supporting #Clojure: "It was also a natural choice because we use and love Clojure for ourselves" (via @jmeydam) -- An infoQ article about Heroku's multi-language support in which, amongst other things, quotes one of the founders of Heroku talking about why they support clojure.
- Why use keywords as symbols (in #lisp)? (via @jneira) -- Interesting article about why do keywords exist in Lisp when symbols would be enough, but also provides some insight on why do people actually use them.
- First successful #clojure build on travis-ci.org by our own @michaelklishin, how to set up (via @travisci) -- Travis is a Ruby-based Continous Integration server for Open Source projects. Looks like making it build a clojure project is simple enough.
NOTE: By overwhelming popular request (well, a suggestion by a single individual…) I am trying a new way of linking referred articles/pages in each tweet report, following a W3C recommendation. This change should let clojurians suffering of musophobia easily click on the links (i.e. they browse with the keyboard, not the rodent). Not sure sure I can fully follow these recommendations since they seem geared towards calls to action, which most tweets are not, but I’ll try for a while and see how it goes, or better, you tell me how it goes!
Keep the suggestions coming!