Hacker News new | past | comments | ask | show | jobs | submit login

I don't see this often talked about, but some of the biggest value that (n)vim provides for me is that I've configured it myself. I know what's in my .vimrc because I'm the one that put it there. It takes me longer to add new features [0], but once it is set up how I want it, I understand it more deeply.

My data is purely anecdotal but I've noticed a correlation: people who spend the added time to configure their editor (be it vim or vscode) tend to be better at using their editor. It naturally follows that the time spent configuring it leads to a better understanding (and better recall) of how it works.

In my mind, the big "omnibus" plugin bundles for (n)vim prevent that understanding just as much as a default vscode config does [1].

[0]: Either by adding a plugin or, in most cases, by incorporating what I want into (n)vim's existing systems.

[1]: And no judgement for that -- not everybody has time or patience to deeply learn every tool they use.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: