@namcios: Anthropic just killed Markdown. A Claude Code engineer published an article yesterday that could herald the start of a …

Anthropic just killed Markdown. A Claude Code engineer published an article yesterday that could herald the start of a new era. The thesis is brutal: Markdown was never the right format for communication between humans and AI. It was just what we had. The author himself admits that he's never read an AI-generated Markdown file with more than 100 lines all the way through. You don't read it either. Neither do I. The insight: Markdown assumes you'll read from start to finish. HTML assumes you want to see what matters and tinker with your hands. In practice: → 30 project tickets turn into a draggable kanban with Now / Next / Later / Cut columns and an export button → Rate limiting logic turns into an SVG flowchart with inline code, instead of 200 lines of text → Code review turns into a colorized diff with dependency graphs between modules → Animation parameters, colors, regex, cron jobs get sliders with live previews → Project specs turn into 6 side-by-side options with interactive mockups All real examples from the article. All replace a wall of text with something you actually open and use. The trade-off exists: HTML is 2-4x slower to generate. But with 1 million token context, that cost has vanished. And the part no one's discussing: the generated HTML isn't just for humans. The verification agent reads it too. The spec stopped being a document and became shared memory between agents. Markdown is a report. HTML is an interface. Reports are for reading. Interfaces are for continuing the work. If you're using AI in 2026 and still asking for Markdown for everything, you might be using a smartphone as a flashlight.