Documentation Source Text

[https://git-scm.org|Git] version control system like everybody
else.
This article attempts to answer that question.  Also,
in <a href="#getthecode">section 3</a>, 
this article provides hints to Git users
about how they can easily access the SQLite source code.

<h2>Revisions To This Article</h2>
<h2>Edits</h2>

<p>
Less than 24 hours after first publication, the original text
of this article was being
[https://news.ycombinator.com/item?id=16806114|hotly debated on Hacker News],
This article has been revised multiple times in an attempt
to address concerns and misgivings and to fix inaccuracies
identified on
[https://news.ycombinator.com/item?id=16806114|Hacker News]
and was rebuked for inaccuracies, distortions, and
exaggerations.
The version you are now reading is a re-write that
attempts to correct those problems and to use a softer
and less confrontational tone.
and on
[https://www.reddit.com/r/programming/comments/8c2niw/why_sqlite_does_not_use_git/|Reddit].

<h1>A Few Reasons Why SQLite Does Not Use Git</h1>

<p>
One could summarize the reason why SQLite does not use Git in
a single sentence:  The lead SQLite developer finds Git to be
unpalatable.  If you like Git and want to use it, that's great.

which is that it is "distributed".  There are various free
alternatives to GitHub, such as GitLab, but those too have
a lot of dependencies and require a lot of server setup.

<p>
In contrast, Fossil is a single standalone binary which one
installs by placing it to $PATH.  That one binary contains all
the functionality of core Git and also GitHub or GitLab.  It
the functionality of core Git and also GitHub and/or GitLab.  It
manages a community server with wiki and bug tracking, provides
packaged downloads for consumers, login managements, and so forth,
with no extra software required.

<p>
Less administration means that programmers spend more time working
on the software (SQLite in this case) and less time fussing with