HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
day8
re-frame-10x
Clojure2018–2021
day8 / re-frame-10x

re-frame-10x

A debugging dashboard for re-frame. X-ray vision as tooling.

4Distinct people
5Mentions
0Explicit recommenders
652GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A debugging dashboard for re-frame. X-ray vision as tooling.

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 year5 dated mentions

Observed mentions: 2018-02-20 04:38:37 UTC to 2021-09-15 23:21:33 UTC.

0122018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021

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
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC211
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC202
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101

What Hacker News says

5 sources
The biggest difference is in how the state is managed. With OOP, each class is typically its own state machine with its internal behavior. With the FP approach, you can treat your state like a database, and you can easily inspect the overall state of the application. There is some nice tooling for doing these kinds of inspections in re-frame nowadays https://github.com/Day8/re-frame-10x
In When FP? And When OOP? (2013)
My team has the opposite experience. We've been using ClojureScript on the front-end for over 3 years now, and it's been fantastic. We use Leiningen with Figwheel, and it's by far the most productive workflow that I've seen in any mainstream language. You make changes and you see the results instantly. You also have an editor integrated REPL, so you can explore and try things live. You get things like code pruning and minification out of the box thanks to leveraging Google Closure compiler, and access to the Closure standard library which is quite comprehensive in itself. Meanwhile, tools like re-frame-10x https://github.com/Day8/re-frame-10x provide a great way to inspect the state of the app during development. I'm not really sure what you mean regarding the interop either. It works quite seamlessly in my experience, and it's much easie
Read the rest
r to do than it is in Elm where you have to use ports, and keep all your interop at the edges.
In Publishing an iOS App with ClojureScript and React Native

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.