Hacker News Reader

Comment by ithrow | Hacker News Reader

Clojure is an elegant language that gets ugly really fast as soon as you have to squeeze little performance out of it or use Java APIs. Both of which you will have to do for "real world" production applications.

View on HN

Could you be more specific? At OrgPad.com (a tool for basically doing first _useful_ mindmaps which you can actually work/ learn with) we have a few tens of thousands of lines of code in ClojureScript (front end) and Clojure (back end) and pretty much all performance problems I can think of were naive algorithms or bad usage of components (which, usually, a better wrapper solves quite well). You can watch a bit about how we use Clojure in this video: https://www.youtube.com/watch?v=4UoIfeb31UU

Otherwise, we use IntelliJ Idea + Cursive but I keep an eye on emacs and vim Clojure/ ClojureScript capabilities.

Seems like this is being downvoted, but I’d be interested in hearing more from both sides on this. I’ve only played around with trivial Clojure programs and don’t know anything about the pains (or joys) of “real world” applications. Any good discussions on this somewhere?

I’m inferring that you had a negative experience using Clojure somewhere. FWIW, I’ve seen Clojure code that was quite readable and well-organized, operating in an environment that handled more traffic than most enterprise developers are accustomed to.

Reply on news.ycombinator.com