codeinabox@programming.dev to Programming@programming.devEnglish · 2 months agoIf you thought the speed of writing code was your problem - you have bigger problemsdebuggingleadership.comexternal-linkmessage-square15fedilinkarrow-up1123arrow-down13file-text
arrow-up1120arrow-down1external-linkIf you thought the speed of writing code was your problem - you have bigger problemsdebuggingleadership.comcodeinabox@programming.dev to Programming@programming.devEnglish · 2 months agomessage-square15fedilinkfile-text
minus-squareMousePotatoDoesStuff@lemmy.worldlinkfedilinkarrow-up3·2 months agoThat’s part why I don’t use VIM for software development, even though I love the motions. It’s a perfect solution… for the wrong problem. (Other reasons are: I like the features that help me handle the code and catch mistakes before running it -I paid for the entire RAM and I’m going to use the entire RAM )
minus-squareFizzyOrange@programming.devlinkfedilinkarrow-up3·2 months agoVim’s solution to fast editing also isn’t very compelling since multiple cursor editing was invented. You can get 90% of the editing speed by learning 1% of the shortcuts. And the UX is slightly nicer since you get immediate feedback.
That’s part why I don’t use VIM for software development, even though I love the motions.
It’s a perfect solution… for the wrong problem.
(Other reasons are:
-I paid for the entire RAM and I’m going to use the entire RAM )
Vim’s solution to fast editing also isn’t very compelling since multiple cursor editing was invented. You can get 90% of the editing speed by learning 1% of the shortcuts. And the UX is slightly nicer since you get immediate feedback.