It's generally a good idea to judge a book by its explicitly expressed audience, where applicable. In this case Bob made his audience very clear in the first fe

It's generally a good idea to judge a book by its explicitly expressed audience, where applicable. In this case Bob made his audience very clear in the first few paragraphs of the book [0]: > It’s the book I wish I’d had when I first started getting into languages, and it’s the book I’ve been writing in my head for nearly a decade. > In these pages, we will walk step-by-step through two complete interpreters for a full-featured language. I assume this is your first foray into languages, so I’ll cover each concept and line of code you need to build a complete, usable, fast language implementation. > In order to cram two full implementations inside one book without it turning into a doorstop, this text is lighter on theory than others. It sounds to me like you picked up the wrong book, skipped the introduction, and then were disappointed that it wasn't directed at you. The good news is that it is free, so you aren't actually out anything but time. [0] http://craftinginterpreters.com/introduction.html http://craftinginterpreters.com/introduction.html