Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage Presentations Clojure after the Honeymoon

Clojure after the Honeymoon



Håkan Råberg and Jon Pither on introducing Clojure to an investment bank team having a large Java code, dealing with cultural differences, the lessons learned, and ways of dealing with legacy code.


Håkan Råberg is Chief of Theory at Ghettojedi Software. Jon Pither writes Clojure at UBS.

About the conference

Intended to be hands-on and interactive, FP Days gives you the opportunity to share experiences with others, find out more about the latest available tools and techniques, network with your peers and have a thoroughly enjoyable experience.The event has a strong, practical focus on learning more about the principles of Functional Programming, using it effectively and exploring possibilities with current FP technologies.

Recorded at:

Jan 04, 2013

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • Rule impact analysis

    by peter lin,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Not to state the obvious, but there's 3 decades of research in rule validation and impact analysis. Rule management is one of the biggest challenges with using business rule systems.

  • The usual weak arguments against static type systems...

    by David Smith,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    ...the argument being given here is "Clojure maps, vectors, etc. are more effective than "complex class hierarchies". Nothing about type theory requires complex class hierarchies or even object orientation; associative maps and vectors are available in all modern statically typed languages.

    There are definitely advantages to FP, and using Clojure's functional data structures over Java's mutable data structures, but this has nothing to do with static v dynamic typing. Haskell has similar data structures with a strict static type discipline.

    I'm not trying to make an argument against dynamic typing -- some of my favourite languages have dynamic type systems. I'm simply against weak arguments.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p