Well, ok, map and reduce are not the mental model behind Clojure, but understanding it allows developing in Java and using closures efficiently. You need a different mental model to successfully implement this. The average Java developer does not understand it, or even when he does, has no need for it. I do wonder where Java is heading with adding closures. Knowing how to develop in OO Java does not help for developing in Clojure, even though it has interop with Java.

When talking about languages like Clojure it is crystal clear that this is a new language it comes with its very own concepts you need to understand before you can develop. And I was pretty much attracted by Clojure when Howard Lewis Ship demoed it yesterday in his session. I like programming with them in JavaScript. Closures can reference state that is no longer existing outside their scope.Ĭlosures are neat. But it is basically a piece of code that gets its own life. But what is the hype?Ĭlosures are tricky to explain. While it is nice that you will be able to switch() on Strings, have a modularized platform and other cool stuff, one thing is a bit odd: the hype Closures get. A hot topic here at the Devoxx were the upcoming Java editions with their features and changes in the language syntax.

Download the new OkMap Desktop 17.11