miniblog.

It seems really odd to me that git uses 'cached' terminology for staging. For example, `git add somefile.rs; git diff --cached`. Caching implies state that you don't mind losing. There's very little state I want to lose in version control!

Every time I implement an interpreter with recursion, I regret it. As soon as I want TCO, or userland control of stack limits, or resumable exceptions, I need my own stack. This is awkward because it's an upfront design decision. Changing the stack model is a big refactoring.

Most of the code I write is in a garbage collected language. I'm often surprised how much extra performance I can get when I can control allocations. I saved ~10% runtime in difftastic by moving to a zero-allocation colour library (owo_colours)!