Fossil SCM

Made the "scale" issue in fossil-v-git less of a false dichotomy.

wyoung 2022-01-08 04:19 trunk
Commit 5171e59120d68e1a0b6ba89b7221c21f4facc6224972e4e3e9a49a25e0ab1054
1 file changed +12 -7
--- www/fossil-v-git.wiki
+++ www/fossil-v-git.wiki
@@ -524,11 +524,11 @@
524524
<h4 id="scale">2.5.2 Scale</h4>
525525
526526
The Linux kernel has a far bigger developer community than that of
527527
SQLite: there are thousands and thousands of contributors to Linux, most
528528
of whom do not know each others names. These thousands are responsible
529
-for producing roughly 89⨉ more code than is in SQLite. (10.7
529
+for producing roughly 89× more code than is in SQLite. (10.7
530530
[https://en.wikipedia.org/wiki/Source_lines_of_code|MLOC] vs. 0.12 MLOC
531531
according to [https://dwheeler.com/sloccount/|SLOCCount].) The Linux
532532
kernel and its development process were already uncommonly large back in
533533
2005 when Git was designed, specifically to support the consequences of
534534
having such a large set of developers working on such a large code base.
@@ -536,16 +536,21 @@
536536
95% of the code in SQLite comes from just four programmers, and 64% of
537537
it is from the lead developer alone. The SQLite developers know each
538538
other well and interact daily. Fossil was designed for this development
539539
model.
540540
541
-We think you should ask yourself whether you have Linus Torvalds scale
542
-software configuration management problems or D. Richard Hipp scale
543
-problems when choosing your DVCS. An
544
-[https://en.wikipedia.org/wiki/Impact_wrench|automotive air impact
545
-wrench] running at 8000 RPM driving an M8 socket-cap bolt at 16 cm/s is
546
-not the best way to hang a picture on the living room wall.
541
+When choosing your DVCS, we think you should ask yourself whether the
542
+scale of your software configuration management problems is closer to
543
+those Linus Torvalds designed Git to cope with or whether your work's
544
+scale is closer to that of SQLite, for which D. Richard Hipp designed
545
+Fossil. An [https://en.wikipedia.org/wiki/Impact_wrench|automotive air
546
+impact wrench] running at 8000 RPM driving an M8 socket-cap bolt at 16
547
+cm/s is not the best way to hang a picture on the living room wall.
548
+
549
+Fossil works well for projects several times the size of SQLite,
550
+[such as Tcl](https://core.tcl-lang.org/tcl/), with a repository over
551
+twice the size and with many more core committers.
547552
548553
549554
<h4 id="branches">2.5.3 Individual Branches vs. The Entire Change History</h4>
550555
551556
Both Fossil and Git store history as a directed acyclic graph (DAG)
552557
--- www/fossil-v-git.wiki
+++ www/fossil-v-git.wiki
@@ -524,11 +524,11 @@
524 <h4 id="scale">2.5.2 Scale</h4>
525
526 The Linux kernel has a far bigger developer community than that of
527 SQLite: there are thousands and thousands of contributors to Linux, most
528 of whom do not know each others names. These thousands are responsible
529 for producing roughly 89⨉ more code than is in SQLite. (10.7
530 [https://en.wikipedia.org/wiki/Source_lines_of_code|MLOC] vs. 0.12 MLOC
531 according to [https://dwheeler.com/sloccount/|SLOCCount].) The Linux
532 kernel and its development process were already uncommonly large back in
533 2005 when Git was designed, specifically to support the consequences of
534 having such a large set of developers working on such a large code base.
@@ -536,16 +536,21 @@
536 95% of the code in SQLite comes from just four programmers, and 64% of
537 it is from the lead developer alone. The SQLite developers know each
538 other well and interact daily. Fossil was designed for this development
539 model.
540
541 We think you should ask yourself whether you have Linus Torvalds scale
542 software configuration management problems or D. Richard Hipp scale
543 problems when choosing your DVCS. An
544 [https://en.wikipedia.org/wiki/Impact_wrench|automotive air impact
545 wrench] running at 8000 RPM driving an M8 socket-cap bolt at 16 cm/s is
546 not the best way to hang a picture on the living room wall.
 
 
 
 
 
547
548
549 <h4 id="branches">2.5.3 Individual Branches vs. The Entire Change History</h4>
550
551 Both Fossil and Git store history as a directed acyclic graph (DAG)
552
--- www/fossil-v-git.wiki
+++ www/fossil-v-git.wiki
@@ -524,11 +524,11 @@
524 <h4 id="scale">2.5.2 Scale</h4>
525
526 The Linux kernel has a far bigger developer community than that of
527 SQLite: there are thousands and thousands of contributors to Linux, most
528 of whom do not know each others names. These thousands are responsible
529 for producing roughly 89× more code than is in SQLite. (10.7
530 [https://en.wikipedia.org/wiki/Source_lines_of_code|MLOC] vs. 0.12 MLOC
531 according to [https://dwheeler.com/sloccount/|SLOCCount].) The Linux
532 kernel and its development process were already uncommonly large back in
533 2005 when Git was designed, specifically to support the consequences of
534 having such a large set of developers working on such a large code base.
@@ -536,16 +536,21 @@
536 95% of the code in SQLite comes from just four programmers, and 64% of
537 it is from the lead developer alone. The SQLite developers know each
538 other well and interact daily. Fossil was designed for this development
539 model.
540
541 When choosing your DVCS, we think you should ask yourself whether the
542 scale of your software configuration management problems is closer to
543 those Linus Torvalds designed Git to cope with or whether your work's
544 scale is closer to that of SQLite, for which D. Richard Hipp designed
545 Fossil. An [https://en.wikipedia.org/wiki/Impact_wrench|automotive air
546 impact wrench] running at 8000 RPM driving an M8 socket-cap bolt at 16
547 cm/s is not the best way to hang a picture on the living room wall.
548
549 Fossil works well for projects several times the size of SQLite,
550 [such as Tcl](https://core.tcl-lang.org/tcl/), with a repository over
551 twice the size and with many more core committers.
552
553
554 <h4 id="branches">2.5.3 Individual Branches vs. The Entire Change History</h4>
555
556 Both Fossil and Git store history as a directed acyclic graph (DAG)
557

Keyboard Shortcuts

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