ed alongside its dependencies and its supported version of the Oak interpreter. If I can bundle all of that into a single-file executable, its dependencies or interpreter won't go out of date or out of sync with the program itself, and it has a much better chance of surviving for years, maybe even decades.</p><p>Because they can be invoked simply, they <strong>fit better into workflows</strong>, especially UNIX-style workflows in the command line. Instead of typing out <code>oak my-cli.oak</code> every time