Like many other Clojure hackers, I sometimes think about what I would call my book about programming in Clojure. The obvious names are taken: Programming Clojure and Clojure Programming. The Joy of Clojure is a memorable name (and my favorite book so far, but it leaves out a few things and is already dated.) And don’t forget: Practical Clojure and Clojure in Action.
So I’ve mulled over a few ideas and finally settled on my favorite. I hereby claim the title:Functional Clojure. I assume that a blog post is sufficient to keep anyone from stealing my idea.
This library leverages the Selenium-WebDriver Java library to drive real GUI browsers like Firefox, Chrome, Safari and Internet Explorer, providing both a thin wrapper over the WebDriver API as well as higher-level Clojure functions to make interacting with the browser easier.
A nice bit of early history, and an explanation of how it affects today’s Clojure community.http://clojure.com/blog/2012/02/17/clojure-governance.html > One consensus that came out of the Clojure/dev meeting was that we need to get better at using our tools, particularly JIRA. We would like to streamline the processes of joining Clojure/dev, screening patches, and creating new contrib libraries. We also need better integration testing between Clojure and applications that use it. Application and library developers can help by running their test suites against pre-release versions of Clojure (alphas, betas, even SNAPSHOTs) and reporting problems early.