Live data from Hacker News

Crafting Interpreters is available in print

craftinginterpreters.com

111–120 of 120 posts

Re: Crafting Interpreters is available in print

#111

Author here! It feels amazing to have this done and live. I'm happy to talk about whatever you might want to know about it. If you're curious how the sausage was made, I wrote a blog post about taking the web book and bringing it to print and ebook here: http://journal.stuffwithstuff.com/2021/07/29/640-pages-in-15...

Congratulations on releasing the book! Grateful for your work both as a student of computer science and as a Flutter/Dart developer. I’m planning on buying a copy after work. Are there any resources you recommend as a follow up to this book, and do you have any new content planned?

The last chapter suggests a few places to go next after reading the book:

http://craftinginterpreters.com/optimization.html#where-to-n...

I have absolutely nothing planned after this. I plan to not have any plans for a while. :)

Re: Crafting Interpreters is available in print

#112
post #82

Earlier quoted context omitted.

Thanks for writing about your process! I enjoyed it almost as much as Crafting Interpreters, which is to say, quite a lot. And you absolutely should be proud of your PDF->PNG->Highlight diffs script. As someone who has kept excel files and PDFs in version control I knew exactly the feeling you were talking about. I got to that part and exclaimed out loud, "Damn cool!"

> As someone who has kept excel files and PDFs in version control Hot tip for handling office file formats or anything that uses a ZIP container: just unzip them and commit that to the repo. It won't fix the issue mentioned of the authoring tool making seemingly arbitrary and unnecessary changes, nor will it give you nifty visual diffs, but it's better than shuffling binary blobs through your version control tools.

AFAIK that won't save space in git, in fact it will probably use more due to the lack of compression and the fact that git commits aren't diffs, they're just commonly displayed as if they are.

Re: Crafting Interpreters is available in print

#113

Author here! It feels amazing to have this done and live. I'm happy to talk about whatever you might want to know about it. If you're curious how the sausage was made, I wrote a blog post about taking the web book and bringing it to print and ebook here: http://journal.stuffwithstuff.com/2021/07/29/640-pages-in-15...

hey! I’d been thinking about this just a few days ago! It’s great that the print version is finally out. Congratulations on publishing your book!

Re: Crafting Interpreters is available in print

#114
post #96

Author here! It feels amazing to have this done and live. I'm happy to talk about whatever you might want to know about it. If you're curious how the sausage was made, I wrote a blog post about taking the web book and bringing it to print and ebook here: http://journal.stuffwithstuff.com/2021/07/29/640-pages-in-15...

Can you please point out the differences compared to other books for the same topic? Thanks!

It’s written by Bob and the others aren’t. That’s a good enough reason for me.

Re: Crafting Interpreters is available in print

#115
post #21

I just finished the first part of the book (building the intepreter, but I did it in typed Python). The book sent me back to the college days where I remember doing similar things. Can't wait to start working on the bytecode virtual machine. It's really an excellent book.

How difficult was it to make this in a different language than the one used on the book?

I've been using C++20 and I haven't run into any Java I couldn't translate yet.

Re: Crafting Interpreters is available in print

#116
post #109

Earlier quoted context omitted.

Thank you so much for all your work on this! I ran through the first part (interpreter in Java, which I ended up doing in Scala for fun) a few years ago, and so much about this sort of thing was demystified for me. I used to think building parsers, tokenizers, AST builders, and interpreters was some sort of unapproachable black magic, but now I realize it's not actually that difficult. I started working on the second…

You might find this blog post interesting: https://ceronman.com/2021/07/22/my-experience-crafting-an-in...

Oh, excellent, thanks for the link! I still want to do this myself, but am now pretty wary of building a GC in Rust...

Re: Crafting Interpreters is available in print

#117

Author here! It feels amazing to have this done and live. I'm happy to talk about whatever you might want to know about it. If you're curious how the sausage was made, I wrote a blog post about taking the web book and bringing it to print and ebook here: http://journal.stuffwithstuff.com/2021/07/29/640-pages-in-15...

Just a note to say that your writing is excellent!

After seeing this HN post yesterday, I bought your /Crafting Interpreters/ book to see if it could help me evolve my AST-walker into a threaded-interpreter (using GNU's computed goto-label extension.) I find your writing style to be just the right mix of humor and content to keep me engaged.

Re: Crafting Interpreters is available in print

#119

Author here! It feels amazing to have this done and live. I'm happy to talk about whatever you might want to know about it. If you're curious how the sausage was made, I wrote a blog post about taking the web book and bringing it to print and ebook here: http://journal.stuffwithstuff.com/2021/07/29/640-pages-in-15...

#1 Bestseller! -> https://imgur.com/3GJkMvd

Re: Crafting Interpreters is available in print

#120
post #112
post #82

Earlier quoted context omitted.

> As someone who has kept excel files and PDFs in version control Hot tip for handling office file formats or anything that uses a ZIP container: just unzip them and commit that to the repo. It won't fix the issue mentioned of the authoring tool making seemingly arbitrary and unnecessary changes, nor will it give you nifty visual diffs, but it's better than shuffling binary blobs through your version control tools.

AFAIK that won't save space in git, in fact it will probably use more due to the lack of compression and the fact that git commits aren't diffs, they're just commonly displayed as if they are.

> AFAIK that won't save space in git

Actually, it should (precisely _because_ of Git's approach to storing blobs) but that's besides the point. Saving space had nothing to do with the motivation for the earlier comment.

> in fact it will probably use more

No.

Post reply on HN