I would ask you to read the article before writing a comment like that.

The whole point of the article is that there is no Markdown. At least not a single instance from it. So when you're referring to Markdown, you're actually referring to a few dozens of slightly different markup languages which are hard to identify and except for a few, very tedious to convert.

In my opinion, this is far from being "reasonable".

Orgdown is explicitly mentioned only as one LML that doesn't come with the listed downsides of Markdown. So if you think that my article tries to convince you to use orgdown instead, you've missed the part where I say that there are many good alternatives of Markdown that do perform better when it comes to real world processes. I just tried to use orgdown as one example among many to state my point by showing an alternative. If you think that orgdown is the only one, you did not read the article carefully enough.

YMMV