A quiet shift is underway in how developers build software. The trend, described as the "Emacsification" of software, describes a world where AI agents make it practical to build bespoke, native user interfaces for personal tools — the same way Emacs users have long crafted custom elisp packages for their own workflows.
What Emacsification means
In Emacs culture, users build entire applications in elisp to scratch personal itches. These tools are often ugly, slow, and discoverable only after years of elisp experience. The key insight is that the source code matters less than the idea — the observation that "yeah, you can do that, and it'll work well."
AI agents have now "fracked" this culture, leaking it into the wider world. Given access to a screen and inputs, agents reliably build native user interfaces. Native UI was previously the province of professionally packaged programs. Now it's as bespoke as your editor configuration.
A concrete example: building a Markdown viewer
One developer spent about 30 minutes of interactive time — plus some preparation weeks earlier — to generate a macOS Markdown viewer called MDV.app. The preparation involved setting up Xcode, git, and Claude on an old Macbook, along with tracking down Swift and macOS design skills.
The resulting viewer includes features that were missing from App Store alternatives: text search, copy-to-paste-buffer support, a SQLite FTS index of all Markdown files in its history, hot-keyed bookmarks, table-of-contents navigation, place-remembering across restarts, and fussy color themes with decent typography.
The developer notes that MDV isn't the best macOS application ever built, but it might well be the best dedicated macOS Markdown viewer. The point isn't the specific app — it's that building a native UI tool that outperforms App Store offerings is now a matter of hours, not weeks.
What changes
The first thing AI-pilled developers report is finally finishing random side projects they'd collected over years. Now those hyperspecific tools can also be pleasant to use. The developer argues this undercuts many arguments for putting up with Emacs itself and its janky user interfaces.
The practical implication: many clanky terminal apps can be drastically improved. Examples include understanding iostat across a fleet of hosts, or visualizing bpftrace output without the terminal visualization hacks Brendan Gregg had to use.
Tradeoffs
The developer acknowledges an upper limit to how good AI-generated interfaces can be with current frontier models. But that ceiling is higher than anything achievable in a TUI. The code itself is of passing interest — what matters are the prompts and the ideas.
For developers comfortable with rolling their own software, everything is now programmable in a practical sense, not merely a technical one. Building with agents feels more like configuring on a platform that has suddenly become vastly more configurable.
Bottom line
The Emacsification of software means native UI development is now fun — more fun than building web interfaces ever was. The advice: make something stupidly specific to your own problems, enjoy it for a little while, and share a screenshot and the prompts you used to make it.