renzev@lemmy.world to linuxmemes@lemmy.worldEnglish · 6 days agoMe giving advice about text editorslemmy.worldimagemessage-square51fedilinkarrow-up1408arrow-down126
arrow-up1382arrow-down1imageMe giving advice about text editorslemmy.worldrenzev@lemmy.world to linuxmemes@lemmy.worldEnglish · 6 days agomessage-square51fedilink
minus-squareCyrus Draegur@lemm.eelinkfedilinkEnglisharrow-up18·6 days agoIf I wanted to hear about what’s good about Vim, should I: a) ask what’s good about vim -OR- b) assert blindly that there is nothing good about vim so fanboys will come crawling out of the walls tripping over each other to tell me how I’m wrong?
minus-squarebabybus@sh.itjust.workslinkfedilinkEnglisharrow-up7arrow-down1·6 days agoYou shouldn’t talk about vim at all! Just write that vscode is the most flexible code editor.
minus-squareMajorHavoc@programming.devlinkfedilinkarrow-up4·6 days agoDoesn’t matter we will tell you either way. Instead of simply shortcuts, vim uses “chords”. Every new shortcut I learn can be combined intuitively* with all the other shortcuts I know. Because of this there’s no faster way to edit files than Vim in the hands of an experienced user. this let’s me spend almost no time editing code, freeing up the rest of my time for swearing at piss poor documentation. * I use “intuitively” here in a way that not merely stretches, but outright abuses the definition of the word.
If I wanted to hear about what’s good about Vim, should I:
a) ask what’s good about vim
-OR-
b) assert blindly that there is nothing good about vim so fanboys will come crawling out of the walls tripping over each other to tell me how I’m wrong?
You shouldn’t talk about vim at all! Just write that vscode is the most flexible code editor.
Doesn’t matter we will tell you either way.
* I use “intuitively” here in a way that not merely stretches, but outright abuses the definition of the word.