sure, if you're going to be lazy and only do one do text. HOWEVER advocating for the lazy path amongst fellow practitioners is not a great strategy to promote quality output.

Documentation is hard. Good documentation is harder. There are many occasions where video and video-like things are good for getting a feel for something and just plain text is good for reference. We shouldn't be saying "just use text because you probably won't bother doing everything you should". We should be saying "Hey, video, still images, and text all combine to make great documentation and help people to understand and use your tool / product." They take time, but we should care about our users, and thus we should take the time to support them.

Not sure it's double the effort. Once you've written the textual version, you pretty much only need to copy and paste it into a terminal to produce the asciicast version.

That's how I did the animations for this Powershell tool.

https://github.com/nickcox/cd-extras