3 ms·
One use case would be a fallback editor for junior developers. It's still important to have syntax coloring for things like config files, JSON files, editing sh
by solidsnack9000 9y ago
One use case would be a fallback editor for junior developers. It's still important to have syntax coloring for things like config files, JSON files, editing shell scripts and writing Git commit messages; and you can't always use the IDE for these things:
* The IDE can be too slow to start.
* Maybe it's not working today.
* Maybe it's not on the server.
Vim addresses nearly all the requirements -- it's reliable; it's easy to use as $EDITOR, to be called by other CLI tools; and it offers great syntax coloring and editing options. It's just that it's too confusing. The old joke about developers shutting off the computer to quit...
- BenjiWiebe 9y agoPlease. Nowadays vim tells you how to quit. If you press control c, it clearly explains how to exit. I learned vim a few years ago, and immediately figured out how to exit it (just do what it says!) and by now it's my main editor and I love it.
- solidsnack9000 9y ago> Nowadays vim tells you how to quit. If you press control c, it clearly explains how to exit. I'm not sure whether I am happy or sad that it does that now.