April 3, 2026
Bold takes, italic burns
Why the heck are we still using Markdown?
Because 'good enough' wins—and the comments are on fire
TLDR: A viral rant slams Markdown’s messy rules and even hints at parser slowdowns, but admits it’s simple. Commenters split between “good enough” defenders and “build a better one” challengers—plus a roast of the blog’s broken links—showing the flawed standard endures because it makes writing effortless.
A spicy blog rant asked the internet’s oldest question: why are we still typing in Markdown—the “simple” text format that turns plain words into web pages? The author praises CommonMark’s clear rules but torches the language’s chaos: three ways to make text bold, funky overlaps for bold‑italic, inline HTML bolted on “like a jet engine on a tricycle,” and even a “nice” 6.9‑rated slowdown bug tied to Markdown parsers. Translation for non‑nerds: the same message can be written many different ways, which confuses people and can trip up software. Two different snippets can spit out identical pages, and that’s the core complaint.
The comments lit up. One joker cried, “Aaron needs to hurry up and reincarnate already,” invoking the late co‑author like a ghost dev who might save us. Pragmatists pulled the “worse is better” card, arguing Markdown survives because it’s friction‑free: perfect is the enemy of good. Everyday users shrugged, “it does what I want and is easy,” while a fed‑up critic snapped “put up or shut up”—if you hate it, build something better. Then the plot twist: a reader roasted the blog’s own UI for invisible text selection and unclickable links in dark mode. Peak internet—debating text formatting while the page itself won’t let you copy the link. The vibe? Markdown remains the messy king: annoying to purists, unbeatable for anyone who just wants to write, hit save, and go live.
Key Points
- •The article evaluates Markdown (CommonMark) as a minimal markup for converting plain text to HTML, noting its ease of use and legibility.
- •It argues that multiple syntaxes produce identical output (e.g., different emphasis markers), demonstrated using CommonMark Dingus.
- •The author claims nested and mixed emphasis (bold/italic) leads to parsing complexity and inconsistent behavior across variants.
- •Security concerns are raised, citing a ReDoS-related CVE with 6.9 severity affecting the markdown-it parser.
- •Allowing inline HTML within Markdown is criticized as adding complexity that conflicts with Markdown’s minimalist intent.