The discussion centers on Clj.rs, a Clojure dialect implemented in Rust, with the author attributing its creation to AI-assisted 'vibe coding' due to personal constraints. Participants debate whether this LLM-generated approach yields a viable tool or merely unstable code, while also contrasting it with existing alternatives like Jank and Babashka.
70 readable replies · Supporting reply 1 · Supporting reply 2 · Supporting reply 3 · Supporting reply 4carp-lang
Carp
Haskell2016–2026
carp-lang / Carp
Carp
A statically typed lisp, without a GC, for real-time applications.
84Distinct people
105Mentions
2Explicit recommenders
6.1KGitHub stars
What to know before exploring
What it is
A statically typed lisp, without a GC, for real-time applications.
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
I love Clojure, but I do miss static types. I'm hoping Carp[0] (mentioned in the article) comes into its own. It seems like it could become my ideal language. The other problem…
christophilus used a recommendation phrase. 2 indexed comments match. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- nakkaya/ferret · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 7:02:26 AM UTC.
Mentions over time
HN mentions by year105 dated mentions
Observed mentions: 2016-03-18 06:15:17 UTC to 2026-10-07 02:57:32 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 |
|---|---|---|---|---|---|
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 11 | 4 | 7 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 6 | 3 | 3 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 7 | 2 | 5 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 13 | 1 | 12 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 8 | 1 | 7 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 17 | 3 | 14 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 13 | 1 | 12 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 12 | 3 | 9 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 9 | 1 | 8 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 5 | 0 | 5 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 4 | 0 | 4 |
What Hacker News says
11 sourcesHAhajile·Dec 5, 2016
In Measuring GC latencies in Haskell, OCaml, RacketPreScheme was a C replacement. It had manual de-allocation. Carp LISP is a new one with code being updated. MLkit supports reference-based GC, region-based management, and disabling GC for real-time use.
https://github.com/carp-lang/Carp
http://www.elsman.com/mlkit/
In Measuring GC latencies in Haskell, OCaml, RacketThere's also Carp: https://github.com/carp-lang/Carp
In Playing with SyntaxYou are right about Scheme. Note that Carp, like Clojure, treats brackets as arrays (https://github.com/eriksvedang/Carp/blob/master/src/reader.c...).
In Carp: a statically typed lisp, without a GC, for high performance applicationsInteresting.
> Carp borrows its looks from Clojure but the runtime semantics are much closer to those of ML or Rust.
> – https://github.com/eriksvedang/Carp/blob/c762e9ff07544b40c8d...
In Carp: a statically typed lisp, without a GC, for high performance applicationsIs there an explanation of the memory allocation used?
There seem to be a GC (https://github.com/eriksvedang/Carp/blob/master/src/gc.c), maybe used in the compiler only, coupled with lifetime analysis (https://github.com/eriksvedang/Carp/blob/8665a7f9a19d9347cc0...), which as far as I know is used once (https://github.com/eriksvedang/Carp/blob/6107e619d4f632acace...) in the compiler. This analysis seems tied to the manual "reset!" special form which apparently frees any existing data bound to a symbol. So, what happens when lifetime analysis cannot determine lifetime? what about stack-allocation? What should I worry about when programming in Carp w.r.t. memory?
In Carp: a statically typed lisp, without a GC, for high performance applicationsCarp: a statically typed lisp, without a GC, for high performance applications
196 points · Open discussionCarp – a statically typed Lisp, without a GC, for high performance applications
24 points · Open discussionCarp: a statically typed lisp, without a GC, for high performance applications
1 points · Open discussionI'm working on Clojure-looking lisp with a borrow checker and static analysis in the vein of Rust. It's especially tailored for games since most lisps don't account for that use case (GC, dynamic types). Here's a link, let me know if you have any questions: https://github.com/eriksvedang/Carp
In Elements of Clojure