miniblog.

Caddy is really growing on me. It's nice having a web proxy that includes letsencrypt functionality without any additional configuration. I've tended to use nginx with a separate letsencrypt setup for projects before, and it's much more awkward.

Thinking more about the "auto eval definitions" approach, I think it breaks down when debugging. If I want to step through the existing definition, it'd be really awkward to re-evaluate the definition at my cursor.

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.