I use vscodium which is vscode with all the telemetry ripped out. Anybody can make malicious extensions for any IDE, so I don’t see what’s speccial in that regard. It’s just a reminder that you want to be careful about extensions you install.

I don’t! Mine isn’t integrated. I edit the code in one software and compile and run it in another.

For an actual IDE, Jetbrains. But I rarely need an actual IDE and will just generally use Vim for everything.

IntelliJ at work, neovim at home.

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.

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.

For macOS and iOS development I use Xcode (don’t really have another choice), but otherwise I am using Kate. Kate has support for macOS and Windows in addition to Linux.

I’m not touching VSCode, I don’t want to use an electron app as a code editor, nor want to use something with Microsoft spyware and propriety plugins.

VSCode with VsVim or whatever plugin. It has the combination I like. Multi-cursor fills in most of the gaps I don’t like.

I’ve tried Neovim variants a few times. I usually get stuck at something and don’t have the time to figure it out. I need to take that time to learn everything and get it right but I get tired.

Neovim

VSCode at work, VSCodium at home

I use Geany. It’s lightweight and easy to use, but there are some features missing.

I write code every day at my job. I use vim.

It does everything I need it to do, and it works exactly the same way on every system I touch, and functions the same way since I started using it decades ago (aside from being able to use arrow keys now instead of hjkl)

If I HAVE to do any coding on Windows, I use notepad++.

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.

I’m a webdev and I mainly work with Vanilla JS, React and PHP - I use phpStorm now. Everything mostly works out of the box, it auto-detects my PHP environment, composer install (which is basically just npm for PHP), nice-to-have features like Stylelint and ESLint are also integrated and enable themselves by default if specific config files are found inside a project folder…it’s just nice. Open a project, see it do all of its magic, start to code.

Previously I’ve worked with VSCode and I needed a plugin for every single feature and every plugin had its own settings that you needed to be aware of. It was horrible. I was configuring my own IDE more than I was actually writing code. I get that it’s probably more flexible than phpStorm, but I just don’t have time do dig into plugin settings all of the time - and god forbid I work with a project from another developer and he uses a different extension than me for Stylelint or formatting .md files…

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.