# The **epic** story of Markdown | The Vergecast
TL;DR
What began as John Gruber's personal solution to avoid writing HTML tags for his 2004 blog Daring Fireball has evolved into the universal markup language now powering modern note-taking apps like Obsidian and AI tools like Claude, distinguished by its radical prioritization of human readability over technical complexity.
🧠 Origins and Philosophy 4 insights
Personal frustration drove innovation
John Gruber created Markdown in 2004 after tiring of writing and repeatedly editing HTML tags for every Daring Fireball blog post, seeking a format that didn't interrupt his writing flow.
Dean Allen's pivotal advice
When Gruber suggested improvements to Allen's Textile markup language, Allen encouraged him to build his own tool instead, directly leading to Markdown's creation as a distinct alternative.
Readability trumped writability
Gruber designed Markdown so that printed text would remain completely understandable to anyone unfamiliar with the syntax, prioritizing how humans read over how computers parse.
ASCII-only constraint
Despite having access to easily-typed Unicode characters on Mac, Gruber deliberately restricted Markdown to ASCII characters to ensure universal compatibility across all systems and platforms.
🌱 Adoption and Early Web Culture 4 insights
Disappointingly slow initial growth
Despite Gruber's confidence in the tool, Markdown saw frustratingly slow adoption from 2004-2010, taking years to gain traction beyond a small circle of early adopters.
Six Apart's crucial integration
Anil Dash championed Markdown at Six Apart, where major blogs like Gawker and HuffPost adopted it because non-technical writers could compose posts without learning HTML or feeling like nerds.
Email-like familiarity
Writers preferred Markdown over alternatives like Textile because it looked identical to how they already wrote emails, making the transition seamless and intuitive.
Blogosphere enabled individual impact
The tight-knit 2000s blogging community, connected through RSS readers and discovery tools like Blogdex, allowed individual developers to create tools potentially reaching millions of users organically.
Bottom Line
Prioritize human readability and familiarity over technical elegance when designing tools meant for widespread adoption, as Markdown succeeded by matching how people already naturally wrote rather than forcing them to learn new syntax.
More from The Verge
View all
Siri is good now?? | The Vergecast
After years of dysfunction, Apple has rebuilt Siri from the ground up with a working on-device content index and Gemini-powered natural language processing, potentially making the built-in assistant good enough to disrupt the entire consumer AI app market.
YouTube is taking over Hollywood | The Vergecast
YouTube creators are bypassing traditional Hollywood gatekeeping to achieve box office success with films like "Back Rooms" and "Iron Lung," signaling an industry shift toward hybrid creator models where talent maintains multi-platform audiences rather than signing exclusive studio contracts.
Your biggest questions from Apple's WWDC | The Vergecast
Apple's WWDC 2026 keynote abandoned its usual theatrical polish for unusually honest, slow-paced live demos designed to prove Apple Intelligence actually works, while signaling an architectural shift toward horizontal AI services that transcend traditional OS boundaries and a return to rigorous design discipline.
How Steve Jobs became Steve Jobs | The Vergecast
Author Jeff Kaine discusses his book 'Steve Jobs in Exile,' arguing that Jobs' ousting from Apple in 1985 and subsequent struggles with NeXT and Pixar were essential crucibles that transformed him from an 'immature agent of chaos' into the disciplined leader capable of orchestrating Apple's historic turnaround.