Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Agreed. When I actually started using it, I wondered why Markdown is so prevalent when AsciiDoc is a thing.


It feels like they have distinct sweet spots.

Markdown is good if you want simplicity that lets you do headings, emphasis and bold, and gets out of your way. I write fiction in Markdown.

AsciiDoc is good if you want structured documents. I would use it to write a technical manual.


They are not that different, are they? AsciiDoc looks just like an specific dialect of markdown.

Maybe a problem with AsciiDoc is that its name is scary. By the name "ascii" it seems to imply that there is a specific markup for typing non-ascii stuff, instead of simply typing the regular unicode characters (in whatever encoding).


Prevalence of Markdown is to a certain extent accidental. It is one of those many markup languages that are easy-enough to reimplement which helped with the spread and I think it was supported on Github early on.

Asciidoc is much more complex and so we only have 2 implementations around (a2x, asciidoctor).


I think it's an example of a phenomenon where there is a new-ish category of things, and that category is good, and there is one thing in that category that becomes well-known, so even though that thing is not the best in its category, it becomes wildly successful.

Git, in the category of DVCS, is another example.


Thats a very valid comparison I think.

(although I'd argue that git's success stems from not pinning down the workflow early on, like competing DVCS did).


No, problem is the covered complexity. For Markdown I have never resort to any documentation - within its original scope. This is his big advantage and I appreciate this. If you need more, you have almost certainly to look up things. This is true for AsciiDoc as well as for example ReST, the syntax of the former being a bit more appealing to me (just compare simple links for example) .

For this reason, I'm using a blogging system (Pelican) that supports all of them (including Pythons Markdown extensions). I'm completely free to apply the best suiting variant to the topics requirements.


> Maybe a problem with AsciiDoc is that its name is scary.

Exactly. For me the name "ASCII" feels like it is for older UNIX-era system experts.

The name might use to be fancy considering its initial version came out in 2002 (before markdown), but it became an unfortunate name.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: