We're using Clojure at the University Health Network (http://www.uhn.ca/). Our team primarily develops mobile and web applications for clinical use. We started using it about 4 years ago, and now have a number of applications and services written in it.
We're primarily a Java shop and Clojure was appealing because it allowed us to leverage the existing ecosystem, tools, and libraries that we were already using. With Clojure, we were able to develop applications much more rapidly than with Java and we found that the applications were easier to maintain. The latter primarily comes from pervasive immutability and vast overall reduction in code.
We're currently exploring ClojureScript for the client side and already deployed a small app in production using Reagent (http://reagent-project.github.io/). It's worked extremely well for our needs to far.
I was also able to release a number of libraries I developed for work as open source:
We're primarily a Java shop and Clojure was appealing because it allowed us to leverage the existing ecosystem, tools, and libraries that we were already using. With Clojure, we were able to develop applications much more rapidly than with Java and we found that the applications were easier to maintain. The latter primarily comes from pervasive immutability and vast overall reduction in code.
We're currently exploring ClojureScript for the client side and already deployed a small app in production using Reagent (http://reagent-project.github.io/). It's worked extremely well for our needs to far.
I was also able to release a number of libraries I developed for work as open source:
- clj-pdf PDF generation - https://github.com/yogthos/clj-pdf
- instant-pdf service - https://github.com/yogthos/instant-pdf
- Selmer templating library - https://github.com/yogthos/Selmer
- markdown-clj - https://github.com/yogthos/markdown-clj
- reagent-forms - data binding library for Reagent - https://github.com/reagent-project/reagent-forms