[derekzhouzhen]

No, Markdown is a format for authoring HTML. It makes a very bad interchange format because the it leaves too much ambiguity in parsing. Also, parsing speed of Markdown is much slower than the parsing speed of a strictly conforming XML file.

[majkinetor]

That is all easily solvable.

Parsing speed, really? In this age?

It has its problems but its easy, widely adopted, with hundreds of tools, and simply way more capable than gemtext (which is simply very bad).

[gerikson]

I have a blog focussed on small entries (tweet length) consisting of Markdown in a fortune file format, that renders +10k items in about 5 seconds. Using Perl.

Parsing Markdown is fast enough.

[derekzhouzhen]

Your 10k items are probably only 2MB. Spending 5s to parse a 2MB text file is very slow, even for Perl. If you are distributing your file to users, that's 5s for each one of them. If you convert it to html and distribute the html file, your user will spend 1s in parsing, tops. This is exactly why I said Markdown makes a very bad interchange format.

[gerikson]

Nah, it's 10K items spread over 45 files, 7.5M in total, and the blog engine generates monthly pages etc. Note that I've not bothered with any optimization, I re-render all content after adding one new item.

But I agree MD isn't a good interchange format.