Comment by tkzed49 | Hacker News Reader

Comment by tkzed49 | Hacker News Reader

Parent Full thread

I actually don't think that developers who use things like VSCode are simply naive. Personally, I am a young person and I frequently do use vim in a low-latency terminal emulator (xterm, mlterm) without a compositor. Yes, I enjoy the fact that it is very fast. However, I still use VSCode when I'm making more complicated edits primarily because of the plugin ecosystem. Plugins "just work", are easy to configure, and all work together nicely. I get rich syntax highlighting and intellisense. I might be doing something wrong, but this was not the experience I have had with vim.

I like the UI simplicity of VSCode in contrast to native editors such as IntelliJ and Visual Studio, which I do use when I really need the features. I am interested in efforts like Onivim 2, which seek to combine these advantages.

You might be interested in coc.nvim, which can allow vim to use the LSP servers which powers VSC's intellisense. It's a bit of setup, but I've found with coc.nvim and a good syntax highlighting plugin, I can get a really great syntax highlighting and intellisense setup going.

Vim + Alacritty + Gruvbox = Happiness.

For me at least.

I've found that I get perfectly passable syntax highlighting with vim, and haven't needed anything else on my current install. If I did use an editor other than vim, I would probably use VSCodium because open build, and I do really like the visual style.

Agreed. I've been editing since the late 70s. At the moment I use VSCode the most. The plugins are the thing. They are doing things I've seen no other editor do. Of course I haven't used every editor.

The latest was I typed

    ...nameOfArrayInOtherFile

and it auto inserted

    import nameOfArrayInOtherFile from './tests/name-of-array-in-other-file.js';

a few lines above some how recognizing the pattern.

Another thing I've seen VSCode do is give me library specific warnings. Maybe that's common now-a-days in other editors but I hadn't seen it before. I'd seen language warnings but not library warnings.

Reply on news.ycombinator.com