You know the exact feeling. You boot up your machine, open Emacs, and wait. And wait. While your editor loads, it’s parsing a 4,000-line .emacs file held together by duct tape, copy-pasted StackOverflow snippets from 2015, and packages whose maintainers abandoned them a decade ago.
Your Emacs configuration isn’t a masterpiece; it’s a graveyard of abandoned packages and forgotten hacks.
We treat our custom setups like sacred texts. We spend hundreds of hours tweaking keybindings, writing bespoke macros, and fighting the default behavior until the editor bends to our exact will. But Emacs 31.1 just dropped, and it’s forcing us to confront a very uncomfortable truth: the thing we love about Emacs is the exact thing holding us back.
The new update brings massive shifts. We’re talking about native Treesitter integration, Eglot (LSP) being built-in by default, and a shiny new user-lisp/ directory that finally gives your custom scripts a proper home. Emacs is moving away from third-party dependency and toward a self-contained, modern ecosystem. It’s a beautiful evolution.
But it comes with a catch. To use it, you have to let go.
Progress is a ruthless editor. It doesn’t care how many hours you spent debugging your custom keybindings.
One top comment on the new release perfectly captures the vibe: “This may be the week I declare .emacs bankruptcy and start again with a clean setup.” If you’ve been in the Emacs world long enough, you know the weight of those words. Declaring .emacs bankruptcy means admitting that your hyper-personalized environment has become a brittle, unmaintainable mess. It means accepting that the default experience is now better than your hard-won customizations.
But there’s a darker layer to this release that most users are ignoring. While we’re agonizing over our init files, a political war is brewing in the background. The controversy surrounding the portable dumper—a feature meant to speed up startup times—has gotten so heated that there are rumors Eli Zaretskii, one of the project’s most prolific maintainers, might resign over it.
Open source isn’t a democracy; it’s a theocracy with a mailing list. When the high priests quarrel, the congregation feels the tremors.
We like to think of open-source projects as pure, collaborative utopias. But Emacs is governed by humans with strong opinions, massive egos, and deeply entrenched philosophies. When internal governance clashes over technical implementations, it threatens the long-term stability of the entire platform. If the maintainers are willing to walk away over a dumper, what happens when the next big architectural shift hits?
You have a choice to make. You can keep clinging to your legacy config, patching deprecated packages and praying the maintainers don’t quit. Or, you can embrace the clean slate. The new Emacs offers a simpler, faster, more integrated experience—if you’re brave enough to delete your config.
Burn the old config. The cathedral has been rebuilt; it’s time to stop worshipping the scaffolding.
FAQ
Q: Why should I abandon a config that works for me?
A: Because it doesn't work for you—you work for it. If you're spending more time maintaining your init file than writing code, you're doing it wrong.
Q: What's the practical impact of Emacs 31.1?
A: It bakes in modern tooling (LSP, treesitter) natively. You no longer need a fragile web of third-party packages just to get basic IDE features.
Q: Is the Emacs project falling apart internally?
A: Not falling apart, but fracturing. The potential resignation of Eli Zaretskii over the portable dumper proves that open-source governance is just as messy as corporate politics.