3 ms·

Why do you think asciidoc is better than Markdown? Serious question as quick skim over the homepage (https://asciidoctor.org/ https://asciidoctor.org/) and it l

• jhoechtl 7y ago
  https://news.ycombinator.com/item?id=18848278 https://news.ycombinator.com/item?id=18848278 https://www.ericholscher.com/blog/2016/mar/15/dont-use-markdown-for-technical-docs/ https://www.ericholscher.com/blog/2016/mar/15/dont-use-markd... https://dev.to/practicalprogramming/we-need-a-new-document-markup-language---here-is-why-5d4c https://dev.to/practicalprogramming/we-need-a-new-document-m... https://mister-gold.pro/posts/en/asciidoc-vs-markdown/ https://mister-gold.pro/posts/en/asciidoc-vs-markdown/
  • Whatitat90 7y ago
    That's what I was looking for, thanks!
• cmroanirgo 7y ago
  One of the main failings of markdown (for me) is it's lack of expressiveness, always forcing us to revert to html to get certain things done. Markdown's great for simple readme, or if you don't need to (say) right align an image, of apply a class to a paragraph (eg. To turn it into an inset). While I personally prefer textile (which is a deader dodo than asciidoc), they are both able to do significantly more than markdown. I look at the problem as: if markdown forces me to write html, then I may as well use html... (Ps: in textile "> hello world" at the start of a line sets right alignment, "=" for justified, "p.inset#my_id hello world" applies an "inset" class to the para and gives it the id "my_id". Asciidoc is similar, but I'm not familiar enough with it to write it on my phone just now)