<story><title>Crafting Interpreters</title><url>https://craftinginterpreters.com/the-lox-language.html</url></story><parent_chain></parent_chain><comment><author>aidos</author><text>If you’re wondering if you should invest your time in this exceptional book, you could read this first in order to fully appreciate how exceptional it is.&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;journal.stuffwithstuff.com&amp;#x2F;2020&amp;#x2F;04&amp;#x2F;05&amp;#x2F;crafting-crafting-interpreters&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;journal.stuffwithstuff.com&amp;#x2F;2020&amp;#x2F;04&amp;#x2F;05&amp;#x2F;crafting-craft...&lt;/a&gt;</text></comment>
<story><title>Crafting Interpreters</title><url>https://craftinginterpreters.com/the-lox-language.html</url></story><parent_chain></parent_chain><comment><author>thundergolfer</author><text>I&amp;#x27;m working through this right now and it&amp;#x27;s awesome. I&amp;#x27;ve completed the Java interpreter and I&amp;#x27;m halfway through the C bytecode stack-based interpreter[1]. I&amp;#x27;d estimate I&amp;#x27;ve spent around 30-40 hours with the book.&lt;p&gt;Throughout I&amp;#x27;ve used both the website and the dead-tree version of the book. The website is great with 2 monitors, but you might be too tempted to copy-paste the code.&lt;p&gt;The one thing the book doesn&amp;#x27;t mandate is the use of the Lox test suite, but I think it should be incorporated into the book. It&amp;#x27;s easier to hack on your implementation when there&amp;#x27;s a test suite to validate that everything still works as it should at Chapter X.&lt;p&gt;1. &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;thundergolfer&amp;#x2F;uni&amp;#x2F;tree&amp;#x2F;main&amp;#x2F;books&amp;#x2F;crafting_interpreters&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;thundergolfer&amp;#x2F;uni&amp;#x2F;tree&amp;#x2F;main&amp;#x2F;books&amp;#x2F;craftin...&lt;/a&gt;</text></comment>