As Slack gets criticism from power users for its WYSIWYG editor and plans an option to revert, a look at the history of Markdown, used by Slack's old interface
Slack just updated its longtime editor for its primary interface—and the rich-text result hints at a longstanding tension …
Context & Ripple Effects
Slack's original editor was built on Markdown, letting power users format messages by typing syntax rather than clicking buttons. The new WYSIWYG interface replaces that with rich-text controls, and the backlash from those same users has been sharp enough that Slack is already planning a revert option.
This isn't Slack's first tug-of-war over how its text works: its 2015 revamp of the long-form Posts feature was aimed at competing with email rather than serving keyboard-first users. The stakes are retention — a tension that resurfaces in Slack's 2023 biggest-ever redesign, which again leaned toward power users with a new Home section and unified Activity window.
First-order effects
- Power users who compose messages in Markdown lose their workflow overnight, and Slack's planned revert option becomes the pressure valve deciding whether they stay or grumble indefinitely.
Second-order effects
- The episode forces Slack to treat editor preference as a persistent setting to maintain, not a one-time migration — every future interface change now carries an explicit 'keep the old way' tax.
Third-order effects
- With Markdown's quiet rise since its 2004 launch now spanning the tech industry (as its history shows), collaboration vendors face a structural choice between graphical interfaces that onboard mainstream workers and syntax-based input that retains technical ones — defaults, not features, become the battleground.
The trend: Collaboration tools keep colliding with the text-formatting conventions of their most vocal users, and revert options are becoming the standard peace treaty.