As a vim user since the 90s - this is what I've landed on. It pretty easy to disable the vim plugin if you're sharing your computer with a muggle.

For me, a major reason is the pervasive spyware baked into VSCode. A lot of the code I write are things I would prefer Microsoft and the US military-industrial complex (of which MS is a big part) not have any data about.

Hello, and welcome to vscodium:

https://github.com/VSCodium/vscodium

The point of using something like VSCode is access to all of the features enabled by proprietary extensions. VSCodium has none of these and goes back to being worse than vim.

Microsoft is just engaging in open source cosplay when they publish the source code. They’re not interested in software freedoms as a concept (in fact, they are interested in explicitly denying them to users) and they certainly aren’t interested in enabling software freedoms via their releases (source code or otherwise).

Weird that you couldn't get extensions working.

Everything I've wanted works in vscodium. The only thing I couldn't get working is the remote sharing where you can connect to someone else's instance and co-edit (remote ssh editing works).

Extensions that I currently have installed:

* https://github.com/alefragnani/vscode-bookmarks

* https://github.com/gitkraken/vscode-gitlens

* https://github.com/redhat-developer/vscode-xml

* https://github.com/redhat-developer/vscode-yaml

* https://github.com/znck/grammarly

* https://github.com/VSCodeVim/Vim

* https://github.com/mousavian/ssh-config-syntax-highlighter

* https://github.com/golang/vscode-go

* https://github.com/prettier/prettier-vscode

* https://github.com/braver/vscode-solarized

Vscode is designed to fracture and vscodium doesn’t escape this. https://ghuntley.com/fracture/