In our todays installment of my little „Did you know“-series we won't look at Clojure itself but an important infrastructure topic.
The Clojure ecosystem is growing steadily. New libraries spawn every day. This is a Good Thing™. Tools like maven, gradle, leiningen and ivy make life easier for the developer who intends to use these new libraries. However library developers should pay attention to some details.
ClojureCheck is back.
It brings specification based testing to Clojure and integrates
(almost) seamless with clojure.test. So what does specification
based testing mean and how does it help you?
Sometimes one comments parts of code. Eg. to quickly check a different variant of the code. Or to return a mock value while debugging. Clojure provides several ways to comment code. Some more obvious than others...
Clojure provides a lot of different facilities to handle concurrency. One of
these are Vars. They can be used to store thread-local information, eg. with
binding. A different thread cannot see the value „modified“ with binding.
And exactly there lies the rub…
My GUIs suck. They are hard to use and are a nightmare behind the scenes. In particular, I find it hard to separate the business logic from the GUI code. However I managed to divide these parts in a recent project into 100% disjoint namespaces. Let's see how.
