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

What other glaring issues can you think of up the top of your head that you caution against using asciidoc? The one GitHub issue linked seems like quite a nitpick.

Been using it for years, and I haven’t run into any issue thy would make me want to use anything else.



I'm not sure I would caution against AsciiDoc, but I stopped using it personally due to lack of support, and Markdown (of various flavors) being good enough for the use cases I cared about at the time.

There isn't much tooling. The community is small. The spec effort seems to have stagnated. AsciiDoctor and related projects seem to move at the speed of what Dan Allen decides is most worth his time.

That said, I've been wanting to do more long form writing, and AsciiDoc is lovely for that, so I may pick it up again for that.


The format itself has several warts, like the ancestor list continuation syntax, or whether or not to add a backslash if you want a literal asterisk.

The implementation lacks checking, so for example if you have some text between square brackets, it will often just get dropped even if the contents is not valid as an attribute list.


AsciiDoctor now has an unambiguous way to insert an asterisk. The original Python implementation does not.


I was on my phone when I posted the above, so couldn't easily look up the exact way it's:

  {asterisk}




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

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

Search: