Our great sponsors
tick | timbre | |
---|---|---|
3 | 5 | |
583 | 1,432 | |
1.0% | 0.3% | |
6.2 | 7.6 | |
about 1 month ago | 6 days 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.
tick
- A History of Clojure (2020) [pdf]
-
Help finding a webdev framework that works out of the box
Some projects like https://github.com/juxt/tick are cljc compatible and will make life easier if you plan on sharing a lot of code, so make sure to look out for that when choosing libraries
-
Rich Hickey and Brian Beckman (2009)
- You want your dates to behave the same on client and server? You got it: https://github.com/juxt/tick
= You want your logging/debugging code to be the same? You got it: https://github.com/ptaoussanis/timbre
timbre
-
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]
Mentioning μ/log and no mention of timbre (https://github.com/taoensso/timbre), that is an odd omission. Malli is a great mention, but there ought to be a mention of clojure.spec (https://github.com/clojure/spec.alpha) which has much more mindshare.
-
Rich Hickey – open-source is Not About You
If you're not familiar with lisps in general, it might be hard to grok the differences between lisp-macros (as used in Clojure) and "normal" macros you see in other languages.
But, if you are familiar already, and just wanna see examples of neat macros that makes the API nicer than what a function could provide, here are a few:
- https://github.com/clojure/core.async/blob/master/examples/w...
- https://github.com/weavejester/compojure
- https://github.com/ptaoussanis/timbre
- https://github.com/krisajenkins/yesql
-
Build and run Clojure projects. CLI, tools.deps and deps.edn guide
When clj is invoked, two libraries will be available in our code: timbre logging library which artifacts taken from Maven, and test-runner, taken from GitHub.
-
Tour of our 250k line Clojure codebase
No, I don't think they were hyped at any point.
They are used in certain libraries like https://github.com/ptaoussanis/timbre but for things that are simply not possible without macros, for example (timbre/spy (+ 1 1)) will actually print both the expression and the result:
DEBUG [ss.experimental.scratch:1] - (+ 1 1) => 2
Perhaps if the macros are "simple" they can be unpacked relatively easily. I do understand how mentally challenging that can be for somebody who's just starting with Clojure. I've been using Clojure for ~8 years and only just recently became more comfortable with macros after I made a conscious effort in that direction. I'm still far from an "expert" in them.
What are some alternatives?
aero - A small library for explicit, intentful configuration.
mulog - μ/log is a micro-logging library that logs events and data, not words!
integrant - Micro-framework for data-driven architecture
hiccup - Fast library for rendering HTML in Clojure
rlwrap - A readline wrapper
mount - managing Clojure and ClojureScript app state since (reset)
clip - Light structure and support for dependency injection
re-frame - A ClojureScript framework for building user interfaces, leveraging React
clj-new - Generate new projects based on clj, Boot, or Leiningen Templates!
warp-estimate
test-runner - A test runner for clojure.test