3 ms·
I've learned vim. It was not worth it. I'm more productive with vscode and nano. I know SQL, 99% of the time, an ORM is more productive, for the rest, I can st
by BiteCode_dev 5y ago
I've learned vim. It was not worth it. I'm more productive with vscode and nano.
I know SQL, 99% of the time, an ORM is more productive, for the rest, I can still write SQL manually. It's not an XOR.
- desmondl 5y agoI got pretty proficient at using vim in vscode, and personally for me the investment was worth it. It's great for working in HTML with chords like `va"p` (replace selection around quote with clipboard) and `dip` (cut out the contents inside this xml tag). YMMV depending on the type of work you do.
- chousuke 5y agoI'm completely hopeless in nano because I can't for the life of me use the arrow keys for moving around, so I just end up typing random strings of hjkl/bw or whatever in the buffer until I realize I have the wrong editor and switch to some variant of vi so I don't fight with my fingers. One major advantage of vi is that it's always there (except on Windows :().