I just saw this story and I want to ditch VSCode https://www.bleepingcomputer.com/news/security/vscode-extensions-with-9-million-installs-pulled-over-security-risks/
I use emacs for almost everything. It took time to get used to. And some time to configure things. But now I’m just riding off my years old config files and packages I wrote as my use case haven’t changed.
I use python, rust, C, R, jupyter notebook, org mode, latex, markdown, PDFs, xml, org-roam, etc.
I keep using emacs, mainly because it has an innovative ecosystem that provides interesting ways to work - meow, consult, corfu, eglot, treesitter - so cool how these pieces for together.
Emacs with evil-mode or when I am banging around the console, neovim.
VSCode + Vim keybindings + Metals for Scala development. I used to use IntelliJ (paid and free) + the Scala plug-in, and Pycharm (free). For Scala I’d be fine with either VSCode or Jetbrains, just depends on who is paying (or not paying). I suspect that Python support in VSCode is a lot better these days so it might be a viable option to Pycharm. I need to check out VSCodium, if it works well with Metals and gets frequent updates I might make the switch.
Helix. I hate tweaking my ide. I just want to launch it and get to work. Setting up my LSP/formatter/theme is the most i’m willing to put up with and that’s all Helix asks for to be an IDE.
I’m just starting to learn to code via VSCode…
Do you guys actually think it’s worth switching? I guess it’s better to switch after you just started than when you’re in deep.
Just move to VSCodium, which is VSCode with the telemetry removed! Thats what I’m on and it’s great.
VSCode! I’m yet to find another editor that runs as smoothly on remote machines. Zed has been getting much better at this, but it’s still too buggy to consider a switch.
Check out VSCodium, which is open source telemetryless binaries of VSCode
Edit: Nevermind, it seems you already use it
I appreciate the thought!
As far as I’ve tested it, vscodium doesn’t support the same remote extensions that vscode does, it’s very silly.
That’s simply due to the repository VSCodium uses to pull extensions from (in the name of using open source extensions). Other (proprietary) extensions can be installed by downloading the .vsx file and installing manually. In most cases, though, open source alternatives to proprietary extensions exist.
While this workaround exists, it breaks Microsoft’s Visual Studio Marketplace terms of use: https://aka.ms/vsmarketplace-ToU :/
Recently switched from VsCodium to neovim - but still use Codium for some specific tasks.
My setup customization focuses around Telescope, Treesitter, Trouble & Blink.
But the advice I got was to start with vim keybindings in VSCode. I used those for six weeks until I got the hang of the basics and it had gone from frustrating to somewhat second nature.
Then I made the move.
I still use Codium for Terraform work (I have struggled to get the Terraform LS working well in neovim and I don’t use it often enough to warrant the effort) and as a GUI git client - I like the ability to add a single line from multiple files and I haven’t looked up how to do it any other way - I’ve got other stuff to do and it’s not slowing me down.
But I grew to hate Codium / VS code tabs in larger codebases. I was spending so much time looking for open tabs ( I realise this is a me problem). While neovim has tabs, it’s much more controlled and I typically use them very differently and very sparingly.
If I need to look up a data structure I just call it up temporarily with Telescope via a find files call or a live grep call (both setup to only use my project directory by default), take a peak, and move on.
The thing is - security risks are going to exist anywhere you install plugins you haven’t audited the code for. Unless you work in an IDE where there’s a company guaranteeing all plugins - there are always going to be risks.
I’d argue that VSCode, while a bigger target, has both a large user base and Microsoft’s security team going for it. I don’t see the theme being compromised as much as problem because it got solved and also prompted some serious security review of many marketplace plugins. Not ideal, but not terrible.