Perhaps a silly question, but what would be the real-life benefits trying to convert a Java team to Clojure in 2019?
Re:Ask HN: Best Lisp for software development?
by iLemming on Monday July 29, 2019 @04:20AM
(#20552526)
- 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;
Would you use the REPL to inspect / modify / debug running applications in production, or would it mainly be useful for development purposes?
Re:Ask HN: Best Lisp for software development?
by iLemming on Monday July 29, 2019 @10:34AM
(#20555010)
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.
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.