I’m in utter disagreement. As others have noted, the brilliance of Markdown is its simplicity — both in use and in readability. Since 2008, I've successfully ta

I’m in utter disagreement. As others have noted, the brilliance of Markdown is its simplicity — both in use and in readability. Since 2008, I've successfully taught so many people — technical and non-technical — how to use Markdown. The complexities of the various flavors is true — and the author has resisted supporting any of those flavors for that reason — but the way around that, in my opinion, is to treat each flavor as its own language. If I get to the point where my needs require I use another flavor of Markdown (I personally use Fletcher Penny's MultiMarkdown superset and have for ~12 years or so), it is with the understanding that those features are for that project. That’s the same approach I use for any collaborative effort. And frankly, if I have to look at pandoc or as Asciidoc or something else, I’m already complicating my life and the life of the people I work with. Which is fine if that’s the premise and if that is the tool we need for our job. I can and do use Markdown for documentation of almost anything I do, persona, side-hustle, or for work. The Microsoft Docs team (I’m not on that team but I work with them from time to time), even has a VS Code extension pack with a collection of plugins specifically geared to how we do docs. Markdown is a massive part of the workflow, in large part because it is so readable. I honestly wish Microsoft Word and OneNote had native Markdown support (OneNote especially. Yes, there are some kludgy plugins but I mean native). I have never been a technical writer as a profession (I’ve written my share of documentation, however), but I was a journalist for a decade and wrote millions of words in Markdown in my text editor. Markdown might not be perfect for all documentation types, but to pretend or even encourage people to NOT use it is a really, really bad take.