# The **epic** story of Markdown

What It Covers

John Gruber, creator of Markdown, joins Anil Dash on The Vergecast to trace Markdown's origin from a 2004 blogging tool built to avoid raw HTML, through its slow adoption, GitHub's pivotal role in mainstreaming it, and its current status as the default formatting language for AI systems.

Key Questions Answered

• •Readability-first design: Gruber's core design principle prioritized human readability over typing convenience, deliberately restricting Markdown to ASCII characters only. The test: print a Markdown document and hand it to someone who has never heard of it — they should immediately understand the formatting intent without any explanation or technical background.
• •Adoption tipping point: Markdown grew slowly from 2004 to roughly 2010, then accelerated through two key platform decisions. Stack Overflow adopted it in 2008 for developer Q&A formatting, and GitHub followed in 2009 with GitHub Flavored Markdown as a non-negotiable default — forcing technical users to engage with it until they became advocates.
• •Convention over specification: Gruber frames Markdown not as a rigid technical syntax but as a set of plain-text conventions. This mindset explains why he tolerates dozens of competing "flavors" — CommonMark, GitHub Flavored, etc. — because all major variants preserve the core asterisk-and-underscore conventions, achieving cultural standardization without requiring a formal enforced spec.
• •AI compatibility by design: LLMs process and emit Markdown more reliably than JSON because Markdown is fault-tolerant — a missing closing asterisk doesn't break the document. JSON's strict syntax means one wrong character invalidates the entire file. Markdown's forgiving structure, originally designed for human readability, maps directly onto how language models handle noisy text patterns.
• •WYSIWYG boundary: Gruber draws a clear line between acceptable Markdown integration and overreach. Syntax highlighting and live italics rendering are acceptable enhancements. Switching between a hidden-markup "edit mode" and a rendered "view mode" crosses into the same broken WYSIWYG territory Markdown was built to replace — reintroducing the formatting ambiguity that made early HTML editors frustrating.