@davemq @jameshowell @ericsfraga @mstempl @sacha

True.

However, you've switched from a very rich syntax (#LaTeX) to a very simplistic one (lightweight markup language - #LML). There's a difference in output: https://karl-voit.at/2015/07/26/LaTeX-typography/

Don't get me wrong: I, too, prefer writing documents in #Orgmode and exporting to PDF myself. It's a very good compromise.

Meanwhile, I'd not care if the process switched from org->(pdf)latex->PDF to org-> #typst ->PDF or anything similar.

However, I'm not so sure if I'd use Org for setting a document where I really want to get the maximum, like I tried with my PhD thesis: https://karl-voit.at/tagstore/en/papers.shtml

Edit: also related: https://karl-voit.at/2017/08/26/latex-fetish/

#publicvoit

@jarango Everything true.

However, I disagree with #Markdown: https://www.karl-voit.at/2025/08/17/Markdown-disaster/

It's way more open than, let's say, #OneNote & so forth. Unfortunately, it's far from being a #textformat that can be reused anywhere without problems. At least I need to convert MD all the time from one flavor to a different.

With more and more #Obsidian add-ons introducing their own syntax elements, you will end up with clear text files you still can't convert for a different tool without modifications. Good luck with finding out which elements are going to survive and which not. For a few files, that seems OK. If you have a decent #PKM like you describe in your awesome #DulyNoted book, it requires more effort.

For everything I need to use with #MD, I keep a syntax file with one example element so that I keep an overview & know what to convert how in case I need to reuse information stored in this MD flavor.

With org, I just push it through #pandoc & I'm done. 🤷

#publicvoit #LML #Zettelkasten

Like you, I use markdown to write notes in Joplin. And to write Fedi posts such as this one. (wafrn, the Fedi software I am using, supports writing posts in markdown.)

My only suggestion: do not get seduced by markdown's ease of use. Do not try to use it indiscriminately. Do not use it for documents that require complex markup (text with lots of subscripts/superscripts, mathematical equations, chemical formulae, nested sections, tables, columns, etc.), or even for simple but very long documents (long-form writing, books).

Basically, limit its use to short documents/notes that require very little markup.

This article is a good overview of the benefits and limitations of markdown.

As an aside, I hope djot replaces markdown as the most popular lightweight markup language in the near future.

Besides not using a better #LML syntax such as #Orgdown, I really do like the way how @silverbulletmd is transparent about its #Markdown downsides.

That's why I extended my article on the downsides of Markdown with it as an example: https://karl-voit.at/2025/08/17/Markdown-disaster/

#SilverBullet #publicvoit #PIM #MD

@yojimbo @screwlisp Maybe.

In best case, this would be a discussion within the org community and not my personal decision any more.

So far, nobody expressed interest in contributing to the idea/concept but I'm more than happy if this would change and I'm out of the game in terms of a one person project.

The community could then define a new name, next steps, OD2, ...

#orgmode #emacs #orgdown #LML