I’m not attacking your thing. I’m not contesting that people have written articles about emacs-less org mode in the past. But they have simply not caught on
The purpose of the article is to make it a bit more transparent for people using Markdown-based tools that they still have some lock-in effects in place - depending how they are using one of the MD variants.
You're certainly right about the low level of popularity of orgdown. However, this was not the main purpose of the article and I made it very clear that there are many LMLs out there that do not come with the downsides of MD mentioned in the article. So even when you never ever touch org-mode or orgdown, this article is highly relevant to MD users. From that perspective, it's quite irrelevant if orgdown has caught on even though there are plenty of applications outside of Emacs that are able to use that syntax: https://gitlab.com/publicvoit/orgdown/-/blob/master/doc/Tool...
There are attempts to extract it but I'm not sure any are successful. org mode is so tightly intertwined with Emacs features. For example tables can have calculations where the expressions are implemented in emacs lisp and can use emacs calc functions
org babel, which allows execution of code in blocks on the page and communication between them requires Emacs's comint (command interpreter) which would need to be ported to whatever application "displays" the text.
Folding and unfolding headlines requires the exact same display features that emacs has.
In general it seems the link is so tightly bound that it would be as well to simply embed Emacs in an application rather than extract org mode from it.
Orgdown doesn't require Emacs either: https://karl-voit.at/2017/09/23/orgmode-as-markup-only/
https://gitlab.com/publicvoit/orgdown/-/blob/master/doc/Tool...
Tadaaaa!
Furthermore: Markdown requires a magic crystal ball to tell which Markdown flavor it actually is and how to process it for machines. Read the article.
Markdown would get more things done if it wasn't tied to the waist to chaos. ;-)
I’m not attacking your thing. I’m not contesting that people have written articles about emacs-less org mode in the past. But they have simply not caught on
My thing? ;-) My things are pretty much safe because I usually do risk analysis before I'm using new tools according to https://karl-voit.at/2021/01/18/tool-choices/
The purpose of the article is to make it a bit more transparent for people using Markdown-based tools that they still have some lock-in effects in place - depending how they are using one of the MD variants.
You're certainly right about the low level of popularity of orgdown. However, this was not the main purpose of the article and I made it very clear that there are many LMLs out there that do not come with the downsides of MD mentioned in the article. So even when you never ever touch org-mode or orgdown, this article is highly relevant to MD users. From that perspective, it's quite irrelevant if orgdown has caught on even though there are plenty of applications outside of Emacs that are able to use that syntax: https://gitlab.com/publicvoit/orgdown/-/blob/master/doc/Tool...
There are attempts to extract it but I'm not sure any are successful. org mode is so tightly intertwined with Emacs features. For example tables can have calculations where the expressions are implemented in emacs lisp and can use emacs calc functions
org babel, which allows execution of code in blocks on the page and communication between them requires Emacs's comint (command interpreter) which would need to be ported to whatever application "displays" the text.
Folding and unfolding headlines requires the exact same display features that emacs has.
In general it seems the link is so tightly bound that it would be as well to simply embed Emacs in an application rather than extract org mode from it.