Busy Monday! Mmm,… let’s see what we’ve got here …
- Developing Google Wave Robots Outside of Google App Engine with Clojure (here, via @theWE_) -- Follow their design and you won't have to re-upload your application every time you make a change in clojure.
- Another #clojure book from Mannings "Idiomatic Clojure" by Chris Houser and Michael Fogus (via @wmacgyver) -- that makes it three slated for next year: this one, "Clojure in Action" by Amit Rathore (Manning) and "Definitive Guide to Clojure" by Luke VanderHart (Apress)
- The case for #clojure (here, via @stuarthalloway) -- It seems that Stu has the rare ability to say a lot with little words. In this article he introduces the titles for four of his upcoming talks, but the titles are full message in themselves, so I'm posting them here individually since they've also been retweeted individually today (you can also access the slides that he is putting together for those presentations):
- "Clojure's sweet spot is any application that has state."
- "Clojure is a better Java than Java."
- "Design Patterns are a disease, and Clojure is the cure."
- "Write functional Clojure and get shit done." -- heh... "Getting Shit Done" is also my wife's version of GTD (Getting Things Done)
- Rich Hickey has been busy thinking about new possible features for Clojure. Here are two relevant tweets:
- From Java to Clojure (here, via @weakreference) -- "Patrik Fredriksson takes us on a tour from Java to Clojure, by using a step by step conversion from one language to the other. If you're a Java programmer who wants to know a little bit about Clojure, make sure you come along."