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-09-07, neovim/neovim contains 1,038,940 total lines (726,010 code) across 2,661 files, while microsoft/vscode contains 5,324,989 total lines (4,222,050 code) across 16,648 files as of 2026-09-09. microsoft/vscode is about 5.8x the size of neovim/neovim by code lines. Code size is not code quality: a larger count only means more source material, not a better or worse project.
| Metric | neovim/neovim | microsoft/vscode |
|---|---|---|
| Files | 2,661 | 16,648 |
| Total lines | 1,038,940 | 5,324,989 |
| Code lines | 726,010 | 4,222,050 |
| Comment lines | 193,396 | 591,796 |
| Blank lines | 119,534 | 511,143 |
| Languages counted | 12 | 12 |
Top languages in neovim/neovim: C (37.7% of code), Vim Script (32.6% of code), PO File (15.5% of code). Top languages in microsoft/vscode: TypeScript (72.9% of code), JSON (21.5% of code), CSS (1.6% of code). C, Vim Script, PO File, Lua, C Header appear only in neovim/neovim's top languages; TypeScript, JSON, CSS, TSX, JavaScript 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 9f425311c38fada4dc25f758c31933fe7b0b4dfe (commit 9f425311c38f) on 2026-09-07; microsoft/vscode was counted at ref main (commit 0af2bfdddee6) on 2026-09-09. See the counting methodology for ignored directories and analysis options.
Evidence and next steps:
Note: code size is not code quality. OctoCounts only reports reproducible line counts and makes no claim that either project is better.
microsoft/vscode has more code: 4,222,050 code lines versus 726,010 for neovim/neovim, about 5.8x as much, based on cached OctoCounts reports as of 2026-09-09.
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.
Methodology: both counts come from cached OctoCounts reports generated with tokei. neovim/neovim was counted at ref 9f425311c38fada4dc25f758c31933fe7b0b4dfe (commit 9f425311c38f) on 2026-09-07; microsoft/vscode was counted at ref main (commit 0af2bfdddee6) on 2026-09-09. See the counting methodology for ignored directories and analysis options.
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.