Return to Vim
Feb 28, 2024
Developer experience (DX)I'm a bit of a purist at heart. Early on in my career, I self-imposed the constraint to use Vim for coding. I stuck to the command line and Vim at every opportunity.
I love the simplicity in Vim's inherent constraints. Forcing myself to use Vim proved to be the best way for me to learn its unique system of navigation.
j
k
dd
c$
yi'
vU
gg
%
cat
.
// etc., etc. <3
Throughout the years, Sublime Text replaced Vim for a bit, then VS Code replaced Sublime Text, Vim, and Terminal. I love the all-in-one ease of VS Code. VS Code has proven to be great for efficiency, with its integrated terminal, robust plugins, and Github Copilot integration.
However, I still use a 2013 MacBook Pro for my personal laptop (I love this machine!). My computer's performance is fine and the battery lasts, but this year (2024), VS Code stopped supporting my version of macOS. It forced me to give Vim another shot, and I got the feeling of being reunited with an old friend.
Even if my switch back to Vim isn't permanent, coding in Vim brings me joy.