3 ms·

I looked at Clojure back in 2010, and from from 2012 I've managed to work with it full time. Love it! The only Java-esque thing you need to decipher are the po

I looked at Clojure back in 2010, and from from 2012 I've managed to work with it full time. Love it! The only Java-esque thing you need to decipher are the potential stack traces. But that's becoming easier with each new release, and it's actually quite easy to find the Clojure-namespace (= file) and line number you need to focus on, just by scrolling through the usually not too long stack trace.

sgt 7y ago
Perhaps a silly question, but what would be the real-life benefits trying to convert a Java team to Clojure in 2019?
- iLemming 7y ago
  - Productivity. Bulding stuff in Clojure is not only joyful but also can give you real (not imaginary, not theoretical, but real, measurable) boost; - Concise syntax. Less code - less bugs; - FP. Immutability by default is something that once you get used to it, it is hard to imagine having to write code without it; - REPL. I mean real REPL, not some kind of crippled "interactive shell". e.g.: Jupyter is interactive shell, Clojure (just like any other Lisp) has a "real" REPL;
  - sgt 7y ago
    Would you use the REPL to inspect / modify / debug running applications in production, or would it mainly be useful for development purposes?
    - iLemming 7y ago
      If you do it right, you won't need to inspect/debug prod. But nothing stops you from enabling socket REPL, connect to it and try things there. Just like NASA fixed their failing spacecraft in 1998 during Deep Space 1 mission.