It's also fascinating to see that Stroustrup's Rule (see https://www.thefeedbackloop.xyz/stroustrups-rule-and-layering-over-time/) applies to text adventure UIs too.
Whilst they have a nice natural language syntax "go west", common commands quickly get abbreviated into something shorter.
miniblog.
Related Posts
My Rust rule of thumb: if there are no lifetimes in your return type, you probably don't need to specify the lifetimes in your arguments.
(I know clippy will point out simple cases of unnecessary lifetimes, but plenty other cases occur IME.)
When I wrote my first Rust program, I got the advice "just clone everything until v1 compiles". I think this OK advice, but I think a better rule of thumb is "used owned types as much as possible".
I spent a ton of time returning &str or &[T] and fighting the borrow checker.
The "Rule Of Least Power" makes a great argument in favour of less computationally capable languages. It claims this helped HTML/CSS adoption.
https://www.w3.org/2001/tag/doc/leastPower.html
Applying this principle, I'd expect total languages to be popular. This hasn't happened AFAICT: what's missing?