Fossil – Next Generation
Author of the referenced wiki post, and of SQLite and Fossil here...<p>The other day, I had 60 minutes of free time between events and so I brainstormed a few ideas for improving Fossil while sitting in a Starbucks, and those unedited, spur-of-the-moment notes trigger a big discussion on HN...  Yikes!  I <i>do</i> appreciate the feedback.  Seriously. Your comments are very, very helpful.  But let&#x27;s not attach too much weight to my musings over coffee.<p>Should I interpret the response here to mean that there is latent demand for a new-and-improved VCS in the world.  Does this mean that Git is ripe for disruption?<p><i></i>Some Issues I Have With Git<i></i><p>(1) A Git repository is a pile-of-files and&#x2F;or a bespoke key&#x2F;value store (packfiles).  The format of the repository is underdocumented.  (Proof sketch:  try to write a utility that reads content out of a git repository without first studying the git source code.)  The repository format is also brittle, as evidenced by the difficulty the Git developers have had trying to add support for hash algorithms other than SHA1.<p>(2) The key&#x2F;value design of Git limits the information you can extract from the repository.  Example:  It is difficult to find the descendants of a check-in in Git - so difficulty that nobody ever does it.  You can find ancestors easily, but finding all the descendants of a check-in is very hard.  In addition to depriving the user of useful information, the inability to find descendants of a check-in leads directly to the &quot;disconnected head&quot; problem.  That one deficiency is a show-stopper for me.  And this is but one example of the limitations imposed by the key&#x2F;value design of Git.<p>(3) For people who don&#x27;t want to put their trust in GitHub, setting up a Git server is way too difficult.<p>(4) Git requires the user to remember too much state information.  Git users should be cognizant of (a) the current check-out, (b) the &quot;index&quot; or staging area, (c) the local head, (d) the local copy of the remote head, and (e) the actual remote head.  The more mental power users must to devote to keeping track of Git, the less there is available to work on their own code.<p>(5) Git only allows one check-out per repository.  (I am told there are resent extensions to git to try to address this deficiency, but I am also told they do not work very well.)<p>(6) Git does not do a good job of remembering branch history.  In particular, branches are unnamed in Git.<p>(7) Git is for file versioning only.  Other important project information, such as bug tracking, must be handled separately.<p>Fossil is an effort to address the problems above.  I do not claim that Fossil is perfect, just that it is better than Git.  I am keen to make Fossil even better.  Your feedback is appreciated.