What I really like about VS Code, though, is that since its all web tech, and extensions are basically working off of VS Code, everything is accessible, that I've tried anyway. So like blind people don't have to make an extension speak, like with Emacs and Emacspeak.
Okay so I know like, I'm not the biggest fan of VS Code's way of doing things, being a big ol' Electron app and such, but goodness they definitely work with what they've got.
Screen reader users can exclude hints from a feature's aria-label to decrease redundancy via the "accessibility.verbosity.diff-editor" and "accessibility.verbosity.terminal" settings.
I assume most chatty folks I know are more interested in Neovim, Emacs, Nano, and Helix — I know I am — but#VSCode 1.78 includes profile templates so you can specify which extensions to load for what you're doing.
@randomgeek $work has me using #VScode instead of my favored #BBEdit, and it’s okay. The remote dev stuff is pretty slick, and of course since it’s so damn popular the plugins automate what would ordinarily be more manual customizations elsewhere.
Kinda wish now that @bbedit would embrace a similar plug-in model with an in-app directory instead of requiring manual dropping of custom scripts and configs in various places.
Recently #VSCode stopped being able to import classes or understand namespaces. It was marking all class names as not defined.
Eventually realized that /vendor/* was in my search filters. Turns out these are defined in 2 places. One is search only, the other affects code scanning & intellisense.
Challenging myself to use #neovim today instead of #VSCode.
I used to use #gvim about 18 years ago for PHP dev work, but I was never a power user.
I just feel like Code is such a massive app for the sort of coding that I do.
I am very far away from being productive, and I have no idea how to interface with language servers, etc. But I remember how to save and quit, so that's a start.
A little VS Code / git protip: in your global git configuration, you can setup files that are globally ignored, e.g.,
git config --global --add core.excludesfile "/<full path to your homedir>/.config/git/ignore"
Then you edit "~/.config/git/ignore" and add in the line .vscode/settings.json and your workspace setting overrides will no longer make your repository dirty.