Documentation Source Text

Check-in [2ad4610bdf]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Minor edits to whynotgit.html due to Reddit comments.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: 2ad4610bdf102736666603cc07f596960b25ceb6bb06d2f5b3253ca471dcba98
User & Date: drh 2018-04-14 10:22:44.994
Context
2018-04-14
11:02
Add a link to the revision history of the whynotgit.html document. (check-in: 34c5347f0b user: drh tags: trunk)
10:22
Minor edits to whynotgit.html due to Reddit comments. (check-in: 2ad4610bdf user: drh tags: trunk)
2018-04-13
15:09
Fix a minor formatting issue in the tempfiles.html document. (check-in: 9f03d7ca10 user: drh tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to pages/whynotgit.in.
︙︙
17
18
19
20
21
22
23
24
25
26
27
28


29
30
31
32
33
34

35
36
37
38
39
40
41

[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>

<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],
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.


<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.








|


<
|
>
>
|
<
<
<
<
|
>








17
18
19
20
21
22
23
24
25
26

27
28
29
30




31
32
33
34
35
36
37
38
39

[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>Edits</h2>

<p>

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 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.
︙︙
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191

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
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








|








175
176
177
178
179
180
181
182
183
184
185
186
187
188
189

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 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
︙︙