Code Editors

VS Code192.9k★

VS Code is the default code editor: editing, debugging, Git integration, and extensions for any language. About three quarters of developers use it, per Stack Overflow's 2025 survey. It's the editor you don't have to justify choosing. The source is MIT licensed, while the official download is a Microsoft build with its own license and telemetry. Built-in terminal, built-in Git, built-in debugging for most languages, and a marketplace with tens of thousands of extensions. The editor is free for private and commercial use, and so is the web version at vscode.dev. Most extensions are free, though publishers can charge, and the built-in AI features run on your GitHub Copilot plan or your own model key. Copilot Chat itself is now open source inside the main repo, and one setting turns all the AI features off. Solo through enterprise: free at every scale. Settings Sync keeps your setup consistent across machines. Remote development extensions let you code on a server or inside a container from your local machine. Live Share does real-time collaboration. The catch: it's an Electron app, a web browser pretending to be a desktop app, and it gets heavy with many extensions loaded. The Microsoft telemetry in the official binary bothers some people, and you can opt out of much of it but not all. VSCodium is a community build without it. For a lighter, keyboard-driven workflow, neovim/neovim or zed-industries/zed will feel faster.

Neovim102.6k★

Neovim is a modernized fork of Vim that bends completely to your will. It runs in your terminal, it is keyboard-driven, and once the keybindings are muscle memory you edit text faster than any mouse-based workflow. Free, no paid tier, no cloud version, no premium plugins, and no company sitting on top of it. The upgrade over classic Vim is what ships in the box: first-class Lua scripting, a built-in LSP client (Language Server Protocol, the thing that gives you autocomplete and go-to-definition), tree-sitter syntax highlighting, and an async architecture that does not freeze while a plugin does heavy work. Version 0.12 pushed further with an interactive :lsp command, inline completion, workspace diagnostics, and vim.pack, an experimental plugin manager built into core. That last one matters, because the standard answer used to be install lazy.nvim first. Free at every team size, since there is nothing to buy. Solo developers, small teams, and large orgs all run the same build. The plugin ecosystem is enormous, with telescope.nvim for fuzzy finding and nvim-lspconfig for language servers, and you can turn it into a full IDE. Plenty of people run Vim keybindings inside VS Code instead, which is a legitimate middle path. The catch is the learning curve. Never used Vim-style keybindings? Expect a week of lost productivity before you get faster. Configuring it properly, meaning LSP and formatting and linting, is hours of Lua either way. LazyVim and AstroNvim hand you a working setup on day one, but you will still be reading Lua eventually. Want an editor that works out of the box? Use VS Code.

Zed90.8k★

Zed is built from scratch in Rust to be the fastest code editor you can run. It is not an Electron app wrapping a browser. Every pixel is GPU-rendered, and it shows: files open instantly, scrolling is smooth, and search across a huge repo feels immediate. Built by the team behind Atom, it has real-time multiplayer editing baked in, so you can share a workspace and pair without setup, plus AI assistant integration with Claude, GPT, and local models through Ollama. After five years in beta, Zed shipped 1.0 in 2026. That matters, because the 'is it still early?' question is now settled. The editor is stable, free, and open source. You can run it forever without paying a cent, using your own API keys for any AI features you want. Pricing is now clear instead of evolving. Personal is free and includes a couple thousand AI edit predictions a month. Pro is 10 dollars a month for unlimited predictions plus 5 dollars of hosted-model token credit, usage-based after that. Business is 30 dollars per seat for org-wide model policies, data governance, and access controls. Solo developers get the fastest editor available for nothing. Small teams gain from the multiplayer editing. Larger teams weigh the governance tier against the one real gap below. The catch is the extension ecosystem. VS Code has tens of thousands of extensions; Zed has hundreds. Before you switch, confirm your language server, your debugger, and the niche extensions your workflow depends on actually exist. The editor is excellent. The ecosystem is still catching up.

Lapce38.9k★

A code editor built from scratch in Rust, designed to be as fast as your terminal. If you've ever felt VS Code getting sluggish on a large project (slow file opens, laggy autocomplete, high memory usage), Lapce is built specifically to solve that. It uses a modal editing mode (like Vim) by default but works fine with standard editing too. The architecture runs a native GPU-rendered UI (not Electron, not a web view) and offloads heavy work like syntax parsing and code intelligence to a separate process. The result is an editor that opens instantly and stays responsive even on large codebases. Completely free and open source under Apache 2.0. No paid tier, no telemetry, no extension marketplace fees. Plugin support exists but the ecosystem is still young compared to VS Code's 40,000+ extensions. Zed is the closest competitor, also Rust-based, GPU-rendered, and focused on performance. Neovim is the other obvious choice if you want maximum speed and don't mind terminal-only. The catch: it's still in active development and not yet at 1.0. Expect rough edges: some language servers don't work perfectly, the settings UI is minimal, and the plugin ecosystem is thin. If you depend on specific VS Code extensions for your workflow, Lapce probably can't replace them yet. But if raw speed matters to you and you're comfortable with a less polished experience, it's worth watching.

coc.nvim25.2k★

coc.nvim turned Vim into an IDE before Neovim's native LSP existed. It runs a Node.js process behind your editor that hosts language servers the way VS Code does: autocomplete, diagnostics, jump-to-definition, refactoring, and an extension marketplace you install with one command. All of it free. Setup is a plugin manager away, but the friction is real: you need Node.js 20+, a recent Vim or Neovim, then per-language extensions and a JSON settings file. The Node dependency is the whole tradeoff. Neovim now ships a native LSP client that does most of this without a separate runtime, and the ecosystem's energy has shifted there. Use coc.nvim if you're on plain Vim, or if you want VS Code's extension experience without leaving the terminal. New Neovim setups should start with the built-in LSP and mason instead. Solo or team doesn't matter here: it's free for everyone. The catch is the license. It's Anti-996, a modified MIT with a labor clause, so it's free to use but not OSI-approved open source. And with Neovim's native LSP maturing, coc is the established choice, not the growing one.

evil3.9k★

Evil is the extensible vi layer for Emacs, and it is the reason a lot of Vim users can stomach Emacs at all. It brings real modal editing, normal mode, visual mode, operators, text objects, the muscle memory you already have, into Emacs without the half-measures other emulations settle for. It is thorough enough that most people forget they are not in actual Vim. There is nothing to host and nothing to pay. It is a GPL-licensed Emacs package you install through MELPA in a couple of lines. The reason you would bother: Emacs has decades of extensibility, Org mode, Magit, a built-in Lisp machine, that no Vim setup matches, and Evil lets you keep your editing keys while you get all of it. Distributions like Doom and Spacemacs are built on top of it. If you are a Vim user curious about Emacs, this is the on-ramp. If you are an Emacs user who never clicked with the default keybindings, this is the fix. Either way it costs nothing and you can back out anytime. The catch is the seam. Evil is excellent, but Emacs packages are written assuming Emacs keybindings, so you will occasionally hit a mode where Evil's bindings and a package's bindings fight. The community has shims for the big ones, evil-collection covers a lot, but expect to tune your config rather than have everything work on the first launch.

vim-lsp3.4k★

Vim-lsp is a lightweight Language Server Protocol client for Vim. It connects your editor to language servers for autocompletion, go-to-definition, hover docs, diagnostics, and code actions in any language that has an LSP server (TypeScript, Python, Rust, Go, C++, and dozens more). It is async (won't freeze your editor), works with both Vim and Neovim, and has no external dependencies beyond Vim 8+ or Neovim. Pure Vimscript. Setup means installing a language server for each language you use, then adding a few lines to your vimrc telling vim-lsp where to find it. Pair it with vim-lsp-settings for automatic server installation and configuration. The catch: stable but niche. The Neovim ecosystem has moved toward built-in LSP support (nvim-lspconfig), which makes vim-lsp more relevant for classic Vim users who want LSP without switching editors. Configuration is manual unless you add helper plugins, and the Vimscript implementation is slower than Lua-based alternatives on Neovim.

qt-creator3.1k★

Qt Creator is the purpose-built IDE for the Qt framework. Developers building cross-platform desktop, embedded, or mobile apps with C++ and QML already know this is the purpose-built tool for the job. Full code completion via Clang, integrated debugger, visual UI designer, profiler, and one-click deployment to desktop, embedded, iOS, and Android targets. The IDE itself is GPL-3.0 (free to use). Pre-built binaries from qt.io work out of the box. Building from source requires Qt 6.8+, CMake, Ninja, and optionally LLVM, which is not trivial but rarely necessary. It is a desktop application, not something you host. For Qt developers: there is nothing better. The integration with Qt libraries, build systems (CMake, qmake, Meson), and remote device deployment is tighter than anything VS Code plugins can offer. General C++ developers can use it too, though VS Code or CLion may be more flexible outside the Qt ecosystem. The catch: the IDE is free but the Qt framework has commercial licensing for closed-source products. Shipping proprietary software means either complying with (L)GPL or buying a Qt commercial license. The IDE is only truly valuable if you are already in the Qt ecosystem.

phoenix3.0k★

Phoenix is a browser-based code editor built on Adobe's discontinued Brackets. It runs from a static web server, keeps full Brackets extension compatibility, and is positioned for web development specifically. AGPL-3.0, free. No installer; it's a webapp. That means you can run it anywhere a browser runs, including locked-down corporate machines that won't let you install VS Code. The trade-off is that an uncompromised local development experience without complex build steps is the explicit goal, so it's lighter than VS Code by design. Pick this if you teach web development, work in restricted environments, or already have a Brackets workflow you want to keep alive. Solo: free, install nothing. Small teams: same. Large teams doing serious engineering: VS Code, Zed, or Cursor are still better picks. The catch: a browser-based editor is not a desktop IDE. No remote dev containers, no local file system access without an extension shim, no Copilot-grade integrations yet. Phoenix exists because Brackets shouldn't have died, not because the world needs another VS Code competitor.

vscode-mssql1.9k★

vscode-mssql is Microsoft's official extension for working with SQL Server inside VS Code. Connect to a database, browse and search objects, write T-SQL with IntelliSense, run queries, view execution plans, and edit table data inline, all without leaving the editor. MIT-licensed and free. If your day involves SQL Server and you've been bouncing out to SQL Server Management Studio, this pulls most of that work into the editor you already use. It goes well past a basic query window: visual schema designers, schema comparison, DACPAC and BACPAC support, local SQL Server container workflows, and connections to Azure SQL and Microsoft Fabric. There's GitHub Copilot integration for writing and tuning queries if you carry a subscription. Setup is the usual VS Code routine: install from the marketplace, then point it at a connection string or browse your Azure tenant. The extension costs nothing. What costs money is SQL Server, and there are free paths: Developer Edition, the Azure SQL free tier, or a local container. Solo developers and small teams on SQL Server should just install it. Larger teams standardized on the Microsoft stack get a consistent cross-platform client that behaves the same on Mac and Linux as on Windows, which SSMS never did. The catch is that this only talks to SQL Server and Azure SQL. If your shop runs Postgres or MySQL, it does nothing for you, and you'll want a general client like DBeaver or the language-specific extensions instead. It's also still catching up to SSMS on the deepest admin features.

Rune1.2k★

Rune is a code editor and a terminal multiplexer in one native window. Editors, terminals, and an AI agent sit side by side across nine workspaces, and Rune Network opens a project living on another of your machines as if it were local. GPU-accelerated, no Electron, GPL v3. It was built in private and opened up in September 2026. It runs on macOS 13.3 or later and Linux with glibc. No Windows, no Alpine. Install is a curl script or a DMG. Vim, Emacs, and standard keymaps are built in. Language support is the limit: Go and Python are fully supported, Rust and Zig are beta, TypeScript is still on the roadmap, and 300 other languages get syntax highlighting only. The agent is a separate install and takes OpenAI, Anthropic, Gemini, or Bedrock keys, a ChatGPT or Claude subscription, or local models. Solo: free, including Rune Network for 2 connected machines. Rune Pro is $10/mo or $100/yr for 10 machines and premium support. Enterprise adds SSO, SCIM, and running the network stack on your own servers, by quote. TypeScript shops should stay on zed-industries/zed or microsoft/vscode for now. The catch: telemetry is on by default, and it includes your machine's host name. Remote access needs a Rune account and runs through the company's coordination server unless you pay for Enterprise.