The Emacsification of Software

· ai · Source ↗

TLDR

  • Author built MDV, a native macOS Markdown viewer in ~30 minutes of interactive Claude time, arguing AI agents have unlocked personal native UI the way elisp enabled personal Emacs tooling.

Key Takeaways

  • MDV.app: SwiftUI macOS Markdown viewer with SQLite FTS full-text search, bookmarks, TOC nav, scroll position memory, and color themes, built faster than App Store alternatives.
  • Electron persists because native UI talent is scarce; Claude is described as genuinely competent at SwiftUI, not just replacement-level.
  • The Emacs analogy: AI-generated personal software is more like configuration than construction, and prompts matter more than the source code.
  • Released artifacts matter less than the idea and prompts; the author explicitly tells readers to steal the concept and build their own version.
  • Vulnerability research and exploit development tooling cited as concrete domain where agent-built native UIs are already producing gains.

Hacker News Comment Review

  • Broad consensus that “personal software” is finally arriving as originally imagined for home computing, with commenters noting relatives using LLMs to build tools without knowing how to code.
  • Counterpoint from an Emacs power user: the whole Emacs value proposition is one program for everything, so proliferating single-purpose apps is the opposite of that ethos.
  • Real reliability caveat: one commenter opened a large Markdown file in MDV, hit scroll hangs, and the app crashed, flagging that proof-of-concept polish does not equal production robustness.

Notable Comments

  • @morpheuskafka: Asks whether LLMs can finally kill Electron by automating native-per-platform UI generation from Figma specs or wireframes for standard CRUD apps.
  • @tptacek: “why learn SwiftUI at all at this point?” – frames deep SwiftUI knowledge as analogous to mastering Microsoft Word: outcomes nearly identical with or without it.

Original | Discuss on HN