4 ms·
Inversely, this is counteracted by the logic to not use Git: https://sqlite.org/whynotgit.html https://sqlite.org/whynotgit.html
by Daviey 8y ago
Inversely, this is counteracted by the logic to not use Git:
https://sqlite.org/whynotgit.html https://sqlite.org/whynotgit.html
- raverbashing 8y agoBut to be honest, this is mostly fair criticism. Not sure why they need some of those things, but if they need it, then it's fine.
- deanishe 8y agoIt's explained in more depth here: https://fossil-scm.org/fossil/doc/trunk/www/fossil-v-git.wiki https://fossil-scm.org/fossil/doc/trunk/www/fossil-v-git.wik... Essentially, git is designed for the "bazaar" development model, while Fossil is designed for the "cathedral" one, which is what SQLite uses, being developed by just three guys working very closely together.
- Drdrdrq 8y agoThos is not the reason. The real reasons are explained quite nicely here [0] and I agree with all of them - though I still use Git because of network effects. My alternative of choice would be hg. [0] https://sqlite.org/whynotgit.html https://sqlite.org/whynotgit.html
- vnorilo 8y agohow would using a specific vcs improve the code quality?
- Daviey 8y agoThis was a response to test coverage used as a benchmark. I see them both as an indirect project quality benchmark. Neither is directly representing the actual code quality but does indicate if it is a project that matches my view of a mature project. Sure, others will disagree - but the whole idea of quality in this context is subjective anyway.
- utahcon 8y agoThe most interesting thing (IMO) left out of this page is the fact that D. Richard Hipp is the author of Fossil. This has a particular smell factor to it, not sure if it is a good or bad smell.