4 ms·

I've noticed that (almost?) any talk about any editor in the last few years: emacs, vim, sublime, atom etc always brings up how good VS Code is. It's a huge en

I've noticed that (almost?) any talk about any editor in the last few years: emacs, vim, sublime, atom etc always brings up how good VS Code is. It's a huge endorsement of VS code.

thatguyagain 7y ago
I think users of VI or emacs has different ways of defining "good" here. Personally, I would never use VS Code, or any other chromium editor.
- tendencydriven 7y ago
  Is this due to some notion of it being slow? VSCode is fast, native-fast. With a fantastic plugin ecosystem I've been a full-time Vim user for the past decade (now NeoVim) but I've seriously considered switching, VSCode with vim mode turned on is truly fantastic, it's just not portable enough for my needs.
  - saagarjha 7y ago
    > VSCode is fast, native-fast. Not when starting up…
    - tendencydriven 7y ago
      I'd consider startup time the least important metric for measuring speed of a text editor - as long as it's not ridiculous. Important speed metrics for me are: Switching between buffers Scrolling up/down a page (vim used to be terrible for me before i switched terminals to Kitty) Substitutions Search
- Skunkleton 7y ago
  I keep trying to use VSCode because there are aspects of it that work better than vim. I always end up back with vim. I think that is because an editor that sits on top of a CLI is much more useful than an editor with a CLI on top of it, at least for my work.
theCodeStig 7y ago
I'm a diehard Emacs (+evil) user, and I tried VS Code for a few months. It really is quite good. Here are the few detractors that brought me back to Emacs as my primary editor. Lousy macro support from the Vim emulator. Evil is still leaps-and-bounds above anything else (possibly Vim itself). Flexibility of split windows. I like to view multiple files side-by-side. From my experience, Emacs and Vim have the best support for split panes; whereas VS Code and JetBrains editors have the worst. VS Code has nothing like Magit. In my time with VS Code, I would keep Emacs open in another space for git.
- kamaal 7y ago
  VS Code also doesn't support Macros in the same way Emacs and vi do. In fact its not even remotely close.

I've noticed that (almost?) any talk about any editor in the last few years: emacs, vim, sublime, atom etc always brings up how good VS Code is. It's a huge endorsement of VS code.

thatguyagain 7y ago

I think users of VI or emacs has different ways of defining "good" here. Personally, I would never use VS Code, or any other chromium editor.

tendencydriven 7y ago
Is this due to some notion of it being slow? VSCode is fast, native-fast. With a fantastic plugin ecosystem I've been a full-time Vim user for the past decade (now NeoVim) but I've seriously considered switching, VSCode with vim mode turned on is truly fantastic, it's just not portable enough for my needs.
- saagarjha 7y ago
  > VSCode is fast, native-fast. Not when starting up…
  - tendencydriven 7y ago
    I'd consider startup time the least important metric for measuring speed of a text editor - as long as it's not ridiculous. Important speed metrics for me are: Switching between buffers Scrolling up/down a page (vim used to be terrible for me before i switched terminals to Kitty) Substitutions Search
Skunkleton 7y ago
I keep trying to use VSCode because there are aspects of it that work better than vim. I always end up back with vim. I think that is because an editor that sits on top of a CLI is much more useful than an editor with a CLI on top of it, at least for my work.

theCodeStig 7y ago

I'm a diehard Emacs (+evil) user, and I tried VS Code for a few months. It really is quite good. Here are the few detractors that brought me back to Emacs as my primary editor. Lousy macro support from the Vim emulator. Evil is still leaps-and-bounds above anything else (possibly Vim itself). Flexibility of split windows. I like to view multiple files side-by-side. From my experience, Emacs and Vim have the best support for split panes; whereas VS Code and JetBrains editors have the worst. VS Code has nothing like Magit. In my time with VS Code, I would keep Emacs open in another space for git.

kamaal 7y ago
VS Code also doesn't support Macros in the same way Emacs and vi do. In fact its not even remotely close.