{"slug": "asciidoc", "name": "AsciiDoc", "category": "notes", "category_name": "Notes and knowledge", "description": "", "recommenders": 3, "commenters": 4, "warners": 2, "score": 0.111, "rising": 0.35, "first": "2025-11-22", "latest": "2026-08-23", "why": "", "why_is_quote": false, "has_verdict": false, "sentiment": {"recommend": 3, "neutral": 0, "compare": 0, "warn": 1}, "spark": [0, 0, 0, 0, 0, 1, 0, 1, 0, 1, 0, 0], "listed": true, "loved": [], "caveat": "", "short_quote": "", "icon": true, "domain": null, "github_repo": null, "official_url": "https://asciidoc.org", "pricing": "", "aliases": ["AsciiDoc", "Asciidoc"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 790541489, "item_id": 49408843, "url": "https://news.ycombinator.com/item?id=49408843", "by": "geokon", "date": "2026-08-23", "stance": "recommend", "quote": "I moved to asciidoc", "excerpt": "Orgmode also does this on HTML export. Makes it impossible to get good diffs Granted they started doing this several years ago and as a result I moved to asciidoc, so it might have made a fix by now..", "context": "", "use_case": "documents", "switched_from": "Org mode", "story": "What's in a PowerPoint File?"}, {"id": 776087888, "item_id": 48505493, "url": "https://news.ycombinator.com/item?id=48505493", "by": "Rochus", "date": "2026-06-12", "stance": "recommend", "quote": "Why not Asciidoc? It works well with AI so far.", "excerpt": "Why not Asciidoc? It works well with AI so far. To make it even work better I made a more formal subset which can be read with a single-pass parser (https://github.com/rochus-keller/leandoc/), to reduce the \"level of surprise\" for all parties. Why should an xml-kind format be better suited for AI?", "context": "", "use_case": "documentation format for AI", "switched_from": "", "story": "Doclang-Project/Doclang"}, {"id": 762085728, "item_id": 47630358, "url": "https://news.ycombinator.com/item?id=47630358", "by": "lopsotronic", "date": "2026-04-03", "stance": "recommend", "quote": "Asciidoc forever baby. Write actual books in it.", "excerpt": "The \"right element for the right meaning\" crowd is always going to fall when they charge against the sheer walls of \"but I like using Caution for my bulleted list\" crowd. Or the \"of course we put tire patches in the wiring element, it's when we use the tire patches\". Or a million other examples I've wrassled with over the literal decades. Whatever sophisticated semantic scheme you move into the markup layer, is gonna", "context": "", "use_case": "writing books", "switched_from": "", "story": "Why the heck are we still using Markdown?"}]}], "caveats": [{"label": "", "summary": "", "quotes": [{"id": 776771617, "item_id": 48548226, "url": "https://news.ycombinator.com/item?id=48548226", "by": "Rochus", "date": "2026-06-15", "stance": "warn", "quote": "But Asciidoc has unneccessary complexity and ambiguity, and the results are often surprising.", "excerpt": "Typst is great. I think they'll catch up to LuaTeX in terms of typographic quality in near future. But Typst is for typesetting; it's essentially a programming language for layout. If you compare it to e.g. Asciidoc, the latter is for content and semantics. We need both. But Asciidoc has unneccessary complexity and ambiguity, and the results are often surprising. So I made an unambiguous, deterministic subset of Asci", "context": "", "use_case": "content markup", "switched_from": "", "story": "Typst 0.15.0"}]}], "who": [], "tags": [], "use_cases": ["documents", "content markup", "documentation format for ai", "writing books", "making pdfs"], "compared": [{"slug": "typst", "name": "Typst", "co": 2, "switched_from": 0, "switched_to": 1}, {"slug": "org-mode", "name": "Org mode", "co": 1, "switched_from": 1, "switched_to": 0}], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=49360643", "title": "What's in a PowerPoint File?", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=48544396", "title": "Typst 0.15.0", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=48500595", "title": "Doclang-Project/Doclang", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47629903", "title": "Why the heck are we still using Markdown?", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=46017782", "title": "Markdown is holding you back", "mentions": 1}], "sentiment_by_month": {"2025-11": {"warn": 1}, "2025-12": {}, "2026-01": {}, "2026-02": {}, "2026-03": {}, "2026-04": {"recommend": 1}, "2026-05": {}, "2026-06": {"recommend": 1}, "2026-07": {}, "2026-08": {"recommend": 1}, "2026-09": {}, "2026-10": {}}, "quotes": [{"id": 790541489, "item_id": 49408843, "url": "https://news.ycombinator.com/item?id=49408843", "by": "geokon", "date": "2026-08-23", "stance": "recommend", "quote": "I moved to asciidoc", "excerpt": "Orgmode also does this on HTML export. Makes it impossible to get good diffs Granted they started doing this several years ago and as a result I moved to asciidoc, so it might have made a fix by now..", "context": "", "use_case": "documents", "switched_from": "Org mode", "story": "What's in a PowerPoint File?"}, {"id": 776771617, "item_id": 48548226, "url": "https://news.ycombinator.com/item?id=48548226", "by": "Rochus", "date": "2026-06-15", "stance": "warn", "quote": "But Asciidoc has unneccessary complexity and ambiguity, and the results are often surprising.", "excerpt": "Typst is great. I think they'll catch up to LuaTeX in terms of typographic quality in near future. But Typst is for typesetting; it's essentially a programming language for layout. If you compare it to e.g. Asciidoc, the latter is for content and semantics. We need both. But Asciidoc has unneccessary complexity and ambiguity, and the results are often surprising. So I made an unambiguous, deterministic subset of Asci", "context": "", "use_case": "content markup", "switched_from": "", "story": "Typst 0.15.0"}, {"id": 776087888, "item_id": 48505493, "url": "https://news.ycombinator.com/item?id=48505493", "by": "Rochus", "date": "2026-06-12", "stance": "recommend", "quote": "Why not Asciidoc? It works well with AI so far.", "excerpt": "Why not Asciidoc? It works well with AI so far. To make it even work better I made a more formal subset which can be read with a single-pass parser (https://github.com/rochus-keller/leandoc/), to reduce the \"level of surprise\" for all parties. Why should an xml-kind format be better suited for AI?", "context": "", "use_case": "documentation format for AI", "switched_from": "", "story": "Doclang-Project/Doclang"}, {"id": 762085728, "item_id": 47630358, "url": "https://news.ycombinator.com/item?id=47630358", "by": "lopsotronic", "date": "2026-04-03", "stance": "recommend", "quote": "Asciidoc forever baby. Write actual books in it.", "excerpt": "The \"right element for the right meaning\" crowd is always going to fall when they charge against the sheer walls of \"but I like using Caution for my bulleted list\" crowd. Or the \"of course we put tire patches in the wiring element, it's when we use the tire patches\". Or a million other examples I've wrassled with over the literal decades. Whatever sophisticated semantic scheme you move into the markup layer, is gonna", "context": "", "use_case": "writing books", "switched_from": "", "story": "Why the heck are we still using Markdown?"}, {"id": 736299521, "item_id": 46018720, "url": "https://news.ycombinator.com/item?id=46018720", "by": "jimmar", "date": "2025-11-22", "stance": "warn", "quote": "", "excerpt": "Markdown is the minimum viable product. It\u2019s easy to learn and still readable if not rendered in an alternate format. It\u2019s great. For making PDFs, I\u2019ve recently moved from AsciiDoc to Typst. I couldn\u2019t find a good way to get AsciiDoc to make accessible PDFs, and I found myself struggling to control the output. Typst solves all of AsciiDoc\u2019s problems for me. But in the end, no markup language will make you write bette", "context": "", "use_case": "making PDFs", "switched_from": "", "story": "Markdown is holding you back"}]}