Hacker News Reader

Comment by _halgari | Hacker News Reader

After Emacs/Cider/whatever crashed/locked up on me for the 20th time I finally gave up and moved to Cursive over a year ago. I've never looked back, it's fast, does what I need it to, and I still discover features all the time (like the clojure.test integration!). It's also a fantastic way to get new programmers into Clojure. No need to download lein, or dozens of packages or learn a text based editor. Just install InteliJ and install a single plugin.

Great work.

View on HN

I'm having a very good experience with cider/emacs lately. version 10 has breakpoints and stepping, code reload... it's working pretty smoothly for me now, both osx and linux.

I tried cursive a week ago and I only got breakpoints working once. I'm not used to intellij so that might be my fault, but I couldn't make it work so after an hour or so I just went back to emacs. I'm really a vim person at heart, but for clojure, emacs seems to fit the best. Well not emacs really, but the ecosystem.

And the debugging support. Good. Debugging. Support!

This really cannot be repeated enough times.

After 2 years without it you go back in and it's so seductive you almost want to stop writing unit tests.

Ignore this feeling even as you bask in it! :D

Any tips on using it? Breakpoints in the chrome dev tools and `debugger` are a huge part of my JS workflow, but I've been having trouble wrapping my head around the InteliJ UI. I basically just want to be able to pause the program, see/move up the call stack, and use the REPL with local variables.

You just click in the gutter to create a breakpoint and start a debug REPL - look at the IntelliJ Run menu.

let's not forget crazy stuff like going into debug mode and then evaling random clojure code in the context of the debugger

Best of all is "stop when this exception is thrown". I use that to start 90% of my investigations.

This post is enough for me to decide to get this NOW.

If you're interested in the debugger, I spoke about it at Clojure/West this year: https://www.youtube.com/watch?v=ql77RwhcCK0. It shows how the debugger works and I talk about the problems debugging Clojure code, of which there are many.

Reply on news.ycombinator.com