whyline
flow-storm-debugger
| whyline | flow-storm-debugger | |
|---|---|---|
| 2 | 33 | |
| 72 | 634 | |
| - | 2.5% | |
| 0.0 | 9.6 | |
| about 8 years ago | 8 days ago | |
| Java | Clojure | |
| MIT License | The Unlicense |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
whyline
flow-storm-debugger
- FlowStorm a omniscient time travel debugger for Clojure/CLJS
-
What I Have Changed My Mind About in Software Development
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
- ANN ClojureStorm: Omniscient time travel debugging for Clojure
-
What a good debugger can do
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.
-
Debugging Lisp: trace options, break on conditions
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.
-
FlowStorm - Flow Docs, experimental execution derived documentation for Clojure
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.
- Clojure at the REPL: Data Visualization
- [ANN] FlowStorm Clojure[Script] debugger 3.1.259 is out
- Debugging ClojureScript applications with FlowStorm
What are some alternatives?
test-refresh - Refreshes and reruns clojure.tests in your project.
hashp - A better "prn" for debugging
scope-capture - Project your Clojure(Script) REPL into the same context as your code when it ran
logseq - A local-first, non-linear, outliner notebook for organizing and sharing your personal knowledge base. Use it to organize your todo list, to write your journals, or to record your unique life.
sayid - A debugger for Clojure
portal - A clojure tool to navigate through your data.
deps.clj - A faithful port of the clojure CLI bash script to Clojure
penpot - Penpot: The open-source design tool for design and code collaboration
reveal - Read Eval Visualize Loop for Clojure
scittle - Execute Clojure(Script) directly from browser script tags via SCI
Light Table - The Light Table IDE ⛺
watchpoints - watchpoints is an easy-to-use, intuitive variable/object monitor tool for python that behaves similar to watchpoints in gdb.