clojure-site VS flow-storm-debugger

> At least in the official docs, things should be cleaned up and made much more user friendly.

The source of clojure.org is at https://github.com/clojure/clojure-site/ and it gets a pretty constant stream of updates these days (it even accepts PRs!). It's a huge improvement over what it used to be -- so it depends on what/when you're comparing it to.

If you have specific criticisms or suggestions, I expect they'd be welcomed.

I'll concede the docs could be improved but, hey, feel free to open an issue or PR here https://github.com/clojure/clojure-site instead of arguing with everyone on Reddit, eh?

Eventually, I'm sure there will be a 4th edition of Programming Clojure and it will cover those tools in greater detail, but if you find issues or questions, feel free to file them at https://github.com/clojure/clojure-site/issues or ask on https://ask.clojure.org .

succession - the following of one value after another, as opposed to "updating", in which one value displaces another. Discussion at https://github.com/clojure/clojure-site/issues/188

The ^ macro actually annotates metadata onto the value that read, rather than the resulting runtime value. This is mentioned in the last paragraph on the metadata page, and there's some more explanation in this Github issue.

These are good points and I'd welcome feedback at https://github.com/clojure/clojure-site/issues

Tracing debuggers give you the best of both worlds. I've recently started using Flow-storm [0], by @jpmonettas), and it's been quite transformative. You can still easily see the values flowing through your system (better than just "prints"), and it can handle multi-threaded / async scenarios quite nicely. You don't need to manually step through code, you can just "see" your data flow, and when you have loops or some other form of iteration, you can see the data for each pass. Coupling this with a good data visualization tool (such as Portal [1]) really feels like magic. I've been doing Clojure for quite a few years now, and was very happy with my plain REPL-driven workflow, but this is way better.

[0] https://github.com/jpmonettas/flow-storm-debugger

[1] https://github.com/djblue/portal

This is another example, a tracing time travel debugger for Clojure https://github.com/jpmonettas/flow-storm-debugger

Supports a bunch of stuff described there and more.

Lisps have some good tooling around debugging, for example clojure's flowstorm or common lisp which has built into the language most of what this article is talking about.

There's some good debugging tooling for Clojure as well. A recent entrant is https://github.com/jpmonettas/flow-storm-debugger and of course there's the estabilished pretty full featured debugging features in CIDER (Emacs), Calva (VS Code) and Cursive (IntelliJ). And for barebones tracing from REPL there's goo old clojure.tools.trace.

For Emacs there is something already if you use the Emacs integration described here https://github.com/jpmonettas/flow-storm-debugger/tree/flow-docs/editors.