Vim or not to Vim…
A few weeks ago I started to learn Vim, and I loved it. So much. But the problem is that when you want to mirror your old IDE’s setup in Vim environment then… the journey starts… Like choosing Linux over macOS. You are excited — a lot — but you know it will be a long road…
With great powers comes great responsibility.
— Someone’s uncle
I was afraid that hjkl would be difficult to master, but… it wasn’t. I got used to it quickly. Especially when I’m using HHKB keyboard. HHKB + Vim is a super-duo.
So all the problems I thought would be hard to deal with, were not that bad. Basic movement, motions, macros, commands… Easy peasy.
Re-configuring Vim to get most of the features I have in VSCode is the most time-consuming part. Things like: IntelliSense, plugins for git, syntax highlighters and so on. And that is the part I’ve postponed indefinitely… But I cut corners here by installing Neovim with NvChad which gives me an extended version of barebone Vim with file explorer as a sidebar buffer, tabs and fuzzy search.
I’m still divided between VSCode and Vim and the gap is getting smaller and smaller each day.
But… I’ve got this thought in the back of my head that keeps saying: keep it simple. And I can do that by using just VSCode.
