[yosito]

The way I see it, Markdown is a way to add semantic formatting to a text document. Yes, you can insert other forms of code into a Markdown document, but at a certain point, inventing a new "markdown" syntax for all of the the non-semantic-text code that you want to add isn't really Markdown anymore, and just kind of misses the point. If I want to write semantic text, I'll use Markdown, if I want to create a PostgreSQL table, I'll use Postgres, etc, etc. I don't see the point of trying to make Markdown an interface for things that is wasn't designed for.

[ymblender]

Certainly, I wholeheartedly agree with your perspective. The viewpoint you expressed is directional and falls within two philosophical realms. This issue has been a longstanding debate in my mind. There is an abundance of simplistic Markdown editors available in the market. If our sole purpose is to render pure Markdown content, there are already enough editors on the market.

Here's how I convinced myself: if I only need pure Markdown, I can abstain from those advanced features. However, when I desire it to accomplish more, then perhaps MDX extensions could be a choice. Once you venture beyond the realm of basic Markdown features, it becomes less universal. Nonetheless, it can accomplish tasks that pure Markdown alone cannot.