June 18, 2026
Ctrl-Alt-Drama
Emacs, how it all started (for me)
From coding in Word to Emacs devotion — and the comments are fighting over how to survive it
TLDR: A programmer shared the hilariously messy path from writing code in Microsoft Word to embracing Emacs, the famously hardcore editor. Commenters turned it into a debate over myth, pain, and pride: some called Emacs a hacker rite of passage, while others said its learning curve is basically a prank.
This should have been a sweet little nostalgia post about one programmer’s gloriously chaotic journey from writing code in Microsoft Word to settling into Emacs, a famously intense text editor beloved by old-school coders. Instead, the community turned it into a full-blown support group, roast session, and mini holy war. The author insists this is not a political manifesto or an attack on rival editors, just a personal tale of stumbling from Notepad to Notepad++ to Sublime Text and eventually into Emacs territory. But the comments? They smelled drama instantly.
One camp went full myth-making, with veterans basically saying this is how it always starts: you learn the legends, hear that the "real hackers" all choose either Vim or Emacs, and then get pulled into the orbit. Another group was much less romantic. One commenter bluntly said Emacs fans keep calling it "self-discovering," while they’ve never once managed to use its built-in help without running to Google like everyone else. Ouch. Then came the practical hot take: don’t use fancy Emacs starter packs like Doom or Spacemacs if you’re new, because they turn curiosity into confusion. Meanwhile, Vim fans breezed in with the classic shade: Vim is easy for daily life, while Emacs is a "rocket." Which is either a compliment or a warning label.
The funniest part is the accidental comedy of the original story itself: a future serious programmer innocently using Word as a code editor because a book said "any text editor". The comments loved the vibe: half nostalgia, half survivor’s tale, with just enough editor-war tension to keep everyone dramatically typing.
Key Points
- •The article is a personal retrospective on how the author came to use Emacs as their main editor, beginning around 2008.
- •The author explicitly says their editor choice is pragmatic, not political, and that they are not trying to argue in the Emacs-versus-Vim debate.
- •The author's early programming attempts began with PHP, learned largely from books due to limited internet access and lack of installation rights.
- •A misunderstanding of what counted as a text editor led the author to write code in Microsoft Word before later switching to Notepad.
- •The author's tool progression later included EasyPHP, Notepad++, SciTE, Eclipse with PHP support, and Sublime Text.