One advantage of vi is that even though emacs is available on all those systems, vi is actually installed on all of those, setting aside windows. If you know rudimentary vi you can walk up to any of those machines and edit a configuration file well enough to work.
vi isn't even in the same neighborhood in this regard. You can and should learn vi (and ed!) in one afternoon even if you never use them. Whereas Emacs isn't something you just learn in an afternoon. (And vim is not the same as vi)
That is a separate discussion from whether you should use ed or vi normally. You learn the "fallback" with the hope of never being forced to used them.
How do you have non-IBM clones of something like this? It sounds like it would break every law ever made about copying hardware, BIOS, everything. And IBM would come after you with an army of lawyers.
Common Lisp, and even more so Racket, has reader macros. With a little help from LLMs you might be able to get a Ruby-like language that translates into Lisp.
As a last resort look at Racket's "Rhombus" language, it's basically an infix, Python-like syntax on top of Racket. You can use that or see how they pull it off and add Ruby constructs to it.
I still use a 2019 MacBook Pro, in 2026 I found the best way to warm it up was to use it daily and not blow the dust out of it for 7 years. After I opened it up and did that it's running a lot cooler.
I've barely read about Category Theory, but isn't it a just a slightly more mathy version of what programmers have been doing all along? Going up and down levels of abstraction, graphs, functions that transform one type of "object" into another?
