ALalhazrod·May 8, 2026
What is your opinion on farolero[0]?
[0]: https://github.com/IGJoshua/farolero
In ClojureScript Gets Async/AwaitIGJoshua
farolero
Clojure2021–2026
IGJoshua / farolero
farolero
Thread-safe Common Lisp style conditions and restarts for Clojure(Script) and Babashka.
7Distinct people
8Mentions
0Explicit recommenders
405GitHub stars
What to know before exploring
What it is
Thread-safe Common Lisp style conditions and restarts for Clojure(Script) and Babashka.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year8 dated mentions
Observed mentions: 2021-04-12 00:10:54 UTC to 2026-05-08 09:48:01 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 4 | 2 | 2 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
8 sourcesAlso note an implementation of Common Lisp condition system in Clojure that allows you to have CL-style condition handling: https://github.com/IGJoshua/farolero/
In Idiomatic Errors in ClojureTrue, the CL REPL is more useful than the Clojure REPL, but CL has a 20-30 year head start in development. Plus, Clojure was developed as a hosted language, and runs on .NET, Javascript, JVM, and even Dart (in-progress).
Since exceptions are quite deeply integrated into those platforms (as opposed to conditions), it has "bled through" to the Clojure APIs, and, in turn, REPL.
Folks have written a CL-style condition/restart library for Clojure (https://github.com/IGJoshua/farolero) too. https://www.youtube.com/watch?v=zp0OEDcAro0 video too.
In What makes a good REPL? (2017)Someone added conditions/restarts to Clojure: https://github.com/IGJoshua/farolero
It does allow errors to be caught by the Repl and choose how to handle them.
Honestly though, I haven't found the interactive restarts at the REPL useful. It's way faster to just re-evaluate the code again.
Maybe in CL they are more useful because the language is full of mutation? I can't say, I've only ever done Clojure and Emacs Lisp, but in Clojure I tried that library, and found picking options at the REPL to handle the condition was more laborious than just fixing whatever or adding a catch and pressing Ctrl+Enter again.
In ClojureRS – Clojure interpreter implemented in RustFor people who want to get a more CL-like debugging setup on Clojure, there is a CL-style condition system available as a library.
https://github.com/IGJoshua/farolero/
In Debugging in ClojureThis is interesting tool[1] that allows much the same with Clojure
[1]: https://github.com/IGJoshua/farolero
In REPL vs CLI: IDE warsShow HN: Farolero – Common Lisp style-conditions and restarts for Clojure
150 points · Open discussionFarolero – Thread-safe CL style conditions and restarts for Clojure(Script)
3 points · Open discussion