Emacs in the Age of Magic

Emacs In the Age Of Magic or, Rome Wasn't Built In A Day, More Like 10 Minutes That's the rule. That's the goal now. What are we doing? What's going on?" -- Jeremy Culhane impersonating Tucker Carlson Look, we desire you to province yourself, okay? -- Chotchkie's Manager, Office Space (1999) I began using Claude Code concerning a twelvemonth ago in September 2025. For a good week, I woke all dawn pinching myself to create certain what I'd witnessed the day former really happened. Its handling of all aspects of the coding procedure blew my socks off then, and it's an order of dimension additional capable now. On the period measure of our species, the digital age has barely just begun. When I graduated alongside a device discipline degree, the site was largely at a phase Churchill power call the "end of the beginning." And yet, fair a quarter-century later, no matter anywhere you rotate online you can't escape the faint but persistent chime of the death knell. It seems a longstanding issue in maths or theoretical computer science falls to a toaster on the daily. In what Scott Aaronson is calling The Mathocalypse, OpenAI's latest example took all of three hours to carpet bomb 8,000 investigation problems, resulting in 372 likely hits, several of them career-makers had they been solved by a human. When we say "digital age" we average a province of the art in which sealed up transistors can reproduce the identical outputs stated the identical inputs with unerring precision. The power to unambiguously differentiate an on- versus an off-signal -- the binary "digital" -- power seem trivial, but is 100% the logic why we're so comfortable handing over the reins to computers. And up until the advent of stochastic AI, it's this rigid adherence to instruction that underlies our earth perspective of technology. So whenever the first AI scientists touted their "expert systems," we scut programmers tittered inwardly. Our sanitized, sequential concept of software could never acknowledge a ruleset so thorough as to shield arbitrary, unbounded behaviors in a real-world system, one akin individual dialogue for instance. RMS appeared in a latest video recounting his CSAIL work on a circuit analyst in which he, and I'm paraphrasing, "didn't model the circuit as a scheme of equations to be solved, but rather approached it much as a individual would" by applying a sequence of diagnostics. I cognize -- he appears downright foolish, and would have sounded so equal fifteen years ago. But at the time, rules-based programming was motionless novel adequate to be considered a viable approach to AI. In particular, the feedback iteration and the bodily ergonomics of programming were vastly improving complete workflows lone recently migrated from punch cards. When sole computers motionless occupied entire rooms, operating your program frequently meant strolling it a flat down then waiting for a slot in the queue, an act of barbarism akin to dropping off your camera rotate at the photomat. When RMS was slumming it at CSAIL, it was considered a important accomplishment fair to have your text publishing company echo rear onto the display what you fair typed! Given how much additional pleasant the act of programming was becoming, group thought the rules-based paradigm could, alongside far small man-hours than ENIAC would have required, encode adequate of the earth to continue itself off as a sentient intelligence. Natural tongue understanding, for reasons not entirely apparent to me, was considered AI-complete and possessed the enormous advantage of having a testable eval complete say birdsong, which the first CMU folks initially investigated. The correct programming tongue for AI surely would have to parallel the inherent recursion of individual grammars. And so for most of the Chomsky era of tongue research, LISP/Scheme was the education set of choice (and to a lesser extent, the equally recursive Prolog). Richard Gabriel has written several engaging stuff about the philosophical distinct between the two bastions of East Coast computing, Cambridge and Murray Hill. One catered to the fuzzy "just do what i mean" semantics of academia, during the another hewed to the buttoned-up strictures of industry. Unsurprisingly, LISP was a lot slower than C, but what it misplaced in economics of execution, it made up for in economics of expression. LISP was plainly cobbled together without director supervision, and chose symbols that seemed "good for now." While C contains oddities akin "creat" and "strpbrk", at least they're according to genuine words. LISP's enigmatic "car" and "cdr" defy any lay attempt at comprehension. Which brings us, following a thousand words of prolix setup, to the subject of emacs. Whither now, we ask -- now that we have, equal to my jaded eye, a god device that makes abbreviated activity of all the material we emacsers believed we were faster at than group using lesser tools. Editing speed, customization, the expressiveness of LISP: every advantage we claimed disappeared the instant we stopped typing and started telling the AI what we wanted. We may have felt harmless bringing a gun to a blade fight, but now everyone's fair sending a drone. Take git commit via magit for instance. We idea ourselves so slick with our C-x g (magit screen), S (stage all changes), c c (commit), rattling off a meaningless commit communication in ungrammatical English, then a final C-c C-c for the win. Now Claude Code knows to immediate a grayed out "commit" following making a discrete chunk of changes, so all that's required is a quick tab-return. You win, Claude wins, and Anthropic gets a co-author credit in your git history. The only question is whether you should get a co-author credit. While we fig it out, we can discover amusement in the following two case studies in which a noob took a feasible, if not sound, conclusion to its ridiculous limit. Case Study 1, excali-mode.el ---------------------------- You: I put a image hook up on the wall. Gaude: Nice, I cognize exactly what to suspend there. [Leaves and comes rear ten minutes afterward alongside a painting.] You: Is that the Mona Lisa? Gaude: I'm Gaude. I do what I can. I can effortlessly ideate the thinking rearward excali-mode. The emacs people province a new API for a canvas widget, and a elevated schooler muses, "Hmm, what's a famous example app?" The Qwen conversation might have proceeded as: Student: There's a new canvas widget in emacs. Make excalidraw use it. Qwen: I'm fearful Excalidraw is implemented as a React component. It is currently unified in Electron apps which characteristic a React-aware browser under the hood. You may desire to regard xwidget-webkit but that won't leverage the new canvas API. Student: I desire to use the new canvas API. Qwen: You got it. Qwen afterward proceeded to *reimplement* Excalidraw's complete stack following a one-for-one substitution of the applicable layers. +-------------------------------------+--------------------------------+ | Excalidraw (web) | excali-mode | +-------------------------------------+--------------------------------+ | browser | Emacs | +-------------------------------------+--------------------------------+ | JavaScript (compiled from | Elisp | | TypeScript) | | +-------------------------------------+--------------------------------+ | rough.js and Excalidraw's render | the C component (excali-rough.c, | | code (JS) | excali-render.c, ... | +-------------------------------------+--------------------------------+ | Canvas 2D API (ctx.stroke(), | Cairo, alongside Pango for content | | ctx.fillText()), backed by Skia in | | | Chrome | | +-------------------------------------+--------------------------------+ | the page's component | Emacs 32's canvas depiction | +-------------------------------------+--------------------------------+ No pre-AI developer would always attempt specified insanity, equal under the penalty of discharge. He'd 100% discontinue before subjecting himself to porting an complete use stack for what is plainly a toy purpose. That, for improved or worse, is no longer the case. Such quixotic forays now disbursal nothing but tokens. Case Study 2, cooked.el ----------------------- You: Can you act my wedding in Mexico? Gaude: Sure can. You: Awesome, which airlines are you taking? Gaude: [Pauses] There, I built my own Boeing. Want to arrive with? You: Come again? Gaude: I'm Gaude. I do what I can. About a duration ago, r/emacs discussed construction a terminal emulation mode that preserved all of comint's quality-of-life advantages. This means nothing to the informal reader, but the gist is a terminal emulation manner that presents most straightforwardly as a plain text buffer. One respondent, whose reddit sign purported emacs mastery, described specified buffer output as being "cooked." A elevated schooler reading this must have stated to himself, "This expert of emacs can't implement this. I myself am not a master, but this man needs my help!" A brace days later, the elevated schooler posted his resolution cooked.el which correct off the rip apologized for AI use yet sought credit for being "very powerfully and immediately designed by me." And by Jove, the design does appear spotless and rational, at smallest how Claude described it to me. Then again, Claude additionally wrote the code. But there's one glaring headscratcher, and that's its full-blown, self-contained implementation of a terminal emulator, in Rust no less. In the before times, a developer would undoubtedly search specified a heavy lift from off-the-shelf kit, but the holmes replicated complete a coffee interrupt what a billionaire alongside infinite resources had been toiling complete the final five years. It likely never occurred to the high schooler that a tradition built Boeing materialized in the backyard when all he intended was a new escape rod design. Then there are the projects for which a top-to-bottom reimplementation is warranted. These would contain emacs's longstanding grand challenges akin replacing Elisp alongside Guile Scheme, or preemptive LISP threads. I accept a sufficiently curious emacs developer alongside a $100 scheme and a lengthy weekend could hammer out a beautiful fine archetypal cut. That no one's yet done it is apparent evidence that no one really wanted these things so much as they wanted to conversation concerning it. Several years ago, there was a guy whose grandiose scheme for rejuvenating emacs made the rounds on YouTube before falling rear into obscurity. Dude never wrote a sole row of code to acknowledge his vision, but his conversation became a rallying item for new users appalled by emacs's deficiency of Electron-like web interop. Loud bellyaching, or massaging a nice-to-have into a should-have-had, is a potent social hack. It's how politicians win elections. It's why complaining is so fun. You get all the notice and none of the work. Alas, among users whose self-worth isn't tied to code quality, which is most of the population, the proliferation of tradition one-offs will continue apace. A latest Hacker News thread featured an article titled "The Emacsification of Software" in which the author describes having AI compose a markdown spectator according to his exact preferences. He predicts all applications volition get likewise personalized, even ones of disassemblable closed source. He nails the ethos of r/emacs perfectly as "0% Product Hunt and 100% Show and Tell." No longer would application makers try to enforce uniformity throughout a release. Everyone would have their own personal idaho of throwaway hacks, something we finicky emacs users have lengthy been used to. As excali-mode.el and cooked.el illustrate, traditional notions of wastefulness endure definition whenever construction up and tearing downward are as easy as flipping a switch. If AI models do demonstrate to rotate into Dario's "machines of loving grace," afterward it's fair a matter of period before we entrust them alongside penning immediately to the hardware. And how God-like would that be? It's one item to map behaviors to a high-level language. Mapping them to device code would necessitate the same higher-dimensional translation that produced existence from a gobbledygook of ACGT basis pairs. The irony is affluent that AI has turned Stallman's goal of software freedom on its head. Having your device do any your imagination can think up -- that's genuine freedom. The lone capture is you'll have no idea how it works. No one does.