Skip to content

The Emacsification of Software

Source: sockpuppet.org
Author: tqbf (Thomas Ptacek)
Date: 2026-05-12

Core Thesis

AI agents have made bespoke native UI development so accessible that software culture is becoming "Emacsified" — hyper-personal, idea-driven, and endlessly configurable, with native interfaces replacing both clanky TUIs and bloated Electron apps.

The Problem: Markdown Viewing Is Broken

The author argues that AI agents have triggered a "cursed renaissance of TUI tooling," making the Markdown reading experience intolerable.

  • TUI Viewers (e.g., glow, Markless): Well-built but "hamstrung by the terminal itself," which is almost always monospaced and fatiguing.
  • GUI Editors (e.g., Obsidian, Typora, Bear): Attractive and legible, but opening a random .md file disrupts carefully arranged editing environments.
  • App Store Viewers: Fundamentally flawed — missing text search, in-app purchases, inability to copy text.

"I'm certain that at least 14% of the agita about AI code is driven by exhaustion over incessantly scrolling terminal Markdown."

Case Study: Building MDV.app with Claude

Instead of settling, the author had Claude generate a native macOS Markdown viewer: MDV.app.

  • Total elapsed time: Several hours
  • Interactive human time: ~30 minutes
  • Features: Text selection, search, SQLite FTS index, bookmarks, TOC navigation, reading position persistence, color themes, decent typography

"MDV isn't the best macOS application ever built... But it has improved my quality of life immensely."

The author urges readers not to install it, but to treat it like a shiny .emacs: "Steal the idea and make a better one."

The Native UI Inflection Point

Signal is cited as an Electron app ("a whole-ass copy of Chromium") causing constant screen flickering. Historically, native UI was rare because capable macOS developers are "rare birds."

"Claude isn't just a replacement-level SwiftUI developer. Claude is actually good."

Defining "Emacsification"

A new software culture where AI agents bypass the traditional pain of native UI development, allowing Emacs-like bespoke tooling to escape into the mainstream.

Key Characteristics

  1. Personal Software: Built to scratch a personal itch, useful mainly to the creator, often later forgotten — like "the dozens of obsolete little elisp programs littering my .emacs."
  2. Ideas > Code > Binaries: The artifact and even source code matter less than the concept.

    "For the kinds of software I'm talking about, you want the prompts more than you want the source code."

  3. Configuration Over Construction: Creating software with agents feels less like building and more like configuring a newly programmable platform.

    "'Building' implies more effort than you're expending. What you're doing feels a lot more like configuring, on a platform that has suddenly become vastly more configurable. A platform that feels a lot more like Emacs."

  4. Malleability: Users replace existing tools with their own shinier versions.

"AI agents have fracked Emacs culture, and it's leaking out into the wider world."

Implications and Outlook

  • Finished Side Projects: Developers finally complete old ideas because the UI implementation barrier has collapsed.
  • TUI Replacement: "Clanky terminal apps" can be drastically improved. The author shares a BPFUI prototype gist to replace painful terminal visualizations.
  • Undercutting Emacs Itself: Ironically, AI-native UIs remove the traditional justification for tolerating Emacs's janky UI. (Only Magit remains undisputed.)

"Building native UI is now fun; a lot more fun than building web interfaces ever was. Give it a shot; make something stupidly specific to your own problems, enjoy it for a little while, and then throw it away and make something else."