Sounds something like charm’s vhs:
https://github.com/charmbracelet/vhs
FWIW as a non-mathematician: when I hear “Penrose” I think “Penrose Diagram”. The name association would benefit me as a sort of mnemonic: if I saw a binary called penrose on my system, I would guess it has something to do with diagrams (not necessarily Penrose diagrams). Similarly, if I forgot the name of this tool, it would be easy to recall, as there aren’t too many “____ diagram” word pairs floating around in my brain. I give libraries and executables pithy names along the same lines, where one word that isn’t already in use (“Penrose”) strongly associates with another more general word (“diagram”) in my memory.
Look at the VHS tool for example — it doesn’t have anything to do with physical VHS tapes, but it does record a scripted shell invocation as a GIF for embedding in docs and demos and such. Super easy name to remember. See https://github.com/charmbracelet/vhs
Yes! I'm slowly moving towards these steps, it's my excuse for learning go and rust. There are some CLTs that don't exist for my need and I'm working towards creating them.
I don't know if you've heard of charmbracelet [1] but they are a company that makes a lot of cool go libraries to assist creating CLTs and TUIs. One of which was on HN recently, VHS [2].
I feel like the blog post is at fault for not introducing VHS, more so than the tool itself for calling itself that.
Of course, for something as ubiquitously known as VHS it needs no introduction...except it's not actually talking about the magnetic storage format, it's a "tool" named VHS[0].
All of that aside, it seems like a poor alternative to asciinema[1]
Or a recording, could use something like https://asciinema.org/ or https://github.com/charmbracelet/vhs