3 ms·
I used AsciiDoc for a while at my first job because it looked better than Markdown on paper, but I hated it. The syntax made no sense to me, and AsciiDoctor (t
by thiht 4y ago
I used AsciiDoc for a while at my first job because it looked better than Markdown on paper, but I hated it. The syntax made no sense to me, and AsciiDoctor (the de facto tool to generate formatted AsciiDoc documents at the time, not sure if it has changed) was a pain in the ass to use and the output was basically impossible to configure (I just wanted to use the colors of my company).
Markdown feels a lot of less powerful, but somehow "just works". So now I just stick with Markdown everywhere and have never regretted it so far.
- nerdponx 4y agoYep, AsciiDoc implementations/tooling are a big part of why I think it has been slow to catch on. I think a standardized specification will go a long way towards addressing that. At least then implementations can target the specifications, or at least target some well-defined subset of it, and we won't be stuck with one or two monolithic legacy applications. To be clear, I don't see AsciiDoc as a Markdown replacement. But part of what I like about it is that it's simple enough to be used in most contexts where Markdown is currently used. I wrote my masters thesis with Markdown, Pandoc, and GPP, using Pandoc to generate a PDF via TeX. If I could use the same workflow but with AsciiDoc instead of Markdown, I would.