Hacker News new | ask | show | jobs
by cylon13 2246 days ago
As long as there's no latency when actually editing text, which is my experience with vscode, I don't think it's that big of an issue. As someone that's moved from vim+plugins to vscode, I'll take the few milliseconds of latency here and there as the price of having an environment where everything just seems to work out of the box, including plugins. Sure vim is snappier, but does it really matter if I have to constantly debug why youcompleteme isn't finding my header files or whatever.

Theoretically that doesn't have to be trade off. Theoretically it's possible to build an editor like vscode with a native interface. In the actual world it doesn't exist for whatever reason, so I'm going to keep using vscode.
1 comments
hashkb 2246 days ago
Theoretically it's possible to have a not-buggy vim. It's not fair to exclude everyone who is able to configure a more performant editor just because you can't.

Your claim that "in the actual world it doesn't exist" is just not true. Thousands of lifetime vim/emacs users are scratching their heads.

link
cylon13 2245 days ago
Configuration is maintenance that I'd rather not do, it's not a matter of "can't". I used vim as my main editor for years, and I had it very much configured to my liking. Any time you have to set up plugins for a new language or a new environment though, it can be annoying, which is why I started using vscode as a front-end for neovim. Now I have a nice-feeling well-supported IDE with all the power of vim for editing.
link
hashkb 2243 days ago
Okay; my response was to what you said, which was that my editor doesn't exist.
link