3 ms·
Just because someone is going to link it, I might as well do it first: https://xkcd.com/927/ https://xkcd.com/927/ But yeah, "Too many implementations of Markd
by norswap 9y ago
Just because someone is going to link it, I might as well do it first: https://xkcd.com/927/ https://xkcd.com/927/
But yeah, "Too many implementations of Markdown" is not an issue a new markup language is going to solve.
"Markdown is slow!" is nonsensical: its implementations are slow (it seems the author tested this, but the link supposed to supply evidence doesn't -- I find it hard to believe that aren't fast implementations of Markdown, but perhaps). Nothing in the language makes it inherently slow.
- cptaffe 9y agoThe reference implementation of CommonMark, cmark (https://github.com/commonmark/cmark https://github.com/commonmark/cmark) > cmark can render a Markdown version of War and Peace in the blink of an eye (127 milliseconds on a ten year old laptop, vs. 100-400 milliseconds for an eye blink). In our benchmarks, cmark is 10,000 times faster than the original Markdown.pl, and on par with the very fastest available Markdown processors.
- wpietri 9y agoDefinitely. I worked for a while on a Markdown-based CMS. Markdown renderers vary widely in performance, probably because a) it's pretty easy to write a basic renderer, and b) performance doesn't matter for many use cases. But I did a bake-off, found some decently fast ones, and was confident they could be made faster if it mattered.