Why I Quit VS Code for a JetBrains IDE
For a long time, VS Code was my default editor. But when I started building this portfolio—a complex, full-stack Next.js project with a Supabase backend—I realized I was spending more time managing my tools than writing code. I made the decision to quit VS Code and fully switch to a JetBrains IDE (WebStorm).
It wasn't an easy choice, but after making the switch, I’m not looking back. Here is why.
The Extension Fatigue
The main reason I left is simple: VS Code is a text editor that you have to build yourself.
In VS Code, starting a serious project meant "extension hunting." To get the environment I needed, I had to find, install, and configure a dozen different plugins: one for proper TypeScript support, another for database management, another for advanced Git history (like GitLens), and so on. I was constantly building my editor instead of building my project.
With my JetBrains IDE, the experience was the complete opposite. I just opened the project, and it all worked. It automatically detected Next.js, understood my `tailwind.config.js`, and the TypeScript integration was flawless out of the box. No plugin hunting required.
The Native Git Experience
The feature that finally convinced me to stay was Version Control. In VS Code, the built-in Git features are basic, and you almost need heavy extensions to make them usable for complex work.
In the JetBrains ecosystem, the Version Control system isn't a plugin—it's a core, powerful part of the interface. It provides a dedicated panel where I can see a full history, visually compare branches side-by-side, and handle complex merges with a robust UI. I’ve stopped dropping to the command line or relying on third-party plugins to manage my repository.
It's About Focus
Ultimately, VS Code is an amazing lightweight editor. But for a full-stack application, I don't want to waste mental energy maintaining my development environment. I want to focus purely on logic and features. Switching to a JetBrains IDE let me do exactly that.
