I kind of agree, although I find them useful for different things. Markdown is terrific for casual text entry that needs a little bit of markup—being able to add italics or bold or a formatted link inside of comments or discussions is really handy, and it works well in chat clients and GitHub and things like that.
Where Markdown falls down is when people try to apply it to larger, more formal documents that need specific formatting choices: footnotes, specific list layouts, table line breaks, etc. Once you get up to trying to publish a more complicated document, you find the edges of Markdown pretty quickly. I would say "right tool for the right job", but the problem is that once devs get used to one format, they don't want to learn another.
Where Markdown falls down is when people try to apply it to larger, more formal documents that need specific formatting choices: footnotes, specific list layouts, table line breaks, etc. Once you get up to trying to publish a more complicated document, you find the edges of Markdown pretty quickly. I would say "right tool for the right job", but the problem is that once devs get used to one format, they don't want to learn another.