Live data from Hacker News

Don't use Vim for the wrong reasons (2020)

gist.github.com

81–85 of 85 posts

Re: Don't use Vim for the wrong reasons (2020)

#81
I moved to NeoVim recently and I never missed VSCode. Most of my development happens in remote machine and I found VSCode symbol look up, code navigation painfully slow and sometimes it doesn't autocomplete. When I update my repo, all linting and LSP features stop working in VSCode. In NeoVim, it happened 0 times so far. So, yeah, OP is wrong. VIM(NeoVIM may be) is as good as any other IDE out there.

Re: Don't use Vim for the wrong reasons (2020)

#82

Earlier quoted context omitted.

Now you're just grasping for straws. By adding one line in ~/.inputrc i have vim magic in just about every TUI program available (in theory some may not, but I've yet to encounter it). Don't make it sound more difficult than it is just to make a point. Lots of tools for power-users come with vim keys today, and when I choose a tool it's one of the first things I look for.

You are saying that a more complicated setup and harder to learn tool is superior. Not sure i get your point. Parent has a point with the number of keystrokes.

I never described it as superior, I'm just pointing out GPs exaggerations. I would never expect my grandmother to use vim keys. But she's not the HN demographic and vim doesn't have to be complicated.

Re: Don't use Vim for the wrong reasons (2020)

#83

Earlier quoted context omitted.

There is no objective evidence that Vim makes you a more productive programmer. There is no evidence that avoiding a mouse makes you a more productive programmer. Use the editor you want! Vim is faster at some things and slower at some things. The main drawback of all the keypresses you see is that Vim is an imperative editor: You have to tell Vim how to edit text by glueing together lots of small commands.* IDEs are…

> Ask your local Vim nerd to rename the file they're editing. It will be entertaining! Oh that’s easy though, friend :) :!git mv % new-name > IDEs are declarative editors, you say "rename this variable" and they do it. Most NeoVim setups I’ve tried recently include LSPs with code actions, so now I just hover a variable and do “ ra” and I get a little popup window asking me for a new name. I type it, hit enter, and th…

I was indeed entertained with your imperative instructions to move the file, which is also slightly more annoying if your file is not at the top level!

Re: Don't use Vim for the wrong reasons (2020)

#84

Earlier quoted context omitted.

> Ask your local Vim nerd to rename the file they're editing. It will be entertaining! Oh that’s easy though, friend :) :!git mv % new-name > IDEs are declarative editors, you say "rename this variable" and they do it. Most NeoVim setups I’ve tried recently include LSPs with code actions, so now I just hover a variable and do “ ra” and I get a little popup window asking me for a new name. I type it, hit enter, and th…

I was indeed entertained with your imperative instructions to move the file, which is also slightly more annoying if your file is not at the top level!

Slightly, but you can tab expand the % and then just edit the name at the end of the path

Re: Don't use Vim for the wrong reasons (2020)

#85

Earlier quoted context omitted.

The difference in productivity is hard to measure. What's really gained by vim bindings is not having to leave flow state to move the cursor over there and then change that word for a different one. The same operating can be done with a cursor, but in having to leave home row and then come back to it, your mind has a chance to wander and you start thinking about whatever else is going on in life. Like why you're usin…

One thing I'm concerned about is that, if I'm moving around the files, then there's already very quick keyboard commands available for that. And if I want to look around a single file, I feel like anything else besides scrolling would be quite inferior in terms of speed and accuracy. And moving around lines and words is already quite optimal enough without a mouse, using arrows and option/command modifier. So mostly…

you have to move off the home row to get to the arrow keys though. like, even that is extraneous with vim movement.
Post reply on HN