binvim vs VS Code

VS Code is the default editor for a huge share of developers, and for good reason — a polished Electron GUI with an enormous extension marketplace. binvim answers a narrower question: it is a single-binary terminal editor with native Vim grammar and the IDE essentials — LSP, tree-sitter, four DAP debuggers, formatters, opt-in Copilot — compiled in, at ~42 MB and ~14 ms startup, running anywhere a terminal does.

+--

§ AT A GLANCE

binvim vs vs code
// dimension
binvim
VS Code
Interface
TUI · runs in a terminal
GUI · Electron (Chromium + Node)
Edit over SSH, no GUI
native, nothing to install
~Remote-SSH ext + GUI client
Size on disk
~42 MB
~370 MB
Cold start
~14 ms
1–3 s
Editing model
Vim grammar, native
~Vim via extension
Extensions
none · features compiled in
huge marketplace
LSP
built in · 24 servers
built in
Debugging (DAP)
4 adapters built in
first-class, graphical
AI
Copilot opt-in + AI pane
Copilot + Copilot Chat
License / cost
free · BSAL source-available
free · MIT core (MS build adds telemetry)
+--

§ THE HONEST TAKE

who wins what

Where VS Code is the better choice

VS Code's extension marketplace is unmatched — almost any language, framework, or tool has a polished extension. Its graphical UI makes debugging, source control, and refactoring approachable; Live Share, notebooks, web and container dev, and first-class Copilot Chat are excellent; and it is the most beginner-friendly serious editor with the largest community. If you want a graphical editor, the marketplace, or any of those workflows, VS Code is the better pick and binvim will feel spartan.

Where binvim is the better choice

binvim is built for the terminal. It runs natively over SSH with no server component and no GUI, starts in about 14 ms, and weighs about 42 MB against VS Code's ~370 MB and Electron runtime. Vim grammar is native — not an emulation layer that occasionally fights the host editor — and there is no marketplace to curate or keep updated, because LSP, tree-sitter, four DAP debuggers, formatters, Git, and Copilot are already inside the one binary. For developers who live in a terminal and think in Vim, that is the whole point.

Which should you pick?

Pick VS Code if you want a GUI, the marketplace, graphical debugging, or beginner-friendly defaults. Pick binvim if you work in the terminal, edit on remote servers over SSH, want instant startup and a tiny footprint, and think in Vim grammar. They are not really competing for the same hour of your day — choose by where you work.

$brew install bgunnarsson/binvim/binvim all install methods →
+--

§ FAQ

binvim vs vs code

Is binvim a VS Code alternative?

For terminal and Vim users, yes. binvim ships built-in LSP, tree-sitter, four DAP debuggers, formatters, and opt-in Copilot — many features people install VS Code for — but as a TUI with native Vim grammar and no extension marketplace.

Can binvim edit over SSH like VS Code Remote?

Yes, and more simply — SSH in and run binvim, with no server component and no GUI client. VS Code's Remote-SSH works well but needs the GUI on your machine plus a server it installs on the host.

Does binvim have extensions?

No marketplace, by design. Language servers, tree-sitter, debugging, formatting, Git, and Copilot are compiled in — nothing to install or update, but no arbitrary third-party extensions either.

How big is binvim compared to VS Code?

Roughly 42 MB and ~14 ms startup, versus ~370 MB and 1–3 s for VS Code on Electron. Figures are approximate and vary by platform and extension load.

+--

§ MORE COMPARISONS

deep dives