mu

Absolutely. And for a flaw in your OS you need an OS with automated end-to-end tests. Good luck! (Speaking as someone who's trying to imagine OSs with automated end-to-end tests: https://github.com/akkartik/mu)

Fascinating! Seems to have some commonality with dependency injection, which is one of my interests (https://github.com/akkartik/mu#readme) Can you point me at any Lua docs where I can read more about overriding IO in Lua?

Hmm, I haven't heard this idea before that the FFI or surface area of libraries in a language causes bitrot. Could you elaborate on the connection? I can take version 1 of the C sources of Vim from back in '92 and compile them without trouble. I'm not aware of dynamic languages like Javascript or Python 2 having any bitrot issues either. Backwards compatibility seems like a pretty big constraint for everyone. Edit 16 minutes later: I just tried your benchmark with my VM-like language (https://github.com/akkartik/mu), and the time taken was almost identical. Interesting exercise! Here's the Mu and Plush/0 programs side by side: $ cat fib.mu def fib n:num -> result:num [ local-scope load-ingredients base-case?:bool <- lesser-or-equal n, 1 return-if base-case?, n n <- subtract n, 1 fib-n-1:num <- fib n n <- su

For the past couple of years I’ve been researching ways to write software that make it easier for newcomers to understand rather than for insiders to maintain. (https://lobste.rs/c/rue8pf) Currently as part of that larger project, I've been improving my zoomable UI for browsing program traces: https://github.com/akkartik/mu/blob/9be4a67f42/100trace_brow.... I plan to turn this into a self-contained tool. All it requires is for logging frameworks to start each log line with a number indicating depth. When you open it on such a log file it shows just the highest-level information, allowing you to drill down into details in specific parts of the log. I think such a UI can be a strong alternative to a debugger. Instead of running the program at interaction time you first collect a trace of the program's execution. You get time-travel debuggin

For many years now I treat C++ as "C with destructors and the STL". Examples: 1. RAII: https://github.com/akkartik/mu/blob/61fb1da0b6/010vm.cc#L484 2. STL: https://github.com/akkartik/mu/blob/61fb1da0b6/020run.cc#L50 I really don't use anything else.

I somehow missed previous submissions from this blog, but I've now favorited some of them and subscribed to its feed. In particular, http://vicsydev.blogspot.com/2017/01/on-tests.html resonates very much with my approach to organizing programs: 1. https://github.com/akkartik/wart/blob/91356d9385/organizatio... 2. http://akkartik.github.io/mu/html/000organization.cc.html (https://github.com/akkartik/mu/blob/61fb1da0b6/000organizati...) The ability to 'tag' tests into multiple suites is particularly nice. I might steal that at some point, but I'm first going to think about how it might synergize with my Literate Programming approach (http://akkartik.name/post/wart-layers)