> What’s awful about VSCode? Genuinely curious.

- palpably slow on a recent 16-inch high-specced MBP

- does a lot of extra distracting stuff that can’t be easily turned off (I know I opened a .java file, I don’t need you to open an extra tab that takes focus to tell me I don’t have a Java extension installed. I especially don’t need you to try and launch several Java-related daemons that you know I don’t have and then also put up some notifications about failure to find them)

VSCode is fine, not great. Nice scrollbar. Still rather mouse dependent, not enough keyboard navigation (e.g. for git, AFAICT), and tabbed layouts don't use large monitors well. I like many files visible at once to see context.

Re:extensions: great when they work well. But they tend to move fast, and come and go fast. That makes combinations of them brittle. If they're conveniences, that's no problem. But if they're necessary parts of my workflow, then life can suck.

With regards to keyboard navigation it gets really good if you work for it (no harder than you would with an editor like EMACS or Vim).

I use vim extension which works well for editing the files themselves. Accessing pretty much almost anything else can be done using the command palete and you can manually assing keybinds to it as well.