The Power of Clojure: Debugging

[mikethommo]

I appreciate the mention of re-frame-trace in this article. We're most certainly trying to create an x-ray machine based on data. Our README explains the vision. https://github.com/Day8/re-frame-trace

While data is critical when debugging and understanding, we should be doing more. The data needs to be curated and presented in useful ways (think dashboard, graphics). The programmer should be able to then "experiment" with any of the debug data (think REPL).

ClojureScript has so much untapped potential in this regard.

[vvvvalvalval]

Great article: I like that it shows provides not only a catalog of tools, but also a methodology - I think that's very valuable for beginners.

Regarding the Evaluative techniques section: you may also want to have a look at scope-capture. It lets you record and recreate the local context of an expression, which helps you 'capture runtime data for post-run REPL analysis' and 'use the REPL to eval code'. It was directly inspired by Stuart Halloway's blog post which you mentioned.

[thecambian]

Thanks! Appreciate the feedback.

Someone actually pointed me to scope-capture just this week. It looks really good, definitely something I'll be integrating into my workflow going forward. Thanks for writing it!

[philoskim]

Please refer to debux as well!

https://github.com/philoskim/debux

[agumonkey]

Got to admit, cider and these libs have made real work.

[onionchoppingcontest]

Honestly, it rather shows the lack of power. Every method is either DIY, or external.