# The **epic** story of Markdown
Episode
34 min
Read time
2 min
Topics
Fundraising & VC, Design & UX, Artificial Intelligence
AI-Generated Summary
Key Takeaways
- ✓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.
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.
Notable Moment
Gruber describes reaching a third phase of his relationship with Markdown — after years of wishing it were more popular, then satisfaction at its growth, he now actively wants to slow its spread, arguing that exposing everyday users to raw Markdown syntax does them a disservice compared to well-built WYSIWYG editors.
Episode Transcript
Hello and welcome to the Vergecast, the flagship podcast of asterisks and underlines. I'm your friend David Pearce. And today on the show, we're gonna talk about Markdown. Now, Markdown is probably very familiar to you if you're like a deep nerd about note taking apps like I am, and maybe a word you've never even heard of otherwise. If you're in that latter group, don't worry. We're gonna we're gonna get into it. The way to understand markdown is basically as a way of writing text that both a computer and a human can understand. So if you're if you're writing words and you want to bold something, right, rather than go to, you know, file and format in bold, you just put two asterisks at the beginning and at the end of the word. And that tells the computer that this is bold. Mark markdown is a language that computers understand and know how to translate into other things. It also just looks like emphasis. Right? So when you're reading it, you see a word with two asterisks on either side and you go, oh, that's emphasis. You can do underlines for underlines. You can write a link in a specific way so that it can be read by markdown so you can see the title of the link and then the URL of the link itself. It's a way of writing text that both computers and humans can understand. It's a very powerful thing and it is absolutely everywhere. All of a sudden, all of these note taking apps are using it. Obsidian is a very popular one that lets you write in markdown and everything is stored on your computer as markdown files, which are basically, again, just annotated text files. This is also kind of the lingua franca of the AI industry right now. When you make a claw dot m d file, the m d stands for markdown. It's a way of writing for the computer that is simple and straightforward and that lots of people understand. Markdown is not just an inherent thing of computers. It was created. It was created by a person and that person is John Gruber, who you might also know as the writer of the blog Daring Fireball. John's gonna come on the show as is Anil Dash, who is a longtime tech executive, was around in the early days of Markdown, and really has seen it grow up into the standard it has become. We're gonna talk about where markdown came from, why it's so important that this thing became a crucial part of the way that we write text on computers, and where we go from here. The conversation is very nerdy. I will just warn you in advance, But I had a really good time, and I think you will too. But first, here's everything else happening on The Verge today. This is ninety seconds on The Verge for Monday, 06/15/2026. Fox announced that it's …
Get the full transcript (7,523 words) + summary by email — free
One-time email with the complete transcript and AI summary of this episode. No account needed.
One email, no spam. We’ll also show you what SignalCast does.
You just read a 3-minute summary of a 31-minute episode.
Get The Vergecast summarized like this every Monday — plus up to 2 more podcasts, free.
Pick Your Podcasts — FreeKeep Reading
Books, tools, and gear mentioned in this episode
SignalCast may earn commission on purchases via these links.
Tools
- MarkdownBy guest
by John Gruber
“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”
by GitHub
“GitHub followed in 2009 with GitHub Flavored Markdown as a non-negotiable default”
“Stack Overflow adopted it in 2008 for developer Q&A formatting”
“This mindset explains why he tolerates dozens of competing "flavors" — CommonMark, GitHub Flavored, etc.”
More from The Vergecast
We summarize every new episode. Want them in your inbox?
Who is the $1,059 Steam VR headset for?
We unfolded the iPhone Duo
Schools are catching onto tech’s playbook
The folding iPhone Duo is finally here | The Vergecast Livestream
The tech that made a 2-hour marathon possible
Similar Episodes
Related episodes from other podcasts
a16z Podcast
Sep 13
World Models, Robotics, and the Future of 3D AI
Software Engineering Daily
Sep 1
The Death of Online Anonymity
How I Built This
Aug 27
Advice Line with Daymond John of FUBU
How I Built This
Aug 20
Advice Line with Carlton Calvin of Razor
a16z Podcast
Jul 29
AI Micro Dramas, Generative Media, and the Future of Creativity
Explore Related Topics
This podcast is featured in Best Tech Podcasts (2026) — ranked and reviewed with AI summaries.
Read this week's AI & Machine Learning Podcast Insights — cross-podcast analysis updated weekly.
You're clearly into The Vergecast.
Every Monday, we deliver AI summaries of the latest episodes from The Vergecast and 192+ other podcasts. Free for one show.
Start My Monday DigestNo credit card · Unsubscribe anytime