Because it's so integrated with Emacs, and all other editors are second class citizens (/hosts)?
Because it's so integrated with Emacs, and all other editors are second class citizens (/hosts)?
My org files quickly accumulate custom elisp snippets for automating small one-off things like rendering embedded dot with Graphviz and displaying them inline. I don't think I'm alone in that. Unfortunately, that creates a situation where, whenever I try to work with org files in other editors, there's a certain "it's like opening Photoshop files in MS Paint" aspect to the experience. Too many things that I've come to take for granted about how I'd interact with and edit these files no longer works.
Markdown, on the other hand, is just a markup format. It has lots of dialects, but it isn't really owned by anyone. That creates a very different power structure: Markdown editors are free to just try to make a good Markdown editing/viewing experience, whatever that means to that particular editor's developer. There's no looming and inevitably unfavorable comparison to the format's native editor to have to contend with.
I suspect that I can write embedable applications in JS and load them as libraries in Markdown to perform advanced stunts, like in Org mode.
But jokes aside, is there something that doesn't let us implement a language server for org mode?
%%(org-anniversary 2021 11 18) It's been %d years since the 50,000th org-mode thread on HN.
Or with org-babel you can have different blocks of code interact with and reference each other:https://orgmode.org/manual/Environment-of-a-Code-Block.html
That's a lot more than markup at this point since you can run those inside of org-mode.
/s
It doesn't. There have been failed efforts in standardizing the grammar. If they can't even do that, it's clear that being standalone is not a goal.