> Or are you saying the ttyrecord files are more accessible?
I do. You can edit them like if you made a typo. They are common, so there's an ecosystem of tools if you don't like raw edits.
Next to that, asciinema looks like reeinventing the wheel, except it's no longer round, so it requires special tools and roads now. But what's a few extra dependencies? It looks better and it's new!
> I have nothing on my system that can read it. I do have a web browser, though.
In general, I prefer a standard format supported by many free software tools that lets me create a file in another standard format that I can put on my website without requiring various other dependencies, like javascripts. Especially if I can pacman / apt-get install the tools.
> seq2gif makes a GIF file. How does this "support all
asciinema #1 use case is to show a recording with color, unicode, etc. I think that's a bad idea for accessibility. You want to show features, not look cool. Still seq2gif gives you that, and the output in a standard format. You can replay the original in a normal term, copy paste etc.
If you think copy & paste from the browser showing an animated replay of the terminal is an important use case #2, huh, we have different use cases, but I don't see how it couldn't be done as another target (seq2something_else, maybe seq2svg?) from a well known and accessible format like ttyrec
Normal people want things that look cool and can be made with minimal effort. Some people can afford to stay in an abstract backend world without ever presenting anything to non developer people, but I think most of us live in the real world and use modern computers so they'd rather have the cpu run a few more cycles than having to think about the details themselves.
I do. You can edit them like if you made a typo. They are common, so there's an ecosystem of tools if you don't like raw edits.
Next to that, asciinema looks like reeinventing the wheel, except it's no longer round, so it requires special tools and roads now. But what's a few extra dependencies? It looks better and it's new!
> I have nothing on my system that can read it. I do have a web browser, though.
In general, I prefer a standard format supported by many free software tools that lets me create a file in another standard format that I can put on my website without requiring various other dependencies, like javascripts. Especially if I can pacman / apt-get install the tools.
> seq2gif makes a GIF file. How does this "support all
asciinema #1 use case is to show a recording with color, unicode, etc. I think that's a bad idea for accessibility. You want to show features, not look cool. Still seq2gif gives you that, and the output in a standard format. You can replay the original in a normal term, copy paste etc.
If you think copy & paste from the browser showing an animated replay of the terminal is an important use case #2, huh, we have different use cases, but I don't see how it couldn't be done as another target (seq2something_else, maybe seq2svg?) from a well known and accessible format like ttyrec