How is it possible, that I've worked as a Linux sysadmin, backend engineer, security developer, and technical writer (regularly sharing CLI snippets in articles), and regularly document my CLI work on my blog, and I'm just learning about this.
script seems to require you to type the demo commands perfectly and at the right pace for the demo. That openssl command, for example. Contrast with this tool, where you can get the command right at your leisure then apply magic to look like it's being typed in interactively. The two steps (running commands, interactive typing with desired timing) are much easier to get right separately than together.
Same, I’ve been working on a command line tool and set up VCR to record demos (https://github.com/zachallaun/mneme/blob/main/examples/demo....). I’d be very interested if anyone could speak to the fundamental differences between VCR and the tools referenced in the OP.
For live demos "its a live" [0] by @stavros is also great.
From the Readme:
It's a Live lets you write commands and keystrokes in a file, which it will then read and open a new terminal for you.
Every time you press a key, It's a Live will write one character from the file into the terminal, making it look like
you're typing every single command with the practiced ease of a consummate professional.
This looks nice, but if there is a script anyway isn't making an animated GIF of it a relatively poor use of capabilities? Why not have a result that is able to go backward and forward (like a slideshow), the ability to pause/resume, or to copy/paste text from it.
He actually mentions the tool [0] that has all of this, in the end. It records your screen and compiles a demo that runs in any browser by the looks of it.
