RE: https://mastodon.social/@jarango/116047121332640221
Reminds me of "Dominik's tenth rule: Any sufficiently complicated #PIM or note-taking program contains an ad hoc, informally specified, bug-ridden, slow implementation of half of #Orgmode."
Today they're adding a CLI.
Next a REPL.
In a couple of years maybe a decent programming language.
If you want all the fun just now without the lock in effects of #Obsidian, take a look at the cool features of https://karl-voit.at/orgmode/ 😉
@publicvoit I love Org, but Obsidian is fine. I don't know about its latest features (Bases or its LLM integrations) but for keeping a notes archive, an Obsidian vault isn't locked in at all. With an Org plugin it's even able to open my main notes archive and interop with my notes just fine.
(Coming from the Org world I also don't think we get to call Markdown or Obsidian informally specified or slow. Org is no Common Lisp, unfortunately. Which is fine, but it's fine for both.)
@publicvoit That issue is with extra syntaxes that represent unique features, and that is indeed something to be wary of. But GFM is still a perfectly fine portable core syntax that many platforms (including pandoc) already fully support. In terms of lockin, Markdown is also fine.
Markdown allows in-word ita*lics* which is very necessary in languages that don't use spaces; Org has far better properties and outlining; so I use both and neither is strictly worse than the other
@kisaragi_hiu If everybody and any tool would limit itself to GFM (or any other well-defined Markdown flavor), then I'd agree.
I don't see that in practice.
Therefore, I may convert or reuse any orgdown file with any tool. This is not true for Markdown - which I need to use on a daily basis as well. It's a chaos and therefore I'd like to warn people about the subtle and not so subtle lockin effects of plain text formats: https://karl-voit.at/2025/08/17/Markdown-disaster/
Karl Voit 
如月飛羽🌈