4 ms·
> Why wouldn't we use them? On an individual level: learning curve, company policy, integrations to dev ops flavor-of-the-week and the initial difficulty to ex
by iratewizard 6y ago
> Why wouldn't we use them?
On an individual level: learning curve, company policy, integrations to dev ops flavor-of-the-week and the initial difficulty to extend the editor.
With that said, learning Vim is a good way to get exposure to a very different type of user experience in software. Plus, you may see an increase in productivity. I don't see that increase, but I at least gave it a fair shake 10 years ago.
- sdwolfz 6y agoMy increase in productivity was because of the auto completion feature from Sublime that I could not turn off, I found myself typing two letters and then waiting half a second for the drop down to appear so I could select the word. When I tried making a Jupyter notebook for a presentation I was planning and tried to type code there I realized: "I don't know the syntax, because I never needed to learn it. If I present like this I'll look like someone who doesn't know how to code". Was really ashamed of myself at that point. So I forced myself to write code in Vim without any plugins for two weeks until I could type fluently. I was in insert mode most of the time, and did not use hjkl movement naturally, but it worked wonders, I could write words without interruption, my thoughts flowed freely. Then I tried switching back to Sublime and felt less precise. Like vim was this stone path I was walking with confidence, and Sublime this fluid river I needed to row a boat on. Also for some reason I noticed that when using Vim, my wrist would feel lighter, while switching back to Sublime and using a mouse my wrist would suddenly gain "pressure". That's when I made the switch to Vim permanently and started customizing it. Only switched to Emacs, and later Spacemacs due to poor "Find and replace in project" functionality.