|
I think the intent of Markdown is more the plain syntax and non-programmer look of it than the readability. Headers, tables, headers, blockquotes, code blocks, links, and footnotes can make text hard to read. Especially link syntax can hurt readability, even if you use [url] variables instead of the full (http) url; previews trim that away, although I'm slowly become broken inside enough to find Markdown tables easier to read than HTML renderings. URLs, footnotes, and the big bad, tables of content, are the kind of set-and-forget stuff you'd probably rather prefer in a separate document or something. But it's also worth keeping in mind that people use Markdown for very different things, and those who aren't writing extensive READMEs with tables, links, and a bunch of headers won't run into those problems; I love using Markdowns on forums, for instance, but I don't actually read those comments the same way I would an article or a README. Previews are a little like fuzzy post-deploy tests for typos, poor phrasing, and syntax errors. :) |