HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
vnmakarov
mir
C2020–2026
vnmakarov / mir

mir

A lightweight JIT compiler based on MIR (Medium Internal Representation) and C11 JIT compiler and interpreter based on MIR

22Distinct people
22Mentions
0Explicit recommenders
2.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A lightweight JIT compiler based on MIR (Medium Internal Representation) and C11 JIT compiler and interpreter based on MIR

GitHub

Where it is used

No documented product use was verified in the last source check.

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

Observed mentions: 2020-01-20 14:37:31 UTC to 2026-04-28 21:52:08 UTC.

0123452020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 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
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC514
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC514
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC413
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC413
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC211
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

22 sources
Wirth’s Law still hits hard in 2025. It's like the ghost of your first CS prof whispering "I told you so" every time an app eats 500MB to display a list of items. We were supposed to use better tools to build better systems. Instead, we used faster hardware to make it acceptable to ship ever-more bloated layers of abstraction. Everything depends on everything else, and no one knows what any of it does, just that it “works on my machine.” Until it doesn't. It’s not just about performance — it’s about comprehensibility. You used to be able to hold a system in your head. Now? Good luck tracing anything across 8 layers of indirection, six config files, a microservice mesh and a runtime whose lifecycle even the maintainers don’t fully understand. I find myself drawn to projects like Red[1], MIR[2], or even Metamath[3] — not because they’re pro
Read the rest
duction-ready silver bullets, but because they remind me what it’s like to work on systems that are conceptually finite. With MIR, you get a JIT compiler backend that’s tiny and knowable — and that still punches way above its weight. There’s elegance in understanding where every byte and cycle goes. The rebound effect of Moore’s Law is real: more resources led to more indirection, which led to more tools, which led to more churn. And now we’re entering the AI era, where tools can generate “working” code faster than we can understand what it’s really doing. And sure, it feels productive — but something subtle gets lost when we stop thinking through the system as a whole. We’ve outsourced understanding to the machine. Now we just hope it’s right. [1] https://www.red-lang.org/ [2] https://github.com/vnmakarov/mir [3] https://us.metamath.org/
In Wirth's Law
I came here to say exactly the same thing. There are also a couple of other options: the MIR project from RedHat [1], libjit [2], lightning [3] and Dynasm [4] 1. https://github.com/vnmakarov/mir 2. https://www.gnu.org/software/libjit/ 3. https://www.gnu.org/software/lightning/manual/lightning.html 4. https://corsix.github.io/dynasm-doc/tutorial.html But in general it seems to be very hard to beat the bang for buck from generating C and compiling that - even with something simple like tcc
In Implementing Interactive Languages

Showing the 15 most recent of 22 sources. Enable JavaScript to search and browse every indexed mention.

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.