News for hackers. Stuff that matters.
Re:State of Clojure 2020 by simongray on Friday February 21, 2020 @03:41AM (#22381760)
I tried learning emacs when learning Clojure, but found IntelliJ with the Cursive plugin to be a much superior experience (the static analysis is awesome). Been writing Clojure for 3 years now (2 years professionally) and I still prefer Cursive to the alternatives, e.g. Atom, Vscode + Calva, emacs. I would say that most of my colleagues with their custom emacs setups still don't have as a good of a development environment as the vanilla experience in Cursive.

I also use parinfer (https://shaunlebron.github.io/parinfer/) rather than paredit, which makes editing Clojure a bit like editing Python. Rather than memorising commands for structural editing, you instead adjust the whitespace using tab/space/delete and the parens reorder themselves accordingly. You can still use paredit commands while having parinfer enabled, but I rarely have a need to.

Re:State of Clojure 2020 by kls on Friday February 21, 2020 @08:06AM (#22382775)
I fells for the same trap and I would caution any readers considering learning Clojure, that do not already know Emacs, to not fall for the same trap. It sets you up for a harder road and increases the chance of failing to achieve your goal. Just use Cursive or Visual Studio Code with the Calva extension and leave Emacs for a later date if that is a goal.
Re:State of Clojure 2020 by bpicolo on Friday February 21, 2020 @09:30AM (#22383339)
Parinfer + Cursive is my strategy too, and I describe it the same way (Pythonish).

This is definitely the least intimidating strategy for ecosystem newcomers.

Re:State of Clojure 2020 by ngcc_hk on Friday February 21, 2020 @05:41PM (#22387700)
Would try this...