Skip Navigation

What IDE do you use and why ?

45 comments
  • 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.

  • Visual Studio Professional mostly because it is included for my job and we develop on mostly Microsoft stack. VS Code for simple text editing outside of a project.

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

  • Neovim (heavily customized configuration) + tmux for me. Switched from Jetbrains IDE and VSCode to this ~5 years ago. I use neovim with every language.

    Fast to use, one app for all and I have customized that to my liking and I already spent half of my time in terminal while working anyway. + knowing how to use vim helps a lot when configuring servers remotely.

  • 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...

  • Neovim ( not heavilly customized, mostly just lsp+trisitter and mini.nvim for a lot of other stuff ) and tmux ( which is also barelly customized + sesh for sessiond management. Also have it start automatically whem opening my terminal ).

    Started using neovim right away when switching to linux back in 2018, started using tmux only last year and it's a godsend for even just regular terminal work not just with neovim.

    I also reccomend for anybody who tries to learn neovim to learn touch typing and get to atleast 60wpm, it's a big difference.

  • Android studio, clion and sometimes vs code but I'm not really happy with it.

  • mostly gedit nowadays, but i'm more on the infrastructure side now, grain of salt.

  • 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.

45 comments