Table of Contents
- Hotel California
- Hands Off the Mouse
- Vim Was Never About Typing Speed
- The Case for :q!
- Plot Twist: The Terminal Strikes Back
- The Last 10% Is Where Vim Lives
- The Editor Might Leave, The Motions Won't
- So... :q! or :w?
Hotel California
There's an old joke that the hardest part of learning Vim is figuring out how to leave it. The Stack Overflow question about exiting Vim is one of the most viewed questions on the site, and the answer has become a meme: :q!.
Hands Off the Mouse
For decades, Vim's pitch has been simple: keep your hands on the keyboard and do everything faster. No mouse, no menus, no reaching for arrow keys. Just you, the home row, and a text editor that feels like an extension of your fingers.
I've never been a Vim power user. But I've always been a big believer in treating the keyboard as an extension of your hands. Reaching for the mouse only takes a fraction of a second, but when you're deep in focus, that tiny interruption is enough to break your train of thought. So while I'm not a Vim enthusiast, I still think keyboard shortcuts are essential. Not for speed, but for focus.
Then AI showed up and started writing our code. So, the question is, do we still need Vim? Or maybe it's time to type :q! and walk away for good?
The answer is much more nuanced than a yes or no.
Vim Was Never About Typing Speed
Here's the thing most people get wrong about Vim: it was never really about typing speed. You can type just as fast in Notepad.
Alright, 🔥Hot take🔥, folks: does fast typing make you a better programmer?
My take? Absolutely not! Come on! Look, the typing is the easiest part of our job. The hard part is figuring out what to type, and no amount of words per minute is going to help you there. Average speed? You're golden. Trust me.
Vim's real superpower is that it gives you a language for editing. Instead of pressing keys to move a cursor around and delete characters one by one, you describe what you want to happen:
ci" means change inside quotes
dap means delete a paragraph
. means do that again
You're not pushing characters around, you're expressing intent, and the editor carries it out.
That matters because even before AI, most of our time wasn't spent writing new code. It was spent reading, navigating, and changing code that already existed. Keep that in mind, because it's about to become very important.
The Case for :q!
Let's be fair and give the "Vim is done" side its best shot, because it makes some good points.
The Learning Curve is Harder to Justify
Learning Vim means weeks of feeling slower than before. That investment made sense when you spent eight hours a day writing code by hand. If AI writes most of it now, the payoff shrinks.
AI-First Tools Aren't Built for Modes
The modern AI workflow revolves around chat panels, inline suggestions, diff views, and an "Accept" button. When your main interaction is describing what you want in plain English, switching between normal and insert mode can feel like friction rather than power.
The Next Generation May Never Need It
Developers starting out today might never write enough code by hand to build the muscle memory Vim demands. If your fingers spend the day writing prompts instead of for-loops, hjkl starts to look like a hobby.
These are pretty solid arguments. But they miss a plot twist.
Plot Twist: The Terminal Strikes Back
Here's the irony nobody predicted: the AI era sent developers back to the terminal.
Some of the most capable AI coding tools today, like Claude Code and GitHub Copilot CLI, live right there in the command line. When I built Metal Birds Watch for the GitHub Copilot CLI challenge, a big part of my back-and-forth with the AI happened in a terminal window, not a fancy IDE.
And the terminal was never really gone for developers anyway. SSH into a server, open a shell in a container, fix a config file in production at 2 AM, and there's a good chance Vim (or its ancestor, vi) is the only editor waiting for you, judging your skills.
So while AI was supposed to pull us further from the keyboard-driven world, it actually made the terminal feel modern again. And Vim has always been the terminal's native tongue.
Gosh... our industry is basically the Daytona 500: we just keep going in circles. The question is, are you Richard Petty, or the guy he just lapped... twice.
The Last 10% Is Where Vim Lives
This is the part that changes everything.
AI is fantastic at getting you 90% of the way there. But anyone who has shipped AI-generated code knows what the last 10% looks like: rename this variable, delete that redundant block, move this method up, fix the off-by-one error, swap these two arguments.
Those aren't typing tasks. They're editing tasks, small, precise, surgical changes in code you didn't write yourself.
Your job is quietly shifting from writing code to reviewing and shaping code. You read a diff, jump to the suspicious part, search for where something is used, change one thing, and move on. That's navigation and editing, which is exactly what Vim was designed for all along.
AI took the typing. It left the editing. And editing was always Vim's real job.
The Editor Might Leave, The Motions Won't
There's an important distinction here: Vim the program and Vim the way of editing are two different things.
Vim the program may well stay a niche choice. Plenty of developers will happily live in AI-first editors with chat panels and never open a raw terminal editor.
But Vim's motions have escaped the editor. They're in VS Code through an extension, in Rider and every other JetBrains IDE through IdeaVim, in Neovim with its huge modern ecosystem and even in your browser through extensions like Vimium. You can use the shiniest AI-powered editor available and still edit like a Vim user.
So... :q! or :w?
Is this Vim's swan song? I don't think so. I think we have to keep it as an option. Can't say it's absolutely essential, but it never was to be fair.
Vim the editor is optional, as it always has been. But Vim as a way of editing becomes more valuable, not less, when your job shifts from writing code to shaping it. The less you type, the more every edit counts.
If you already know Vim, keep it. Hold onto it. If you're new, don't learn it to type faster, AI has that covered. Learn the motions to edit faster, because that's the part of the job that isn't going anywhere.
So maybe it's not time for :q!. Maybe it's just time for :w save what works and keep going.
What about you? Still using Vim or Vim motions, or has AI made you drop them? Let's discuss.
Enjoyed this write-up? Let's stay connected!
I share more software engineering insights, projects, and experiments across these platforms:
Top comments (4)
You know how much I love Vim but I don't see much of a use of it on my Dev Tools anymore.
It's kinda sad ngl. But I still believe Vim has its use cases. Not many, but still.
Yeah absolutely, for example: editing config files on bare metal linux server on different environments where I don't have Claude then it comes super handy, but this is preaty rare scenario.
I wonder when we'll have Claude on servers by default 😂