| 1 |
Hello, Rich. |
| 2 |
|
| 3 |
On Fri, Aug 28, 2015 at 01:41:05PM -0400, Rich Freeman wrote: |
| 4 |
> On Fri, Aug 28, 2015 at 11:26 AM, Alan Mackenzie <acm@×××.de> wrote: |
| 5 |
|
| 6 |
> > I disagree completely. A little time spent on git is time wasted. Only |
| 7 |
> > a lot of time spent on git is useful. |
| 8 |
|
| 9 |
> I disagree with this. |
| 10 |
|
| 11 |
> > git is to VCSs as assembler is to programming languages. To use either |
| 12 |
> > effectively, you've got to have a complete grasp of the internal logic of |
| 13 |
> > git/the processor. |
| 14 |
|
| 15 |
> I agree with this. |
| 16 |
|
| 17 |
> > the collected man pages of git (collected into an info file) |
| 18 |
> > weigh in at 1.9 Mb. |
| 19 |
|
| 20 |
> And if you read them all 12 times it probably wouldn't help you out |
| 21 |
> with using git one bit. I haven't read most of it, and I'd say that I |
| 22 |
> grok it. |
| 23 |
|
| 24 |
> You really need to take time to understand how git works, and that |
| 25 |
> doesn't actually take that much time. |
| 26 |
|
| 27 |
I've spent many tens of hours in the last year trying to get to grips |
| 28 |
with git, ever since a project I work on (Emacs) converted to using git. |
| 29 |
|
| 30 |
There are all sorts of stupidities in it - like `push' and `pull' not |
| 31 |
being opposites, `clone' not producing a clone, but a new repository |
| 32 |
radically different from the original. Unnecessary arcane teminology, |
| 33 |
and standard terminology perversely used to mean something different. |
| 34 |
|
| 35 |
When everything works just fine, according to the book, I now have few |
| 36 |
problems. But when something goes wrong - like merge conflicts, for |
| 37 |
example, I end up spending, perhaps, two hours searching the doc for an |
| 38 |
answer then end up asking for help on the project mailing list. With |
| 39 |
the same problems in, say, hg or cvs, the answers would be clear within |
| 40 |
a few minutes of opening the doc. |
| 41 |
|
| 42 |
> The man pages are mainly used to figure out what Linus named the |
| 43 |
> command line option you're looking for when he was drunk and creating |
| 44 |
> a new subcommand. Git has a beautiful design and a horrible |
| 45 |
> interface. |
| 46 |
|
| 47 |
I can accept that. |
| 48 |
|
| 49 |
> If you understand the design you'll know that there must be a way to |
| 50 |
> do something, but you'll spend 15min figuring out which command line |
| 51 |
> utility does it best. |
| 52 |
|
| 53 |
I don't want to have to understand the design. I just want to be a |
| 54 |
user. I've got enough things competing for limited mental capacity as |
| 55 |
it is. |
| 56 |
|
| 57 |
> -- |
| 58 |
> Rich |
| 59 |
|
| 60 |
-- |
| 61 |
Alan Mackenzie (Nuremberg, Germany). |
Archives