IDEs & Editors Deep Dive · 1 of 5

VS Code — The Editor Everyone Has Open

Microsoft shipped Visual Studio Code in 2015. Free, cross-platform, extension-driven, built on Electron + Monaco + the Language Server Protocol. Within five years it was the most-used editor on the Stack Overflow Developer Survey, and most AI-native editors today (Cursor, Windsurf, Copilot Chat) are forks or extensions of it. Whatever you write next, this is probably what you'll write it in.

ElectronLSPExtensionsRemote DevOpen Source
← Back to Cross-Cutting Tools
Why It Won

The Things VS Code Got Right

  • Language Server Protocol. One protocol, many languages. Pyright, rust-analyzer, gopls, TypeScript — every language gets the same intellisense, go-to-def, refactor experience. LSP is now the industry standard, used by Neovim, JetBrains, Zed, and others.
  • Extensions, not plugins. A separate process, declarative contributes, sandboxed. The marketplace has tens of thousands.
  • Free and cross-platform. Same UX on Windows, macOS, Linux. The MIT-licensed core is "Code-OSS"; Microsoft adds branding + telemetry to ship "VS Code".
  • Remote development. Edit code on a remote SSH host, in a Docker container, in WSL, or in a Codespace as if it were local — the editor runs on your machine, the language server runs over there.
  • Integrated terminal, source control, debugger. Enough IDE features built in that most users never need a separate one.
Configuration

How Power Users Set It Up

  • settings.json — every preference. User-scoped, workspace-scoped, or folder-scoped.
  • .vscode/launch.json — debugger configurations checked in with the repo.
  • .vscode/tasks.json — repo-local commands (build, test, lint) wired to the command palette.
  • .vscode/extensions.json — recommended extensions for the project.
  • Settings Sync — keys, themes, snippets, extensions follow your GitHub login across machines.
Tradeoffs

Honest Caveats

  • Electron. Memory and startup are not as light as a native editor. Acceptable for most; deal-breaking for terminal purists.
  • Heavy refactors are weaker than JetBrains. For day-to-day editing, parity. For large-scale rename / extract / move, JetBrains still leads.
  • Telemetry is on by default in the Microsoft build. VSCodium is a community rebuild without it.
  • Extension supply chain deserves the same skepticism as any other. Marketplace publishes have been compromised.
Continue

Other Editors

JetBrains Suite → Visual Studio → Neovim / Emacs → AI-Native Editors → ↑ Back to Cross-Cutting Tools