mount
mulog
Our great sponsors
mount | mulog | |
---|---|---|
4 | 4 | |
1,210 | 469 | |
- | - | |
4.5 | 4.6 | |
about 2 months ago | 16 days ago | |
Clojure | Clojure | |
Eclipse Public License 1.0 | Apache License 2.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.
mount
-
A History of Clojure (2020) [pdf]
* Lifecycle management: Mount, Integrant or Component (https://github.com/tolitius/mount https://github.com/weavejester/integrant and https://github.com/stuartsierra/component)
-
Any resources for "current best practices and learnings?"
Allesandra Sierra’s Component has lots of competitors now: first mount which has since fallen out of favor for integrant. There’s newer ones too, like clip and donut-power.
-
Building a Live Streaming app in Clojure
As soon as the ec2 boots up, it runs the cloud-init script, which starts the Clojure process and mount (a state management library) that would then starts the dependencies:
-
[ANN] Reveal Pro 1.3.308 — sticker windows for system libraries (component, integrant, mount)
Today I released a new version of Reveal Pro — dev.vlaaad/reveal-pro {:mvn/version "1.3.308"} — that adds sticker integration for system libraries such as mount, component and integrant!
mulog
-
Tracing: Structured Logging, but better in every way
There are logging libraries that include syntactically scoped timers, such as mulog (https://github.com/BrunoBonacci/mulog). While a great library, we preferred timbre (https://github.com/taoensso/timbre) and rolled our own logging timer macro that interoperates with it. More convenient to have such niceties in a Lisp of course.
- A History of Clojure (2020) [pdf]
- Logging verbosely into a ring buffer?
-
Debugging in Clojure
Assuming the crash doesn't cause the process to completely exit, you could indeed use `scope-capture` for this. This works well for local dev. In theory, you could use `sc.api/spy` in production code, and then attach a remote repl to diagnose any crashes. I wouldn't recommend this though, I think it would be best to use a good logging library like Mulog: https://github.com/BrunoBonacci/mulog
What are some alternatives?
integrant - Micro-framework for data-driven architecture
timbre - Pure Clojure/Script logging library
component - Managed lifecycle of stateful objects in Clojure
re-frame-10x - A debugging dashboard for re-frame. X-ray vision as tooling.
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.
debug-repl - A Clojure debug repl as nrepl middleware
aero - A small library for explicit, intentful configuration.
clj-otel - An idiomatic Clojure API for adding telemetry to your libraries and applications using OpenTelemetry.
closeable-map - Application state management made simple: a Clojure map that implements java.io.Closeable.
cider - The Clojure Interactive Development Environment that Rocks for Emacs
system - a dependency injection library for Clojure and ClojureScript 🍩 [Moved to: https://github.com/donut-party/system]
spyscope - Trace-oriented debugging tools for Clojure