Threedominant themes in the discussion
| Theme | Supporting quotations |
|---|---|
| 1. Classic compiler books shape personal experience | “I quite like “understanding and writing compilers” by Richard Bornat … it gives a friendly gentle overview … without excessive quantities of parsing theory.” – msla “I really enjoyed Crafting Interpreters, wholeheartedly recommend!” – vlaaad |
| 2. Hands‑on, incremental compiler projects are preferred | “The real insight isn’t the number of passes but that each pass has an explicit input and output language, which forces you to think about what invariants hold at each stage.” – blueybingo “I think there is a million ways to make a compilers course… Without this I can imagine it being a painful experience.” – kuboble |
| 3. Learning is driven more by practice than theory | “Writing a compiler is not rocket science if you know assembly language. You can pick up the gist in an hour or two by looking at a simple toy compiler.” – lateforwork “I’d never seen Knuth's middle name until your comment… I think it safely could be left out of an article.” – LiamPowell (illustrating the community’s focus on concise, applicable knowledge) |
Overall, the conversation clusters around classic textbook recommendations, a strong bias toward building small, readable compilers (often with modern parser‑combinator or nanopass tools), and the view that practical, incremental work outweighs deep theoretical study.