Re:Why I Prefer RST to Markdown
by YakBizzarro on Wednesday July 31, 2024 @02:55PM
(#41122230)
Oh yes, I could mot agree more. We moved from Antora/asciidoc to mkdocs/markdown. Overall the situation improved (better HTML, faster builds, syntax highlighting of code,...) but I miss how good writing in asciidoc was
Re:Why I Prefer RST to Markdown
by FartinMowler on Wednesday July 31, 2024 @02:41PM
(#41122047)
I run asciidoctor's Docker container. It does what I want it to do without leaving a mess behind on my laptop.
The trouble with that is it becomes a pain in CI. Nested Docker isn't fun.
the toc macro on asciidoc is sublime
:table-caption!: :toc: macro :sectlinks:
toc::[]
Yeah a nice Rust or Go-based implementation of Asciidoc would be fantastic. Having to deal with Ruby and Gems is not fun.
That's a mountain of work though and even if there is a spec, at this point it's complex enough and the Ruby implementation is enough of a de facto spec that I'm doubtful you'll ever make it past "this behaves differently to Asciidoctor" territory.
Btw a more recent alternative is https://github.com/jgm/djot which actually does have multiple implementations and looks like a way better option than Markdown, but maybe not as powerful as Asciidoctor still. I haven't tried it.
There's a spec being drafted, so hopefully that will spur some more action.
For my purposes, Asciidoc is the best markup with the worst tooling, and Markdown is the worst markup with the best tooling.