This page compares the source lines of code (SLOC) of django/django and rails/rails 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-08, django/django contains 543,623 total lines (392,744 code) across 3,582 files, while rails/rails contains 303,718 total lines (137,418 code) across 1,862 files as of 2026-08-26. django/django is about 2.9x the size of rails/rails by code lines. Code size is not code quality: a larger count only means more source material, not a better or worse project.
| Metric | django/django | rails/rails |
|---|---|---|
| Files | 3,582 | 1,862 |
| Total lines | 543,623 | 303,718 |
| Code lines | 392,744 | 137,418 |
| Comment lines | 44,971 | 114,919 |
| Blank lines | 105,908 | 51,381 |
| Languages counted | 12 | 12 |
Top languages in django/django: PO File (60.8% of code), Python (31.1% of code), Modelica (5.6% of code). Top languages in rails/rails: Ruby (86.9% of code), JavaScript (8.5% of code), Rakefile (1.3% of code). JavaScript appears in both top language lists; PO File, Python, Modelica, CSS appear only in django/django's top languages; Ruby, Rakefile, Sass, Ruby HTML appear only in rails/rails's top languages.
Methodology: both counts come from cached OctoCounts reports generated with tokei. django/django was counted at ref 802baf5da5b8d8b44990a8214a43b951e7ab8b39 (commit 802baf5da5b8) on 2026-09-08; rails/rails was counted at ref main (commit 0ffca96a3ce5) on 2026-08-26. 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.
django/django has more code: 392,744 code lines versus 137,418 for rails/rails, about 2.9x as much, based on cached OctoCounts reports as of 2026-09-08.
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 django/django, rails/rails, or any repository.
Methodology: both counts come from cached OctoCounts reports generated with tokei. django/django was counted at ref 802baf5da5b8d8b44990a8214a43b951e7ab8b39 (commit 802baf5da5b8) on 2026-09-08; rails/rails was counted at ref main (commit 0ffca96a3ce5) on 2026-08-26. 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.