Fossil SCM

Updated the SQLite vs Linux project size stats, switching from ye olde SLOCCount to the whizzy new scc in the process.

tangent 2026-06-09 09:54 UTC trunk
Commit 21c98b42818476053c508642df33a6707a458a4fc9cfd00723d9f81f3c86b43c
1 file changed +4 -4
--- www/fossil-v-git.wiki
+++ www/fossil-v-git.wiki
@@ -552,18 +552,18 @@
552552
<h4 id="scale">2.5.2 Scale</h4>
553553
554554
The Linux kernel has a far bigger developer community than that of
555555
SQLite: there are thousands and thousands of contributors to Linux, most
556556
of whom do not know each other's names. These thousands are responsible
557
-for producing roughly 89× more code than is in SQLite. (10.7
558
-[https://en.wikipedia.org/wiki/Source_lines_of_code|MLOC] vs. 0.12 MLOC
559
-according to [https://dwheeler.com/sloccount/|SLOCCount].) The Linux
557
+for producing roughly 73× more code than is in SQLite. (32.0
558
+[https://en.wikipedia.org/wiki/Source_lines_of_code|MLOC] vs. 0.44 MLOC
559
+according to [https://github.com/boyter/scc | scc.) The Linux
560560
kernel and its development process were already uncommonly large back in
561561
2005 when Git was designed, specifically to support the consequences of
562562
having such a large set of developers working on such a large code base.
563563
564
-95% of the code in SQLite comes from just four programmers, and 64% of
564
+95% of the code in SQLite comes from just six programmers, and 62% of
565565
it is from the lead developer alone. The SQLite developers know each
566566
other well and interact daily. Fossil was designed for this development
567567
model.
568568
569569
When choosing your DVCS, we think you should ask yourself whether the
570570
--- www/fossil-v-git.wiki
+++ www/fossil-v-git.wiki
@@ -552,18 +552,18 @@
552 <h4 id="scale">2.5.2 Scale</h4>
553
554 The Linux kernel has a far bigger developer community than that of
555 SQLite: there are thousands and thousands of contributors to Linux, most
556 of whom do not know each other's names. These thousands are responsible
557 for producing roughly 89× more code than is in SQLite. (10.7
558 [https://en.wikipedia.org/wiki/Source_lines_of_code|MLOC] vs. 0.12 MLOC
559 according to [https://dwheeler.com/sloccount/|SLOCCount].) The Linux
560 kernel and its development process were already uncommonly large back in
561 2005 when Git was designed, specifically to support the consequences of
562 having such a large set of developers working on such a large code base.
563
564 95% of the code in SQLite comes from just four programmers, and 64% of
565 it is from the lead developer alone. The SQLite developers know each
566 other well and interact daily. Fossil was designed for this development
567 model.
568
569 When choosing your DVCS, we think you should ask yourself whether the
570
--- www/fossil-v-git.wiki
+++ www/fossil-v-git.wiki
@@ -552,18 +552,18 @@
552 <h4 id="scale">2.5.2 Scale</h4>
553
554 The Linux kernel has a far bigger developer community than that of
555 SQLite: there are thousands and thousands of contributors to Linux, most
556 of whom do not know each other's names. These thousands are responsible
557 for producing roughly 73× more code than is in SQLite. (32.0
558 [https://en.wikipedia.org/wiki/Source_lines_of_code|MLOC] vs. 0.44 MLOC
559 according to [https://github.com/boyter/scc | scc.) The Linux
560 kernel and its development process were already uncommonly large back in
561 2005 when Git was designed, specifically to support the consequences of
562 having such a large set of developers working on such a large code base.
563
564 95% of the code in SQLite comes from just six programmers, and 62% of
565 it is from the lead developer alone. The SQLite developers know each
566 other well and interact daily. Fossil was designed for this development
567 model.
568
569 When choosing your DVCS, we think you should ask yourself whether the
570

Keyboard Shortcuts

Open search /
Next entry (timeline) j
Previous entry (timeline) k
Open focused entry Enter
Show this help ?
Toggle theme Top nav button