flow-storm-debugger
reveal
Our great sponsors
flow-storm-debugger | reveal | |
---|---|---|
33 | 7 | |
626 | 594 | |
2.4% | - | |
9.5 | 4.0 | |
10 days ago | 4 months ago | |
Clojure | Clojure | |
The Unlicense | MIT License |
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.
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
reveal
-
Making Hard Things Easy
Clojure does pretty well. See https://github.com/nubank/morse, https://docs.datomic.com/cloud/other-tools/REBL.html, and https://vlaaad.github.io/reveal/.
It's one of the areas that homoiconicity helps: code is data, data is code, so visualization tools can work on both sides.
-
Morse, an open-source interactive tool for inspecting Clojure
I'm glad the MATLAB interface isn't dead haha
This this looks awfully similar to Reveal - (though a first blush it looks less composable and modular)
https://github.com/vlaaad/reveal/
-
[ANN] London Clojurians Talk: Reveal: lessons learned (by Vlad Protsenko)
In this talk Vlad shares his findings after developing and using Reveal daily. Reveal (https://github.com/vlaaad/reveal) aims to solve this problem by creating an in-process repl output pane that makes inspecting values as easy as selecting an interesting datum. It recognizes the value of text as a universal interface, that's why its output looks like a text: you can select it, copy it, save it into a file. Unlike text, reveal output holds references to printed values, making inspecting selected value a matter of opening a context menu.
-
FlowStorm 2.2 new features demo
Neat project. I use Reveal for some debugging purposes but it's not a true debugger like this project. I am looking forward to using FlowStorm in my projects.
-
Sublime (love) Clojure
;; :main-opts ["-m" "cognitect.rebl"]}
Into your '~/.clojure/deps.edn'.
From there I can just add 'rebl' as a profile to my Intellj when you start a REPL it starts automatically.
There are also alternative tools like Portal to do the same things: https://github.com/djblue/portal
Or: https://vlaaad.github.io/reveal/
-
[ANN] Reveal Pro
Reveal is a Read Eval Visualize Loop for Clojure, a powerful and extensible REPL output pane that lives in the JVM. Being in-process allows for easy access to objects, which makes it perfect for data inspection.
-
Which is the best editor to use with reveal?
Check out https://github.com/vlaaad/reveal/issues/2
What are some alternatives?
test-refresh - Refreshes and reruns clojure.tests in your project.
portal - A clojure tool to navigate through your data.
hashp - A better "prn" for debugging
rebel-readline - Terminal readline library for Clojure dialects
sayid - A debugger for Clojure
dot-clojure - My .clojure/deps.edn file
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.
scope-capture - Project your Clojure(Script) REPL into the same context as your code when it ran
is - an inspector for your environment
lumo - Fast, cross-platform, standalone ClojureScript environment