Markdown’s popularity seems to stem from its simplicity. Complicating the base standard may hurt more than help, as tools that only need the basics (what it was designed for) would be pressured into full support of a complex standard.

It’s one thing for an app to create scope creep for markdown that those users can leverage. It’s another thing for the standard to create the scope creep, which is then pushed onto all the apps that may use it.

At some point, markdown loses its human readability when too many features are added. So if it gets too complicated, someone will inevitably create a new more simple standard… or push something like “markdown classic”.

John Gruber, who created markdown, doesn’t even use it for all the stuff most others do today.

https://daringfireball.net/linked/2025/06/04/apple-notes-mar...

I'm quite happy with Markdown. It powers the website I live from. I like that it's human-readable, supported by so many editors, and generally easy to work with.

I have made a few extensions to make my life easier:

- Constants like {{ current_year}} to set things in one place and repeat them in multiple places

- Custom elements like {% tableOfContents %}. I just use Jinja inside markdown.

That has served me well for 5 years or so.

If markdown allowed class and id identifiers on each content description it would be sufficient to replace HTML.

Markdown + strict extension profiles is probably the next step.