> I decided to rewrite the whole build system for the book in Dart. The build script I wrote for my first book was dead simple. Literally a single Python script that took a Markdown file for each book chapter and rendered it to HTML while weaving in the code snippets. The world’s dumbest static site generator. [...] Useful, but really straining the limits of how much code I want to maintain in a dynamically typed language like Python [...] it was, frankly, really slow
This is great to hear. When I read about your build system in Crafting "Crafting Interpreters" https://journal.stuffwithstuff.com/2020/04/05/crafting-craft...>, I had hopes that your next bugbite would be fleshing out half of a quasi-literate programming tool. For a compiler writer, who also happens to be writing a book, the circumstances and fit seem just too natural to avoid it.
I'm looking forward to diving into your Markdown package, too, and expect that it will be easy to port to JS. Nowadays, whenever I need a library for a JS project, my first choice is to check for a clean Dart, Haxe, or Java implementation that does what I want, with the intent of porting it, rather than disadvantaging myself by relying on whatever the NodeJS community has cobbled together and put on NPM. https://news.ycombinator.com/item?id=24495646>
EDIT: There is a typo "CCS" in the blog post. Highlighted: https://hyp.is/d2cCEPCLEeu7jSft-ex2Ug/journal.stuffwithstuff...>