Nushell vs Fish: source lines of code compared

The Nushell vs Fish comparison on OctoCounts shows side-by-side source line counts for nushell/nushell and fish-shell/fish-shell, 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 nushell/nushell and fish-shell/fish-shell 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-16, nushell/nushell contains 401,347 total lines (344,698 code) across 1,813 files, while fish-shell/fish-shell contains 976,724 total lines (678,909 code) across 1,887 files as of 2026-11-11. fish-shell/fish-shell has about 2.0x the counted code lines of nushell/nushell 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.

Metricnushell/nushellfish-shell/fish-shell
Files1,8131,887
Total lines401,347976,724
Code lines344,698678,909
Comment lines17,05518,321
Blank lines39,594279,494
Languages counted1321

Top languages in nushell/nushell: Rust (97.3% of code), Nushell (1.8% of code), TOML (0.7% of code). Top languages in fish-shell/fish-shell: PO File (75.3% of code), Rust (12.1% of code), Fish (9.1% of code). Rust, Python appear in both top language lists; Nushell, TOML, Nix appear only in nushell/nushell's top languages; PO File, Fish, ReStructuredText appear only in fish-shell/fish-shell's top languages.

Methodology: both counts come from cached OctoCounts reports generated with tokei. nushell/nushell was counted at ref main (commit 0798442ca475) on 2026-11-16; fish-shell/fish-shell was counted at ref master (commit 4da2a2080191) on 2026-11-11. 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. nushell/nushell: 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. fish-shell/fish-shell: 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: nushell/nushell is the Nushell repository: the structured-data shell written in Rust — parser, evaluation engine, built-in commands, and their tests. fish-shell/fish-shell is the Fish repository: the user-friendly command-line shell with its own parser, builtins, and documentation; its core was ported from C++ to Rust for fish 4.0. Both repositories are shell source trees, counted on the dates shown in the methodology line.

Nushell and fish 4 use Rust in their core implementations, but have different shell languages and interaction models. The selected tree and counting policy determine language totals; a shared implementation language does not make their scripting semantics interchangeable.

Both repositories concentrate on the shell and its built-in commands. Inspect the pinned tree to distinguish those components from tests, documentation, and supporting scripts.

Repository size says nothing about startup time, memory use, or scripting capabilities — a shell's interactive feel depends on its features and versions, not on the line count of its source. The counts describe how much code maintains each shell.

Sources: nushell/nushell repository · fish 4.0 release notes (Rust port) · fish-shell/fish-shell 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, nushell/nushell or fish-shell/fish-shell?

As of 2026-11-16, nushell/nushell contains 401,347 total lines (344,698 code) across 1,813 files, while fish-shell/fish-shell contains 976,724 total lines (678,909 code) across 1,887 files as of 2026-11-11. fish-shell/fish-shell has about 2.0x the counted code lines of nushell/nushell 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 nushell/nushell, fish-shell/fish-shell, or any repository.

How is this comparison calculated?

Methodology: both counts come from cached OctoCounts reports generated with tokei. nushell/nushell was counted at ref main (commit 0798442ca475) on 2026-11-16; fish-shell/fish-shell was counted at ref master (commit 4da2a2080191) on 2026-11-11. 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.