|
1
|
<title>What People Are Saying</title> |
|
2
|
|
|
3
|
The following are collected quotes from various forums and blogs about |
|
4
|
Fossil, Git, and DVCSes in general. This collection is put together |
|
5
|
by the creator of Fossil, so of course there is selection bias... |
|
6
|
|
|
7
|
<h2>On The Usability Of Git</h2> |
|
8
|
|
|
9
|
<ol> |
|
10
|
<li>Git approaches the usability of iptables, which is to say, utterly |
|
11
|
unusable unless you have the manpage tattooed on you arm. |
|
12
|
|
|
13
|
<p class="local-indent"> |
|
14
|
<i>by mml at [http://news.ycombinator.com/item?id=1433387]</i> |
|
15
|
</p> |
|
16
|
|
|
17
|
<li><nowiki>It's simplest to think of the state of your [git] repository |
|
18
|
as a point in a high-dimensional "code-space", in which branches are |
|
19
|
represented as n-dimensional membranes, mapping the spatial loci of |
|
20
|
successive commits onto the projected manifold of each cloned |
|
21
|
repository.</nowiki> |
|
22
|
|
|
23
|
<p class="local-indent"> |
|
24
|
<i>by Jonathan Hartley at |
|
25
|
[https://www.tartley.com/posts/a-guide-to-git-using-spatial-analogies]; |
|
26
|
<br>Quoted here: [https://lwn.net/Articles/420152/].</i> |
|
27
|
</p> |
|
28
|
|
|
29
|
<li>Git is not a Prius. Git is a Model T. |
|
30
|
Its plumbing and wiring sticks out all over the place. |
|
31
|
You have to be a mechanic to operate it successfully or you'll be |
|
32
|
stuck on the side of the road when it breaks down. |
|
33
|
And it <b>will</b> break down. |
|
34
|
|
|
35
|
<p class="local-indent"> |
|
36
|
<i>Nick Farina at [http://nfarina.com/post/9868516270/git-is-simpler]</i> |
|
37
|
</p> |
|
38
|
|
|
39
|
<li>Initial revision of "git", The information manager from hell |
|
40
|
|
|
41
|
<p class="local-indent"> |
|
42
|
<i>Linus Torvalds - 2005-04-07 22:13:13<br> |
|
43
|
Commit comment on the very first source-code check-in for git |
|
44
|
</p> |
|
45
|
|
|
46
|
<li>I've been experimenting a lot with git at work. |
|
47
|
Damn, it's complicated. |
|
48
|
It has things to trip you up with that sane people just wouldn't ever both with |
|
49
|
including the ability to allow you to commit stuff in such a way that you can't find |
|
50
|
it again afterwards (!!!) |
|
51
|
Demented workflow complexity on acid? |
|
52
|
<p>* dkf really wishes he could use fossil instead</p> |
|
53
|
<p class="local-indent"> |
|
54
|
<i>by Donal K. Fellow (dkf) on the Tcl/Tk chatroom, 2013-04-09.</i> |
|
55
|
</p> |
|
56
|
|
|
57
|
<li>[G]it is <i>designed</i> to forget things. |
|
58
|
|
|
59
|
<p class="local-indent"> |
|
60
|
<i>[http://www.cs.cmu.edu/~davide/howto/git_lose.html] |
|
61
|
</p> |
|
62
|
|
|
63
|
<li>[I]n nearly 31 years of using a computer i have, in total, lost more data to git |
|
64
|
(while following the instructions!!!) than any other single piece of software. |
|
65
|
|
|
66
|
<p class="local-indent"> |
|
67
|
<i>Stephan Beal on the [http://www.mail-archive.com/[email protected]/msg17181.html|Fossil mailing list] |
|
68
|
2014-09-01.</i> |
|
69
|
</p> |
|
70
|
|
|
71
|
<li>If programmers _really_ wanted to help scientists, they'd build a version control |
|
72
|
system that was more usable than Git. |
|
73
|
|
|
74
|
<p class="local-indent"> |
|
75
|
<i>Tweet by Greg Wilson @gvwilson on 2015-02-22 17:47</i> |
|
76
|
</p> |
|
77
|
|
|
78
|
<li><img src='xkcd-git.gif' align='top'> |
|
79
|
|
|
80
|
<p class="local-indent"><i>Randall Munroe. [http://xkcd.com/1597/]</i><p> |
|
81
|
|
|
82
|
</ol> |
|
83
|
|
|
84
|
<h2>On The Usability Of Fossil</h2> |
|
85
|
|
|
86
|
<ol> |
|
87
|
<li value=11> |
|
88
|
Fossil mesmerizes me with simplicity especially after I struggled to |
|
89
|
get a bug-tracking system to work with mercurial. |
|
90
|
|
|
91
|
<p class="local-indent"> |
|
92
|
<i>rawjeev at [https://stackoverflow.com/a/2100469/142454]</i> |
|
93
|
</p> |
|
94
|
|
|
95
|
<li>Fossil is the best thing to happen |
|
96
|
to my development workflow this year, as I am pretty sure that using |
|
97
|
Git has resulted in the premature death of too many of my brain cells. |
|
98
|
I'm glad to be able to replace Git in every place that I possibly can |
|
99
|
with Fossil. |
|
100
|
|
|
101
|
<p class="local-indent"> |
|
102
|
<i>Joe Prostko at [http://www.mail-archive.com/[email protected]/msg16716.html] |
|
103
|
</p> |
|
104
|
|
|
105
|
<li>This is my favourite VCS. I can carry it on a USB. And it's a complete system, with it's own |
|
106
|
server, ticketing system, Wiki pages, and a very, very helpful timeline visualization. And |
|
107
|
the entire program in a single file! |
|
108
|
|
|
109
|
<p class="local-indent"> |
|
110
|
<i>thunderbong commenting on hacker news: [https://news.ycombinator.com/item?id=9131619]</i> |
|
111
|
</p> |
|
112
|
|
|
113
|
|
|
114
|
</ol> |
|
115
|
|
|
116
|
|
|
117
|
<h2>On Git Versus Fossil</h2> |
|
118
|
|
|
119
|
<ol> |
|
120
|
<li value=14> |
|
121
|
After prolonged exposure to fossil, i tend to get the jitters when I work with git... |
|
122
|
|
|
123
|
<p class="local-indent"> |
|
124
|
<i>sriku - at [https://news.ycombinator.com/item?id=16104427]</i> |
|
125
|
</p> |
|
126
|
|
|
127
|
|
|
128
|
<li> |
|
129
|
Just want to say thanks for fossil making my life easier.... |
|
130
|
Also <nowiki>[for]</nowiki> not having a misanthropic command line interface. |
|
131
|
|
|
132
|
<p class="local-indent"> |
|
133
|
<i>Joshua Paine at [http://www.mail-archive.com/[email protected]/msg02736.html]</i> |
|
134
|
</p> |
|
135
|
|
|
136
|
<li>We use it at a large university to manage code that small teams write. |
|
137
|
The runs everywhere, ease of installation and portability is something that |
|
138
|
seems to be a good fit with the environment we have (highly ditrobuted, |
|
139
|
sometimes very restrictive firewalls, OSX/Win/Linux). We are happy with it |
|
140
|
and teaching a Msc/Phd student (read complete novice) fossil has just |
|
141
|
been a smoother ride than Git was. |
|
142
|
|
|
143
|
<p class="local-indent"> |
|
144
|
<i>viablepanic at [https://www.reddit.com/r/programming/comments/bxcto/why_not_fossil_scm/c0p30b4?utm_source=share&utm_medium=web2x&context=3]</i> |
|
145
|
</p> |
|
146
|
|
|
147
|
<li>In the fossil community - and hence in fossil itself - development history |
|
148
|
is pretty much sacrosanct. The very name "fossil" was to chosen to |
|
149
|
reflect the unchanging nature of things in that history. |
|
150
|
<br><br> |
|
151
|
In git (or rather, the git community), the development history is part of |
|
152
|
the published aspect of the project, so it provides tools for rearranging |
|
153
|
that history so you can present what you "should" have done rather |
|
154
|
than what you actually did. |
|
155
|
|
|
156
|
<p class="local-indent"> |
|
157
|
<i>Mike Meyer on the Fossil mailing list, 2011-10-04</i> |
|
158
|
</p> |
|
159
|
|
|
160
|
<li>github is such a pale shadow of what fossil does. |
|
161
|
|
|
162
|
<p class="local-indent"> |
|
163
|
<i>dkf on the Tcl chatroom, 2013-12-06</i> |
|
164
|
</p> |
|
165
|
|
|
166
|
<li>[With fossil] I actually enjoy keeping track of source files again. |
|
167
|
|
|
168
|
<p class="local-indent"> |
|
169
|
<a href="https://wholesomedonut.prose.sh/using-fossil-not-git">https://wholesomedonut.prose.sh/using-fossil-not-git</a> |
|
170
|
</p> |
|
171
|
</ol> |
|
172
|
|