Nanopass Framework
Ranked 9 of 10 compiler infrastructures by recommenders
Makes each compiler pass's input and output language explicit, clarifying the pipeline. Critics find it harder to debug.
Makes each compiler pass's input and output language explicit, clarifying the pipeline. Critics find it harder to debug.
7 people gave an opinion
- recommend it
- 6
- criticize it
- 1
- approval share
- 86%
Recommended in 4 of 13 months
- November 2025: recommended
- December 2025: recommended
- January 2026: not recommended
- February 2026: not recommended
- March 2026: not recommended
- April 2026: recommended
- May 2026: recommended
- June 2026: not recommended
- July 2026: not recommended
- August 2026: not recommended
- September 2026: not recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 6 people recommend itNeeds 10 or more, not met.
- 6 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 4 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Explicit input and output language per pass
“the real insight isn't the number of passes but that each pass has an explicit input and output language”
Comment from 15 Apr 2026 in “Want to Write a Compiler? Just Read These Two Papers (2008)” “taken to the extreme in the nanopass framework. That's a really useful mental model”
Comment from 12 May 2026 in “Learning Software Architecture”
What people warn about
Each mark is one comment
Harder to debug
“it probably has much less redundancy, but is probably even harder to debug”
Comment from 19 Apr 2026 in “Nanopass Framework: Clean Compiler Creation Language”
Other compiler infrastructures people recommend
The four most recommended other compiler infrastructures, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| LLVM | 119 | 96 | 55% | 12 | 6 yrs3 owners | — |
| QBE | 16 | 10 | 62% | 9 | — | — |
| EDG C++ front-end | 15 | 3 | 83% | 2 | — | — |
| Roslyn | 11 | 1 | 92% | 8 | — | Approved |
| Nanopass FrameworkThis page | 6 | 1 | 86% | 4 | — | — |
What people said
All 7 comments that mention it, newest first. Each links to the original comment.
“taken to the extreme in the nanopass framework. That's a really useful mental model”
“Building a lot of passes was great for initial development of the compilation pipeline, but was terrible for maintenance”
“The pass ordering made it really clear which analysis results are valid at each point in the compilation process.”
“it probably has much less redundancy, but is probably even harder to debug”
“the real insight isn't the number of passes but that each pass has an explicit input and output language”
“And check out Andy Keep's Nanopass Compiler work”
“Give me Chez Scheme and the nanopass compiler any day.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.