Neovim vs VS Code: source lines of code compared

The Neovim vs VS Code comparison on OctoCounts shows side-by-side source line counts for neovim/neovim and microsoft/vscode, counted under the rules and on the dates stated below: files, total lines, code lines, comment lines, blank lines, and per-language totals, pinned to the exact commits listed below.

This page compares the source lines of code (SLOC) of neovim/neovim and microsoft/vscode using cached OctoCounts reports. Code size is not code quality: a larger count only means more source material, not a better or worse project.

As of 2026-11-15, neovim/neovim contains 1,054,757 total lines (736,174 code) across 2,679 files, while microsoft/vscode contains 3,520,191 total lines (2,748,684 code) across 11,718 files as of 2026-11-16. microsoft/vscode has about 3.7x the counted code lines of neovim/neovim under the same engine and counting rules. Code size is not code quality: a larger count only means more source material, not a better or worse project.

Metricneovim/neovimmicrosoft/vscode
Files2,67911,718
Total lines1,054,7573,520,191
Code lines736,1742,748,684
Comment lines196,603405,658
Blank lines121,980365,849
Languages counted2620

Top languages in neovim/neovim: C (37.4% of code), Vim Script (32.3% of code), PO File (15.9% of code). Top languages in microsoft/vscode: TypeScript (83.2% of code), JSON (9.4% of code), CSS (3.0% of code). C, Vim Script, PO File, Lua, C Header appear only in neovim/neovim's top languages; TypeScript, JSON, CSS, TSX, Rust appear only in microsoft/vscode's top languages.

Methodology: both counts come from cached OctoCounts reports generated with tokei. neovim/neovim was counted at ref master (commit f1d176d1ab6e) on 2026-11-15; microsoft/vscode was counted at ref main (commit b79cd7e11c27) on 2026-11-16. See the counting methodology for ignored directories and analysis options.

Both reports use the same engine and effective counting rules. Repository declarations, when enabled, are specific to each repository. neovim/neovim: tokei-15.0.0, policy directories-v1; docs excluded, tests excluded, generated excluded. Excluded directory names: .cache, .generated, .git, .next, __tests__, build, dist, doc, docs, documentation, fixtures, gen, generated, node_modules, target, test, tests, vendor. Ignored languages: none. Repository declarations: off. Exclusions are rule-based; they do not prove that every test, document or generated file was removed. microsoft/vscode: tokei-15.0.0, policy directories-v1; docs excluded, tests excluded, generated excluded. Excluded directory names: .cache, .generated, .git, .next, __tests__, build, dist, doc, docs, documentation, fixtures, gen, generated, node_modules, target, test, tests, vendor. Ignored languages: none. Repository declarations: off. Exclusions are rule-based; they do not prove that every test, document or generated file was removed.

About this comparison

Background observations recorded on 2026-09-16; language descriptions here are historical context, not claims about the current filtered shares. Use this page's measured language breakdown for current counts. Repository layout before counting filters: neovim/neovim is the Neovim editor core: a C codebase with an extensive Lua and Vimscript runtime directory of bundled plugins, syntax files, and documentation. microsoft/vscode is the VS Code product repository — a predominantly TypeScript Electron application with its build scripts, test suites, and product scaffolding. The two repositories are not directly comparable: one is an editor core, the other a full product tree.

The per-language tables show the two editors' different implementation choices directly: Neovim's counted tree is dominated by C with a large runtime layer of Lua and Vimscript, while VS Code's is dominated by TypeScript as an Electron application.

These counts do not measure which editor is more capable or which one you should use: the two repositories package different scopes of software, and editor capability depends on extensions and configuration either way.

Sources: neovim/neovim repository · microsoft/vscode repository. Statements verified 2026-09-16.

Evidence and next steps:

Saved reports remain subject to cache cleanup and replacement. Export their JSON for durable citation; live report URLs can change.

Note: code size is not code quality. OctoCounts only reports reproducible line counts and makes no claim that either project is better.

Compare FAQ

Which has more lines of code, neovim/neovim or microsoft/vscode?

As of 2026-11-15, neovim/neovim contains 1,054,757 total lines (736,174 code) across 2,679 files, while microsoft/vscode contains 3,520,191 total lines (2,748,684 code) across 11,718 files as of 2026-11-16. microsoft/vscode has about 3.7x the counted code lines of neovim/neovim under the same engine and counting rules. Code size is not code quality: a larger count only means more source material, not a better or worse project.

Does more source lines of code mean more complexity?

Not necessarily. SLOC measures size, not complexity, quality, or maintainability. A larger codebase can mean more features, more generated or vendored code, more verbose language idioms, or more tests — none of which imply the code is harder to work with. Use SLOC to gauge the scale of what you'd be reading or maintaining, not as a quality signal for neovim/neovim, microsoft/vscode, or any repository.

How is this comparison calculated?

Methodology: both counts come from cached OctoCounts reports generated with tokei. neovim/neovim was counted at ref master (commit f1d176d1ab6e) on 2026-11-15; microsoft/vscode was counted at ref main (commit b79cd7e11c27) on 2026-11-16. See the counting methodology for ignored directories and analysis options.

Can I compare a different branch, tag, or commit?

Yes. This page shows the default branch for each repository. Use the interactive comparison tool to pick any public GitHub repository, branch, tag, or commit SHA for both sides and get a fresh side-by-side report.