Fossil SCM
Turned a redundancy in the "Scale" section of fossil-v-git into a clearer point. Also added a bit on Fossil's later birthday and our take on its consequences.
Commit
30a74d7e056b063c721177346d93612dd04bf6747e947ac5b6ae944449a60e26
Parent
074b896e575ce52…
1 file changed
+5
-3
+5
-3
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -247,17 +247,19 @@ | ||
| 247 | 247 | of whom do not know each others names. These thousands are responsible |
| 248 | 248 | for producing roughly 89⨉ more code than is in SQLite. (10.7 |
| 249 | 249 | [https://en.wikipedia.org/wiki/Source_lines_of_code|MLOC] vs 0.12 MLOC |
| 250 | 250 | according to [https://dwheeler.com/sloccount/|SLOCCount].) The Linux |
| 251 | 251 | kernel and its development process were already uncommonly large back in |
| 252 | -2005 when Git was designed, so Git was designed specifically with this | |
| 253 | -scenario in mind. | |
| 252 | +2005 when Git was designed, specifically to support the consequences of | |
| 253 | +having such a large set of developers working on such a large code base. | |
| 254 | 254 | |
| 255 | 255 | 95% of the code in SQLite comes from just four programmers, and 64% of |
| 256 | 256 | it is from the lead developer alone. The SQLite developers know each |
| 257 | 257 | other well and interact daily. Fossil was designed for this development |
| 258 | -model. | |
| 258 | +model. As well, we think the fact that Fossil's birth about a year later | |
| 259 | +than Git allowed it to learn from some of the key design mistakes in | |
| 260 | +Git. | |
| 259 | 261 | |
| 260 | 262 | We think you should ask yourself whether you have Linus Torvalds scale |
| 261 | 263 | software configuration management problems or D. Richard Hipp scale |
| 262 | 264 | problems when choosing your DVCS. An |
| 263 | 265 | [https://en.wikipedia.org/wiki/Impact_wrench|automotive air impact |
| 264 | 266 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -247,17 +247,19 @@ | |
| 247 | of whom do not know each others names. These thousands are responsible |
| 248 | for producing roughly 89⨉ more code than is in SQLite. (10.7 |
| 249 | [https://en.wikipedia.org/wiki/Source_lines_of_code|MLOC] vs 0.12 MLOC |
| 250 | according to [https://dwheeler.com/sloccount/|SLOCCount].) The Linux |
| 251 | kernel and its development process were already uncommonly large back in |
| 252 | 2005 when Git was designed, so Git was designed specifically with this |
| 253 | scenario in mind. |
| 254 | |
| 255 | 95% of the code in SQLite comes from just four programmers, and 64% of |
| 256 | it is from the lead developer alone. The SQLite developers know each |
| 257 | other well and interact daily. Fossil was designed for this development |
| 258 | model. |
| 259 | |
| 260 | We think you should ask yourself whether you have Linus Torvalds scale |
| 261 | software configuration management problems or D. Richard Hipp scale |
| 262 | problems when choosing your DVCS. An |
| 263 | [https://en.wikipedia.org/wiki/Impact_wrench|automotive air impact |
| 264 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -247,17 +247,19 @@ | |
| 247 | of whom do not know each others names. These thousands are responsible |
| 248 | for producing roughly 89⨉ more code than is in SQLite. (10.7 |
| 249 | [https://en.wikipedia.org/wiki/Source_lines_of_code|MLOC] vs 0.12 MLOC |
| 250 | according to [https://dwheeler.com/sloccount/|SLOCCount].) The Linux |
| 251 | kernel and its development process were already uncommonly large back in |
| 252 | 2005 when Git was designed, specifically to support the consequences of |
| 253 | having such a large set of developers working on such a large code base. |
| 254 | |
| 255 | 95% of the code in SQLite comes from just four programmers, and 64% of |
| 256 | it is from the lead developer alone. The SQLite developers know each |
| 257 | other well and interact daily. Fossil was designed for this development |
| 258 | model. As well, we think the fact that Fossil's birth about a year later |
| 259 | than Git allowed it to learn from some of the key design mistakes in |
| 260 | Git. |
| 261 | |
| 262 | We think you should ask yourself whether you have Linus Torvalds scale |
| 263 | software configuration management problems or D. Richard Hipp scale |
| 264 | problems when choosing your DVCS. An |
| 265 | [https://en.wikipedia.org/wiki/Impact_wrench|automotive air impact |
| 266 |