Alacritty vs Kitty: source lines of code compared

The Alacritty vs Kitty comparison on OctoCounts shows side-by-side source line counts for alacritty/alacritty and kovidgoyal/kitty, 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 alacritty/alacritty and kovidgoyal/kitty 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-06, alacritty/alacritty contains 38,056 total lines (28,984 code) across 118 files, while kovidgoyal/kitty contains 409,431 total lines (300,327 code) across 961 files as of 2026-11-16. kovidgoyal/kitty has about 10x the counted code lines of alacritty/alacritty 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.

Metricalacritty/alacrittykovidgoyal/kitty
Files118961
Total lines38,056409,431
Code lines28,984300,327
Comment lines3,43475,989
Blank lines5,63833,115
Languages counted1021

Top languages in alacritty/alacritty: Rust (85.4% of code), SVG (9.9% of code), BASH (1.8% of code). Top languages in kovidgoyal/kitty: Python (29.0% of code), Go (26.8% of code), C (25.1% of code). Rust, SVG, BASH, GLSL, TOML appear only in alacritty/alacritty's top languages; Python, Go, C, C Header, Objective-C appear only in kovidgoyal/kitty's top languages.

Methodology: both counts come from cached OctoCounts reports generated with tokei. alacritty/alacritty was counted at ref master (commit aa5d942f46c4) on 2026-11-06; kovidgoyal/kitty was counted at ref master (commit 594c96f660cc) 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. alacritty/alacritty: 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. kovidgoyal/kitty: 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: alacritty/alacritty contains Alacritty: a GPU-accelerated terminal emulator written in Rust, including its core, platform frontends, and documentation. kovidgoyal/kitty contains kitty: a GPU-accelerated terminal also implementing its own graphics protocol, written in C with Python extensions (kittens), plus its tests and docs. Both are terminal-emulator source trees, counted on the dates shown above.

The language tables carry the main structural fact: Alacritty's counted code is Rust while kitty's is C with a Python extension layer — two different implementation stacks for the same category of application.

kitty's counted tree includes its graphics-protocol handling and the kittens extension subsystem, while Alacritty's deliberately stays minimal, so the total difference partly records how much functionality each project chooses to host in the core repository.

Terminal choice is not derivable from these numbers: rendering speed, latency, and feature set depend on the code that runs at render time and on configuration, not on the raw size of either source tree.

Sources: alacritty/alacritty repository · kovidgoyal/kitty 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, alacritty/alacritty or kovidgoyal/kitty?

As of 2026-11-06, alacritty/alacritty contains 38,056 total lines (28,984 code) across 118 files, while kovidgoyal/kitty contains 409,431 total lines (300,327 code) across 961 files as of 2026-11-16. kovidgoyal/kitty has about 10x the counted code lines of alacritty/alacritty 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 alacritty/alacritty, kovidgoyal/kitty, or any repository.

How is this comparison calculated?

Methodology: both counts come from cached OctoCounts reports generated with tokei. alacritty/alacritty was counted at ref master (commit aa5d942f46c4) on 2026-11-06; kovidgoyal/kitty was counted at ref master (commit 594c96f660cc) 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.