Skip to content

Commit 3f2956e

Browse files
authored
mention some alternatives (#27)
* mention some alternatives * up
1 parent 14e2856 commit 3f2956e

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

README.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,3 +42,12 @@ println("ok, done!")
4242
```
4343

4444
![](assets/[email protected])
45+
46+
## Alternatives to Asciicast.jl
47+
48+
- It is easy to use the CLI tool [asciinema](https://asciinema.org/) directly to record sessions to `.cast` files or otherwise. That can be a good option if you need keyboard input or face some of the other [Limitations of asciicast.jl](https://ericphanson.github.io/Asciicast.jl/dev/limitations/#Limitations).
49+
- In contrast, Asciicast.jl has an advantage in maintainability, in that you don't need to manually re-run sessions to regenerate the outputs.
50+
- [Replay.jl](https://github.com/AtelierArith/Replay.jl) provides a similar Julia-based alternative. Some of the differences I can ascertain:
51+
- Asciicast.jl is based on Documenter's code execution sandboxes (which [have their limitations](https://ericphanson.github.io/Asciicast.jl/dev/limitations/#Cannot-rely-on-stdout-(or-stderr)-in-one-line-being-still-open-in-the-next)), while Replay.jl has it's own implementation.
52+
- Asciicast.jl provides Documenter and pandoc-based document integration with `@cast` blocks and `{cast="true"}` blocks, while Replay seems focused on the core replaying-of-sessions. Perhaps these could be composed together somehow?
53+
- Possibly other differences; I am not very familiar with Replay.jl. PRs to improve this comparison are appreciated!

0 commit comments

Comments
 (0)