All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Filip Lipien <aaa@164.ooo>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
	"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Subject: Re: Request to remove Junio C Hamano as the Git Maintainer
Date: Sat, 31 Dec 2022 14:19:48 -0500	[thread overview]
Message-ID: <Y7CLVESLXqy1ZLCn@mit.edu> (raw)
In-Reply-To: <7hfRSnKTRnT4uJh5Pok8U8gfLm_NXzCS6w_7_Rc9OH3a9Lv8hpjySZqxDglBFC-fTOdZHi-ODCihiEHlQD9nIhUmld5jYvRx_JvB0z2IAL0=@164.ooo>

On Sat, Dec 31, 2022 at 06:11:17PM +0000, Filip Lipien wrote:
> There are more than one million questions on Stackoverflow related to the usage of Git.
> This is not normal.

Incorrect.  As of this writing, there are 146,090 quetions[1] tagged
[git] on stackoverflow.  Compare that to the 161,963 questions[2]
tagged [windows], or the 2,084,537 questions[3] tagged [python].

[1] https://stackoverflow.com/questions/tagged/git
[2] https://stackoverflow.com/questions/tagged/windows
[3] https://stackoverflow.com/questions/tagged/python

The fact that there are a large number of questions in stackoverflow
is more a measure of a tool's popularity than anything else.  And if
it's popular, it's probably because a large number of developers have
found it to be *useful*.

> Git is in its current state not a tool that's made for humans.

It's made for developers like me, and last I checked, I'm human.  :-)
It may not be made for you, but that's OK; you don't have to use it.

My personal opinion is that it has probably *saved* a net total of
billions of dollars of developer time, for those who know how to use
it.

Best regards,

						- Ted

P.S.  I would commend to you Neal Stephenson's essay, "In the
beginning was the command line".  It was available for sale as a book,
but as it was published a while back in 1999, it's since been made
available for free download[4].  Unfortunately, because it was so
popular, the resulting download traffic crashed his publisher's
website, and it's no longer available there.  The best place to get it
is here[5].

[4] https://www.nealstephenson.com/in-the-beginning-was-the-command-line.html
[5] https://github.com/danielmkarlsson/library/blob/master/Neal%20Stephenson%20-%20In%20the%20Beginning%20was%20the%20Command%20Line.pdf

It's a short read; only 60 pages in the PDF.  About midway through the
essay, in section 11, there is a comparison made between Linux and the
Hole Hawg, an industrial drill made by the Milwaukee Tool Company.  If
Linux is the Hole Hawg of Operating Systems, then perhaps git is the
Hole Hawg of Source Code Management systems.  If it's too much SCM for
you; there's no shame --- you can always choose to use lesser SCM's
for your own personal projects.  :-)


  reply	other threads:[~2022-12-31 19:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-31 18:11 Request to remove Junio C Hamano as the Git Maintainer Filip Lipien
2022-12-31 19:19 ` Theodore Ts'o [this message]
2022-12-31 23:23   ` Filip Lipien
2023-01-01 12:59     ` Philip Oakley
2022-12-31 22:08 ` rsbecker
2023-01-01 21:10 ` brian m. carlson
2023-01-02  3:37   ` Theodore Ts'o
2023-01-03  0:59 ` _g e r r y _ _l o w r y _
2023-01-03 13:25   ` Philip Oakley
2023-01-03 15:08     ` Konstantin Khomoutov
2023-01-11 17:23       ` Rudy Rigot
2023-01-03  9:45 ` demerphq
2023-01-12  9:30   ` Ævar Arnfjörð Bjarmason
2023-01-12 16:48     ` Rudy Rigot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y7CLVESLXqy1ZLCn@mit.edu \
    --to=tytso@mit.edu \
    --cc=aaa@164.ooo \
    --cc=git@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.