#lml — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #lml, aggregated by home.social.
-
@yantar92 @screwlisp I know.
However, I think you've got the Org point of view perspective and I want to promote Orgdown to people who will never hear of Emacs or are even opposing the use of Emacs. Totally different turf and hosting information at org or worg doesn't help here.
That's totally different perspective and the way non Org people stumble over information.
After all, the #Emacs community never differentiated the tool #Orgmode from the much more general lightweight #markup language #Orgdown. The focus of #OD is the latter and I want to promote that by mostly neglecting any connection to Emacs, Elisp and the communities involved. Not directing people to the mixup of information on Orgmode.org was a very deliberate decision of mine.
https://karl-voit.at/2021/11/27/orgdown/
I know that some org community people disagree with my approach for various reasons. Some of the arguments do have real substance, most rather not.
YMMV
-
@yantar92 @screwlisp I know.
However, I think you've got the Org point of view perspective and I want to promote Orgdown to people who will never hear of Emacs or are even opposing the use of Emacs. Totally different turf and hosting information at org or worg doesn't help here.
That's totally different perspective and the way non Org people stumble over information.
After all, the #Emacs community never differentiated the tool #Orgmode from the much more general lightweight #markup language #Orgdown. The focus of #OD is the latter and I want to promote that by mostly neglecting any connection to Emacs, Elisp and the communities involved. Not directing people to the mixup of information on Orgmode.org was a very deliberate decision of mine.
https://karl-voit.at/2021/11/27/orgdown/
I know that some org community people disagree with my approach for various reasons. Some of the arguments do have real substance, most rather not.
YMMV
-
@yantar92 @screwlisp I know.
However, I think you've got the Org point of view perspective and I want to promote Orgdown to people who will never hear of Emacs or are even opposing the use of Emacs. Totally different turf and hosting information at org or worg doesn't help here.
That's totally different perspective and the way non Org people stumble over information.
After all, the #Emacs community never differentiated the tool #Orgmode from the much more general lightweight #markup language #Orgdown. The focus of #OD is the latter and I want to promote that by mostly neglecting any connection to Emacs, Elisp and the communities involved. Not directing people to the mixup of information on Orgmode.org was a very deliberate decision of mine.
https://karl-voit.at/2021/11/27/orgdown/
I know that some org community people disagree with my approach for various reasons. Some of the arguments do have real substance, most rather not.
YMMV
-
@yantar92 @screwlisp I know.
However, I think you've got the Org point of view perspective and I want to promote Orgdown to people who will never hear of Emacs or are even opposing the use of Emacs. Totally different turf and hosting information at org or worg doesn't help here.
That's totally different perspective and the way non Org people stumble over information.
After all, the #Emacs community never differentiated the tool #Orgmode from the much more general lightweight #markup language #Orgdown. The focus of #OD is the latter and I want to promote that by mostly neglecting any connection to Emacs, Elisp and the communities involved. Not directing people to the mixup of information on Orgmode.org was a very deliberate decision of mine.
https://karl-voit.at/2021/11/27/orgdown/
I know that some org community people disagree with my approach for various reasons. Some of the arguments do have real substance, most rather not.
YMMV
-
@yantar92 @screwlisp I know.
However, I think you've got the Org point of view perspective and I want to promote Orgdown to people who will never hear of Emacs or are even opposing the use of Emacs. Totally different turf and hosting information at org or worg doesn't help here.
That's totally different perspective and the way non Org people stumble over information.
After all, the #Emacs community never differentiated the tool #Orgmode from the much more general lightweight #markup language #Orgdown. The focus of #OD is the latter and I want to promote that by mostly neglecting any connection to Emacs, Elisp and the communities involved. Not directing people to the mixup of information on Orgmode.org was a very deliberate decision of mine.
https://karl-voit.at/2021/11/27/orgdown/
I know that some org community people disagree with my approach for various reasons. Some of the arguments do have real substance, most rather not.
YMMV
-
@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/
-
@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/
-
@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/
-
@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/
-
@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/
-
@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. 🤷
-
@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. 🤷
-
@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. 🤷
-
@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. 🤷
-
@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. 🤷
-
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.
#LML #djot #markdown #joplin #joplinapp #writing -
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.
#LML #djot #markdown #joplin #joplinapp #writing -
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.
#LML #djot #markdown #joplin #joplinapp #writing -
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.
#LML #djot #markdown #joplin #joplinapp #writing -
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.
#LML #djot #markdown #joplin #joplinapp #writing -
My article about "#Markdown Is a Disaster: Why and What to Do Instead" from https://karl-voit.at/2025/08/17/Markdown-disaster/ was listed on the entry page of #HackerNews yesterday.
It hurts me to read through the comments. One part of the people who commented obviously didn't read the article they're commenting on.
And another part of the commenters does mix up #Orgmode, the Elisp implementation within #Emacs, with orgdown, the lightweight syntax which is actually the topic of this article. This part of the discussion is totally missing the whole point of my article: practical issues related to Markdown; choosing any other #LML which doesn't come with those downsides. #Orgdown was just one example of many which I wanted to mention because it is one of the least known alternatives outside the Emacs bubble.
🤷
-
My article about "#Markdown Is a Disaster: Why and What to Do Instead" from https://karl-voit.at/2025/08/17/Markdown-disaster/ was listed on the entry page of #HackerNews yesterday.
It hurts me to read through the comments. One part of the people who commented obviously didn't read the article they're commenting on.
And another part of the commenters does mix up #Orgmode, the Elisp implementation within #Emacs, with orgdown, the lightweight syntax which is actually the topic of this article. This part of the discussion is totally missing the whole point of my article: practical issues related to Markdown; choosing any other #LML which doesn't come with those downsides. #Orgdown was just one example of many which I wanted to mention because it is one of the least known alternatives outside the Emacs bubble.
🤷
-
My article about "#Markdown Is a Disaster: Why and What to Do Instead" from https://karl-voit.at/2025/08/17/Markdown-disaster/ was listed on the entry page of #HackerNews yesterday.
It hurts me to read through the comments. One part of the people who commented obviously didn't read the article they're commenting on.
And another part of the commenters does mix up #Orgmode, the Elisp implementation within #Emacs, with orgdown, the lightweight syntax which is actually the topic of this article. This part of the discussion is totally missing the whole point of my article: practical issues related to Markdown; choosing any other #LML which doesn't come with those downsides. #Orgdown was just one example of many which I wanted to mention because it is one of the least known alternatives outside the Emacs bubble.
🤷
-
My article about "#Markdown Is a Disaster: Why and What to Do Instead" from https://karl-voit.at/2025/08/17/Markdown-disaster/ was listed on the entry page of #HackerNews yesterday.
It hurts me to read through the comments. One part of the people who commented obviously didn't read the article they're commenting on.
And another part of the commenters does mix up #Orgmode, the Elisp implementation within #Emacs, with orgdown, the lightweight syntax which is actually the topic of this article. This part of the discussion is totally missing the whole point of my article: practical issues related to Markdown; choosing any other #LML which doesn't come with those downsides. #Orgdown was just one example of many which I wanted to mention because it is one of the least known alternatives outside the Emacs bubble.
🤷
-
My article about "#Markdown Is a Disaster: Why and What to Do Instead" from https://karl-voit.at/2025/08/17/Markdown-disaster/ was listed on the entry page of #HackerNews yesterday.
It hurts me to read through the comments. One part of the people who commented obviously didn't read the article they're commenting on.
And another part of the commenters does mix up #Orgmode, the Elisp implementation within #Emacs, with orgdown, the lightweight syntax which is actually the topic of this article. This part of the discussion is totally missing the whole point of my article: practical issues related to Markdown; choosing any other #LML which doesn't come with those downsides. #Orgdown was just one example of many which I wanted to mention because it is one of the least known alternatives outside the Emacs bubble.
🤷
-
https://www.europesays.com/fi/118700/ Piispanvirka on P. Hengen lahja kirkolle #Business #Economy #FI #Finland #Finnish #ILC #JuhanaPohjola #lähetyshiippakunta #LML #luther #LutheranTheologicalReview #piispanvirka #piispuus #Suomi #Talous #tunnustukirjat
-
@ericsfraga @oantolin Yes, the direct and initial benefits of #Orgdown are mostly for non-Emacs people: https://karl-voit.at/2021/11/27/orgdown/
However, just imagine for a minute, that all #Markdown usage is replaced with Orgdown usage. Let your thoughts wander for a moment.
This would have tremendous impact on the #Emacs people as well when it comes to working with external tools and people.
#PIM #LML #indirectprofitability #markup #publicvoit #orgmode
-
@ericsfraga @oantolin Yes, the direct and initial benefits of #Orgdown are mostly for non-Emacs people: https://karl-voit.at/2021/11/27/orgdown/
However, just imagine for a minute, that all #Markdown usage is replaced with Orgdown usage. Let your thoughts wander for a moment.
This would have tremendous impact on the #Emacs people as well when it comes to working with external tools and people.
#PIM #LML #indirectprofitability #markup #publicvoit #orgmode
-
@ericsfraga @oantolin Yes, the direct and initial benefits of #Orgdown are mostly for non-Emacs people: https://karl-voit.at/2021/11/27/orgdown/
However, just imagine for a minute, that all #Markdown usage is replaced with Orgdown usage. Let your thoughts wander for a moment.
This would have tremendous impact on the #Emacs people as well when it comes to working with external tools and people.
#PIM #LML #indirectprofitability #markup #publicvoit #orgmode
-
@ericsfraga @oantolin Yes, the direct and initial benefits of #Orgdown are mostly for non-Emacs people: https://karl-voit.at/2021/11/27/orgdown/
However, just imagine for a minute, that all #Markdown usage is replaced with Orgdown usage. Let your thoughts wander for a moment.
This would have tremendous impact on the #Emacs people as well when it comes to working with external tools and people.
#PIM #LML #indirectprofitability #markup #publicvoit #orgmode
-
@ericsfraga @oantolin Yes, the direct and initial benefits of #Orgdown are mostly for non-Emacs people: https://karl-voit.at/2021/11/27/orgdown/
However, just imagine for a minute, that all #Markdown usage is replaced with Orgdown usage. Let your thoughts wander for a moment.
This would have tremendous impact on the #Emacs people as well when it comes to working with external tools and people.
#PIM #LML #indirectprofitability #markup #publicvoit #orgmode
-
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/
-
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/
-
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/
-
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/
-
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/
-
@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, ...
-
@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, ...
-
@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, ...
-
@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, ...
-
@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, ...
-
In a couple of hours (8am UTC, 10am CET), I'll be live on the #screwtape channel by @screwlisp on https://communitymedia.video/c/screwtape_channel/videos
We'll be talking about #Markdown and #Orgdown because I recently published "Markdown Is a Disaster: Why and What to Do Instead" https://karl-voit.at/2025/08/17/Markdown-disaster/
-
In a couple of hours (8am UTC, 10am CET), I'll be live on the #screwtape channel by @screwlisp on https://communitymedia.video/c/screwtape_channel/videos
We'll be talking about #Markdown and #Orgdown because I recently published "Markdown Is a Disaster: Why and What to Do Instead" https://karl-voit.at/2025/08/17/Markdown-disaster/
-
In a couple of hours (8am UTC, 10am CET), I'll be live on the #screwtape channel by @screwlisp on https://communitymedia.video/c/screwtape_channel/videos
We'll be talking about #Markdown and #Orgdown because I recently published "Markdown Is a Disaster: Why and What to Do Instead" https://karl-voit.at/2025/08/17/Markdown-disaster/
-
In a couple of hours (8am UTC, 10am CET), I'll be live on the #screwtape channel by @screwlisp on https://communitymedia.video/c/screwtape_channel/videos
We'll be talking about #Markdown and #Orgdown because I recently published "Markdown Is a Disaster: Why and What to Do Instead" https://karl-voit.at/2025/08/17/Markdown-disaster/
-
In a couple of hours (8am UTC, 10am CET), I'll be live on the #screwtape channel by @screwlisp on https://communitymedia.video/c/screwtape_channel/videos
We'll be talking about #Markdown and #Orgdown because I recently published "Markdown Is a Disaster: Why and What to Do Instead" https://karl-voit.at/2025/08/17/Markdown-disaster/