One thing I like about vim - which I use literally daily - is that if you time-traveled like 30 years into the past, it would still have the same bindings.
That is actually relevant today b/c when you ssh into a cluster computing / linux farm environment, there is no “mouse”, no “clicking”, no “selecting”, etc., there is only what you can accomplish with your keyboard. Nano, pico etc. do exist - except of WHEN THEY DO NOT!!:-P - but vim is just EVERYWHERE. Regardless of how often I actually make use of that fact, I enjoy the confidence that it gives me that it is there for me when I need it:-).
Similarly for Unix shell scripting, and perl, vs. a language like Python where you never quite know what you are going to get irt to different versions on some other machine that you do not control. I mean, it’s great when it actually works but…
Then again, to each their own, and I begrudge nobody their preferences, especially if it suits what they are doing in the moment:-).
One thing I like about vim - which I use literally daily - is that if you time-traveled like 30 years into the past, it would still have the same bindings.
That is actually relevant today b/c when you ssh into a cluster computing / linux farm environment, there is no “mouse”, no “clicking”, no “selecting”, etc., there is only what you can accomplish with your keyboard. Nano, pico etc. do exist - except of WHEN THEY DO NOT!!:-P - but vim is just EVERYWHERE. Regardless of how often I actually make use of that fact, I enjoy the confidence that it gives me that it is there for me when I need it:-).
Similarly for Unix shell scripting, and perl, vs. a language like Python where you never quite know what you are going to get irt to different versions on some other machine that you do not control. I mean, it’s great when it actually works but…
Then again, to each their own, and I begrudge nobody their preferences, especially if it suits what they are doing in the moment:-).