For my lazy self it would be nice to have a gif of how it looks without having to run it on my machine.
Screen2gif is free and open source, people should use it.
Also a decent solution to this problem, it turns out.
Aside: it's a blessing and a curse how many projects don't get curated/groomed regularly for updates/upgrades. I think it should be a day or two a month to update dependencies and runtimes to current. I've now been on a handful of projects in the past year with versions of resources pinned from 3+ years ago. It's disturbing.
And how long to validate the updated dependencies don't break anything?
Most of the time, the updates don't require code changes, so it's maybe an hour, then tests, smoke tests, test/uat pass and release, like any other more significant frequent release ci/cd cycle. About twice a year, it may be deferred for a couple days, if there's a major library update with breaking changes. In those cases, new story(ies) go into the top of the backlog to handle it as a higher pointed change.
Not every environment will follow the above... which is how you see projects with multi-year old dependencies, sometimes 2+ major releases behind. IMO, it should be considered the same as ceremonies and planning, it's just part of the lifecycle. That it doesn't get treated as such is the issue.