hashp VS debux

I honestly did not know there were any ClojureScript debuggers out there. I normally use hashp for debugging, but I do occasionally find myself needing a debugger, so I will definitely check this out!

Though very similar to #spy/p / #spy/d, I really like https://github.com/weavejester/hashp. It colors the syntax, shows the expression and the source code location.

The `let` binding is local, so it's referring to clojure.core/+, and outside the function `add` I can use the name `add` to call it. Seems it's handling that case correct?

> I watched a video and it does seem rather complete, but [1] indicates there is no debugger?

I think debuggers tend to be used as a library across many different editors, rather than the editor/plugin providing that functionality. Personally, I don't use debuggers much as the functions I write tend to be small and evaluating small executions with the repl tends to reveal the issue quickly. Sometimes when refactoring others code I've used https://github.com/philoskim/debux to various degrees of success.

I do think cider (https://github.com/clojure-emacs/cider) has stuff regarding stepping debuggers, but I'm not sure how common it is to use it. Maybe other Clojure users can fill me in :)

> . I also don't see a profiler mentioned

Yeah, as you said, the Java ecosystem basically covers that. For OSS stuff, I use VisualVM, and for professional stuff I use YourKit, both of them work well with Clojure and points out my user-space code with ease. And I've never been paid anything for actually writing/maintaining Java code, so even with that, seems I'm able to use those tools just for Clojure :)

> As an aside, by "continuations" did you mean "restarts"?

Ah yes, of course. The condition system and restarts :) Thanks!

To debug a threading macro you definitely should take a look at debux https://github.com/philoskim/debux .

Really cool! I've used https://github.com/philoskim/debux for somewhat similar(nested prns); I find the horizontal UX quite interesting.