VS Code Problems & Issues

VS Code becomes sluggish with many extensions installed. Unoptimized marketplace extensions cause memory bloat and slow typing response. Large codebases with many files trigger high RAM usage. Some describe it as 'a bloated Electron mess held together by half-baked plugins.'

When working with mega-codebases or monorepos spanning multiple apps, VS Code's file watchers overwhelm the system. Indexing thousands of files causes lag. Reddit developers recommend splitting into multi-root workspaces or using .gitignore patterns to exclude files.

File search and global search become slow on large codebases. Waiting on searches disrupts flow. JetBrains IDEs with their indexing provide instant search. VS Code users must carefully configure file exclusions for acceptable performance.

VS Code collects usage data and crash reports, sending them to Microsoft by default. While telemetry can be disabled, it uses opt-out rather than opt-in. Third-party extensions may collect their own data outside VS Code's telemetry settings. Privacy-conscious users should consider VSCodium instead.

While VS Code's source is open, the downloadable binary includes Microsoft telemetry and proprietary licensing. For true open source, users must use VSCodium, which lacks access to Microsoft's marketplace and some proprietary extensions like GitHub Copilot.

VS Code's refactoring capabilities are basic compared to JetBrains IntelliJ or WebStorm. Java and OOP languages get limited support. Developers switching from JetBrains miss advanced rename, extract, and inline refactoring that work across entire projects.

VS Code doesn't store project or local change history, making it impossible to view previous changes from days earlier without Git commits. JetBrains IDEs have built-in local history that saves every edit. VS Code users must rely on extensions or manual backups.

While VS Code has Git support, developers switching from JetBrains miss the superior Git experience: visual diffs, Git tool window, branches/changes overview, and interactive rebase workflows. VS Code requires extensions and CLI for advanced Git operations.

Many features that are built into full IDEs require finding and installing extensions in VS Code. Setting up a productive environment takes time—choosing between competing extensions, configuring each, and troubleshooting conflicts.

Multiple extensions can conflict with each other, causing unexpected behavior. Extensions from different authors may fight over same functionality. Updates sometimes break extensions until authors catch up. Quality varies wildly in the marketplace.

Some VS Code internal plugins like Pylance are closed source. When bugs occur, it's very hard to reach Microsoft for fixes. Users can't patch issues themselves. Community alternatives exist but may lack features.

VS Code is built on Electron (Chromium + Node.js), meaning it's essentially a web browser running your editor. This architectural choice brings inherent memory overhead compared to native editors like Sublime Text or terminal-based editors.