HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
ruricolist
cloture
Common Lisp2019–2026
ruricolist / cloture

cloture

Clojure in Common Lisp

10Distinct people
13Mentions
0Explicit recommenders
403GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Clojure in Common Lisp

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 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 10:50:02 AM 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 year13 dated mentions

Observed mentions: 2019-11-25 17:54:59 UTC to 2026-04-19 02:15:24 UTC.

012342019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 3 mentions; 3 submissions, 0 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* 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
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC330
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC211
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC202
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC413
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

4 sources
Clojure in Common Lisp came up a couple of days ago: https://github.com/ruricolist/cloture Discussion: https://news.ycombinator.com/item?id=31655574 It should be straightforward to run it in Scheme, which extends Lisp from what I understand, although I only used Scheme in college. I'm not even entirely sure why Schema and Lisp are separate languages, although I've seen some Lisp examples that seemed a bit too low-level to be of practical use. I find that level of attention generally useless when macros and inlined functions provide leverage for free. Although I'm generally against domain-specific languages, so I would like to know if Scheme is a DSL of Lisp or if either can be implemented completely in the other via macros (or both). I'm trying to get to higher-level functional languages likes F#, Haskell and Clojure/ClojureScript. Althou
Read the rest
gh once functional languages allow impurity via mutable variables, they effectively throw the baby out with the bathwater since that forces large swaths of the codepath to fall back to being imperative. ClojureScript especially has a nice functional-imperative bridge where the code just blocks on input/output and lets the Javascript runtime run, rather than getting too lost in monads (from what I can tell, I haven't actually written any ClojureScript yet). I feel that this was the fundamental insight that's been missed in pretty much every other language, the lack of which led to the function coloring mess of async/await that we'll spend the next few decades stripping from legacy code.
In Scheje: A little Scheme implementation on top of Clojure

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.