Edit, run, edit, run, edit, run: During development, we run code over and over again, often with very little changes. Most of the executions are almost identical, but we still compute everything from scratch every time. Why don't we remember stuff to speed up future executions?
This talk explores what goes into designing and implementing an incrementally executed scripting language and shows what fun tooling you can build around it. If you were a CPU, wouldn't you be bored by running the same stuff over and over again, too?
Session author's bio
Laurenz is co-founder at Typst and primary designer of the Typst markup language, on which he has worked for the past four years. While trying to make Typst as intuitive and elegant as possible, he has learned a thing or two about language and compiler design.
|Level of Difficulty||Intermediate|