A look at the history and rise of Markdown, which has been adopted across the tech industry in the decades since its quiet launch in 2004 by John Gruber
Nearly every bit of the high-tech world, from the most cutting-edge AI systems at the biggest companies, to the casual scraps …
Context & Ripple Effects
Markdown’s durability has repeatedly surfaced when products move toward richer editing: Slack faced power-user backlash over its WYSIWYG interface and planned a return option after users pushed back on replacing Markdown-oriented workflows. Google subsequently added expanded Markdown support to Docs, indicating that the format’s utility extended beyond developer-native tools.
This retrospective matters because it frames Markdown not as a legacy syntax but as a shared layer across technical work. Its role remains contested for AI-agent output, however: an Anthropic engineer later argued for HTML as a denser, more interactive agent format.
First-order effects
- The article reinforces Markdown’s position as a common interchange format spanning technical and AI-oriented workflows, while explicitly casting PDFs as less central to that role.
- For authors and software teams, plain-text-first documentation remains a viable default where portability, versioning, and lightweight authoring matter more than fixed visual layout.
Second-order effects
- Products that abstract away markup face continued pressure to preserve Markdown-compatible paths, as Slack’s earlier editor backlash demonstrated.
- The contrast with the HTML-for-agents argument sharpens format selection around the task: Markdown for lightweight text exchange, HTML where richer interaction and presentation are required.
Third-order effects
- If Markdown continues to serve both humans and AI systems, document formats may increasingly be chosen as interoperable machine-readable interfaces rather than as presentation containers.
- The likely long-term outcome is coexistence rather than outright replacement: Markdown can remain a lowest-common-denominator layer while HTML and other structured formats serve more interactive workflows.
The trend: Markdown’s resurgence is part of a broader shift toward portable, text-native formats that can move cleanly among people, code repositories, and AI systems.