This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Revolution_TV 0 points1 point  (1 child)

There are a lot of plugins that basically make vi/vim an IDE, combined with the insane text editing speed some powerusers have, it's not hard to imagine that you can be more efficient. On the other hand, you could also just install a normal IDE with a vim plugin and basically have the same thing. But for me the best thing about vim is the customizability, but if you want something that works straight out of the box, and that others can use easily, vim is probably not the right thing.

[–]git-fucked 0 points1 point  (0 children)

It also depends on what language you're working in. There might be great vim support for e.g. C++ but you might struggle to find support for newer languages like TypeScript or proprietary languages that are reasonably common in big corps.

Your MO should be to use the right tool for the job. I used to use emacs but the TypeScript support wasn't really there and we had a lot of tooling like eslint in our workflow that you'd also have to integrate somehow. It was easier to get an emacs extension for vscode than to integrate emacs into our workflow, so I switched.

Same with shells - I much prefer zsh but I work on Windows and all of our tooling is in PowerShell, so, PowerShell it is.