It's impressive (& was not obvious to me) how much memory a bytecode interpreter can save!
miniblog.
Related Posts
I'm intrigued to see that Google has quantified that new code is generally buggier and less secure than code that has existed in your codebase for longer:
I've been learning how to use Massif, a tool in valgrind for memory profiling. It quickly paid off!
I discovered that difftastic sometimes attempts to preallocate absurd amounts of memory.
Is Forth really a memory-unsafe language? I'm struggling to picture what e.g. a use-after-free would look like in such a minimal programming language.

