scope-capture
lumo
scope-capture | lumo | |
---|---|---|
9 | 5 | |
557 | 1,894 | |
- | - | |
0.0 | 0.0 | |
over 1 year ago | almost 2 years ago | |
Clojure | Clojure | |
MIT License | Eclipse Public License 1.0 |
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.
scope-capture
-
What I Have Changed My Mind About in Software Development
Awesome tools.
Personally I can't imagine coding in clojure without scope capture
https://github.com/vvvvalvalval/scope-capture
- Automatic function argument / return value collection
- Using def within the threading macro. Is there a better way of doing this?
-
Python dataclass equivalent
I haven't tried it myself. I generally just use truss for runtime constraint checking. I use a modified version that integrates scope-capture. And malli validation for more complex cases, but I try to limit that. For me it is better to validate individual attributes as needed, vs validating an entire "type"/collection of attributes. So each function only cares about the attributes that it needs, and validates only as needed.
-
Love Clojure, challenged by discoverability
Use scope-capture to observe the actual data flowing through the system
-
Clojure unique way of debugging
Scope capture library https://github.com/vvvvalvalval/scope-capture automates this approach.
- The Clojure debbugging way with scope capture
-
Let, try and other code blocks in the REPL
Is anyone aware of any prior art along the lines of this? I've seen scope-capture but it's more about instrumenting existing programs than writing new ones interactively.
-
Data-Oriented programming and LISP
I am not advocating against the use of a compiler. I am going to illustrate how to reproduce the scope of a program and replay it in the REPL as it is done for instance in Clojure with scope-capture. In some use cases, I find this approach is simpler than using a debugger. This approach is possible only because the data is immutable.
lumo
-
Clojure Scripting on Node.js
Is this similar to Lumo (https://github.com/anmonteiro/lumo)? I would assume Lumo has a faster start time since it boots from a V8 snapshot, but otherwise I'd assume the two projects are similar (except that, of course, lumo is EOL)
- Clojure – Differences with Other Lisps
-
Clojure, but without the JVM?
Lumo: a standalone ClojureScript environment, runs on Node.js. Doesn't seem to have its own reader conditional, uses :cljs.
-
Racket v8.0 is out!
Lumo and Planck (standalone Clojurescript environments, based on Node and on JavaScriptCore with some additional functionality to make it suitable for scripting, respectively), and Clojerl (Clojure implemented on BEAM). Startup times are comparable to e.g. Racket.
What are some alternatives?
clojure - The Clojure programming language
planck - Stand-alone ClojureScript REPL
flow-storm-debugger - A debugger for Clojure and ClojureScript with some unique features.
etaoin - Pure Clojure Webdriver protocol implementation
hashp - A better "prn" for debugging
babashka - Native, fast starting Clojure interpreter for scripting
truss - Assertions micro-library for Clojure/Script
joker - Small Clojure interpreter, linter and formatter.
rebel-readline - Terminal readline library for Clojure dialects
awesome-clojure-likes - Curated list of Clojure-like programming languages.
spec-tools - Clojure(Script) tools for clojure.spec
Fennel - Lua Lisp Language