Compilers: Principles, Techniques, and Tools
Compilers: Principles, Techniques, and Tools by Aho, Sethi and Ullmanby Aho, Sethi and Ullman
The most recommended of 9 compiler textbooks
People recommend it for its end-to-end introduction to compilers and its lasting techniques; critics say it is theory-heavy, parsing-focused and a poor starting point for hobby projects.
People recommend it for its end-to-end introduction to compilers and its lasting techniques; critics say it is theory-heavy, parsing-focused and a poor starting point for hobby projects.
40 people gave an opinion
- recommend it
- 23
- criticize it
- 17
- approval share
- 58%
Recommended in 9 of 13 months
- November 2025: recommended
- December 2025: recommended
- January 2026: recommended
- February 2026: recommended
- March 2026: recommended
- April 2026: recommended
- May 2026: recommended
- June 2026: recommended
- July 2026: 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
- 23 people recommend itNeeds 10 or more, met.
- 1.3 recommenders for every criticNeeds 2 to 1 or better, not met.
- Recommended in 9 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
End-to-end introduction to compilers
“Chapter 2 is a self-sufficient introduction into compilers from end to end”
Comment from 15 Apr 2026 in “Want to Write a Compiler? Just Read These Two Papers (2008)” “I still like the end-to-end, all-in-one intro”
Comment from 26 May 2026 in “Nobody cracks open a programming book anymore” Timeless techniques still relevant
“the techniques in the Dragon Book for writing compilers are the real magic”
Comment from 17 Jul 2026 in “A Road to Lisp: Which Lisp” “Most underlying technology is timeless”
Comment from 23 Jan 2026 in “The cleaner: One woman's mission to help Britain's hoarders” Good introductory text, approachable
“It was worlds better that anything else available at the time.”
Comment from 1 Apr 2026 in “Intuiting Pratt Parsing” “I found it to be a good introductory text.”
Comment from 15 Apr 2026 in “Want to Write a Compiler? Just Read These Two Papers (2008)” “but I found it more approachable than the Dragon book.”
Comment from 26 Apr 2026 in “Want to Write a Compiler? Just Read These Two Papers (2008)” Taught how to think differently
“it taught me to think very differently”
Comment from 15 Apr 2026 in “Want to Write a Compiler? Just Read These Two Papers (2008)” “where I originally learned about this stuff”
Comment from 15 Apr 2026 in “Want to Write a Compiler? Just Read These Two Papers (2008)”
What people warn about
Each mark is one comment
Too theory-heavy and parsing-focused
“It's focused on theory and very heavy on parsing. All of that is fine, but not especially useful for the hobbies.”
Comment from 8 Feb 2026 in “Tiny C Compiler” “The Dragon Book for some reason spends all its time talking about frontend parsing, which does give you the impression it's impossible.”
Comment from 6 Feb 2026 in “We tasked Opus 4.6 using agent teams to build a C Compiler” “never really understood it, it was too much theory for me”
Comment from 11 Apr 2026 in “Ask HN: Best books on building a programming language” Techniques outdated, surpassed since
“the teachings and techniques have been surpassed since four decades or so”
Comment from 25 Nov 2025 in “Build a Compiler in Five Projects” “It's just pretty bad compared to what you can get today.”
Comment from 1 Apr 2026 in “Intuiting Pratt Parsing” Poor starting point for beginners
“but it is a terrible starting place”
Comment from 15 Apr 2026 in “Want to Write a Compiler? Just Read These Two Papers (2008)” “Whatever you do don't waste your time on the "Dragon" book.”
Comment from 16 Apr 2026 in “Want to Write a Compiler? Just Read These Two Papers (2008)” “avoid the dragon etc unless they really, really need it”
Comment from 10 May 2026 in “Making your own programming language is easier than you think (but also harder)”
Other compiler textbooks people recommend
The four most recommended other compiler textbooks, 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 |
|---|---|---|---|---|---|---|
| Compilers: Principles, Techniques, and Toolsby Aho, Sethi and UllmanThis page | 23 | 17 | 58% | 9 | — | — |
| Modern Compiler Implementationby Andrew Appel | 9 | 0 | 100% | 4 | — | — |
| Writing a C Compilerby Nora Sandler | 8 | 2 | 80% | 8 | — | — |
| Engineering a Compilerby Cooper and Torczon | 6 | 0 | 100% | 3 | — | — |
| Compiler Constructionby Niklaus Wirth | 4 | 0 | 100% | 3 | — | — |
What people said
40 of the 44 comments that mention it, newest first. Each links to the original comment.
“got a few hints from the 1988 edition when working on the TXR Lisp compiler”
“the techniques in the Dragon Book for writing compilers are the real magic”
“but it wasnt that useful tbh, too much math heavy”
“better than most similar courses based on, say, the dragon book”
“writing algorithms down with a pencil on a paper from the Dragon and the Dinasour books to make sure I understand”
“the dragon book got caught with the emperor's new register allocator”
“I still like the end-to-end, all-in-one intro”
“avoid the dragon etc unless they really, really need it”
“but I found it more approachable than the Dragon book.”
“convinced people to use the wrong tools and have the wrong mindset”
“Whatever you do don't waste your time on the "Dragon" book.”
“it taught me to think very differently”
“but it is a terrible starting place”
“It's academic and comprehensive, that's the issue.”
“if no other book is doing it for whatever reason, then the dragon book it shall be.”
“to me it sucked the joy out of the magical concept of making a compiler”
“it dives quickly into things that can clutter a project if its just for fun”
“it starts with like 350 pages on parser theory”
“I found it to be a good introductory text.”
“I wouldn't recommend it if you want to make many optimisation passes or a back-end.”
“where I originally learned about this stuff”
“Chapter 2 is a self-sufficient introduction into compilers from end to end”
“never really understood it, it was too much theory for me”
“The Dragon book wasn't good for me either but I'd disagree about using parser combinators.”
“It's just pretty bad compared to what you can get today.”
“it's problematic for a class and terrible to pick up and try to read as a stand alone”
“It was worlds better that anything else available at the time.”
“The Dragon book is not very good, to be honest.”
“More importantly, you would understand every bit of it.”
“It's focused on theory and very heavy on parsing. All of that is fine, but not especially useful for the hobbies.”
“Traditionally you would start with the Dragon Book”
“The Dragon Book for some reason spends all its time talking about frontend parsing, which does give you the impression it's impossible.”
“Most underlying technology is timeless”
“I prefer the first edition by Aho, Sethi and Ullman”
“The "modernized" version leaves out some fundamental parsing material.”
“the teachings and techniques have been surpassed since four decades or so”
“The basics of lexer and parser are still there. Some of the optimizations are also relevant.”
“the book doesn't teach you how to build a basic working compiler”
“uses translations of technical terms that make it impossible to reconcile with the rest of the literature”
“I also find the traditional Dragon Book to be somewhat helpful, but you can mostly skip the parsing/frontend sections.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.