News for hackers. Stuff that matters.

A comment on Clojure and the technology adoption curve.

Re:Clojure and the technology adoption curve by msluyter on Tuesday November 10, 2015 @11:43AM (#10540369)
Let's say I'm sold on Clojure (I am; I think it's awesome) and I want to convince my boss to convert a crufty Java 7 enterprise app to a better alternative. What is the argument for Clojure compared to, say, Kotlin? How difficult is a complete conversion to Clojure compared to other JVM alternatives. My guess, in terms of ease of transition:

  Java 8 > Kotlin > Scala > Clojure
That's just my impression, especially if you're risk averse and want to make improvements as incrementally as possible. But I could be wrong. Anyone have a good counterexample?
[ Parent | on HN ]
Re:Clojure and the technology adoption curve by astine on Tuesday November 10, 2015 @12:13PM (#10540618)
Clojure's strongest selling point as compared to other JVM languages is probably its concurrency story. If your enterprise app is of any sort of size, you've probably run into concurrency related bugs.

Another strong advantage is the development lifecycle. It's much tighter thanks to the live coding built right in. This should make it much faster to catch bugs or feel out new code. You can also use this to implement zero-downtime deploys and patching.

[ Parent | on HN ]