Vim, Vim... Vim?
Vim; the best way to write.
Vim is ubiquitous on UNIX-like systems and continues to be a reliable, scriptable editor for Nano haters...
People say Vim is old. I say it’s mature.
Vim (and Neovim, Vi) is a modal, UNIX-obeying text editor. The main configuration is at ~/.vimrc or ~/.vim/vimrc. To configure Vim you use Vimscript.
By default Vim hates Dvorak, so I remapped motion keys. My fingers travel less; my brain travels more.
Terminals are amazing; graphical interfaces are fine… if you like being babysat.
Vim and Emacs are like Doas and Sudo, replace the second with the first.
People complain Vim is hard. I complain GUI editors are soft.
Nano is fine… if your ambition maxes out at writing README files.
Vim doesn’t try to guess your intent; it expects precision. Like UNIX, it rewards clarity and punishes carelessness. That’s why it endures.
GUI editors are like training wheels for adults.
Vim doesn’t ask for your intent; it demands your respect.
VS Code crashes, Sublime Text dazzles, Nano is cute until you need macros, and Atom is already dead — Vim endures.
GUI editors have buttons; Vim has consequences.
Emacs wants to run your life; Vim wants to run your text.
Autocomplete is comforting lies; Vim is brutal truths.
Most editors negotiate with your laziness; Vim doesn’t.
Syntax highlighting is optional; muscle memory is mandatory.
Vim is fast because it doesn’t pause to hold your hand.
Plugins are optional; understanding Vimscript is a superpower.
Vim isn’t flashy, it isn’t cute, it isn’t forgiving — it’s precise, eternal, and unreasonably satisfying.
Emacs is a platform; Vim is an editor. One is for people who want a kitchen sink, the other is for people who cook.
The difference between Vim and everything else? Vim doesn’t negotiate.blogSlug=$(basename $PWD). This site has Atom/RSS feeds and PDFs, to get them go to /feed/feed.atom, /feed/feed.rss or /pdf/$blogSlug.pdf.
- < Previous
Pandoc, amazing Pandoc
