DEV Community

Discussion on: What are some stuff that you wish somebody told you when you started learning Vim?

Collapse
 
kspeakman profile image
Kasey Speakman

Under the constraints you mentioned, it could be worthwhile. However, it seems to me the main problem is being forced to use weak hardware for computationally intensive work. Do what you gotta do, but I would probably try to solve that problem first. Then if you still want to use vim for dev work, go for it!

For me, tools like vim or emacs are non-starters. I like to use tools as lightly as possible. I don't do a lot of customization, so that I don't have to worry about the repeatability of my setup. I will perform minor customizations if they make a significant difference. Otherwise, I will look for a tool that does most of what I need out of the box rather than one I have to build up its functionality around my needs.

Ironically, this is the polar opposite stance I take with the code itself. If given the choice between a framework which ties together 80% of the pieces I need, or libraries where I need to compose together the pieces myself, I will choose the library approach. But with the tools I use to write that code, I had rather not expend the effort to compose the settings I need. I had rather just find a different tool so I can concentrate my mental effort on the code.