Why Vim Still Matters

Vim is everywhere, and it's not going anywhere

In a world of Cursor, JetBrains, and VS Code, why would anyone deliberately learn an editor whose first release was 1991? Three reasons that haven't aged in thirty years: it's preinstalled, it's language-portable, and your hands never leave the home row.

SSH into anything and Vim is already there

Every Linux server ships with Vim or its predecessor Vi. When you're debugging a production outage at 2am from a borrowed laptop, you don't get to install your favorite editor — you get whatever's on the box. Vim is the lowest-common-denominator that's actually good.

Vim shows up when you least expect it

git commit opens Vim by default for the commit message.
crontab -e edits cron jobs in Vim.
visudo edits the sudoers file in Vi.
kubectl edit, EDITOR=vim in CI scripts, Docker containers, embedded systems, recovery shells, BSD installers — Vim is the universal constant.

Speed through keyboard-only editing

Once you internalize Vim's grammar, you edit text the way fluent typists type prose: without thinking about the mechanics. No mouse, no menu hunting, no Cmd+Shift+P palette. Just precise keystrokes that compose like words into sentences. Over an eight-hour coding day, that's thousands of context switches you don't pay.

Principle: Vim isn't faster because you type more keys per second. It's faster because more of what you do is editing, and Vim optimizes for editing instead of for typing.

The ergonomic advantage

Your hands stay on the home row. No reaching for the mouse, no arrow-key stretches, no thumb gymnastics on Cmd-modifiers. Most career-ending RSI in developers comes from the chord-heavy editing patterns that modeless editors encourage. Modal editing replaces chords with sequences — and sequences are hand-friendly.

You don't have to go all-in on day one. VS Code, JetBrains, Cursor, Neovide — every modern editor has a Vim mode. Many developers learn the motions inside their existing IDE first, then graduate to Neovim once the muscle memory clicks. The investment compounds either way.

Code

Places Vim ambushes you whether you wanted it or not·bash

# Default editor for git commit messages
git commit  # opens whatever $EDITOR / git config core.editor points to (often vim)

# Cron jobs
crontab -e

# Sudoers file
sudo visudo

# Inside any Linux container or recovery shell
docker run -it --rm alpine sh -c 'apk add vim && vim /etc/hosts'

# Set Vim as your global editor
export EDITOR=vim         # bash/zsh
git config --global core.editor vim

First survival kit — the only commands you need today·vim

:q       " quit (refuses if you have unsaved changes)
:q!      " quit and discard changes
:w       " save ("write")
:wq      " save and quit
ZZ       " save and quit (Normal mode shortcut, no colon)
i        " enter Insert mode (now you can type like a normal editor)
Esc      " leave Insert mode, return to Normal mode

Exercise

Open three terminals. In the first, run git commit --allow-empty in any git repo and successfully save the commit message and exit Vim. In the second, run crontab -e, add a comment line # test cron entry, save, and exit (crontab -l should show your line). In the third, run EDITOR=vim git config --global --edit, add a comment line, save, and exit. If you can do all three without panicking, you've passed the entry test.

Vim is everywhere, and it's not going anywhere

SSH into anything and Vim is already there

Vim shows up when you least expect it

Speed through keyboard-only editing

The ergonomic advantage

Code

External links

Exercise

Progress

Comments 0