git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Philip Oakley <philipoakley@iee.email>
To: Filip Lipien <aaa@164.ooo>, Theodore Ts'o <tytso@mit.edu>
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: Sun, 1 Jan 2023 12:59:41 +0000	[thread overview]
Message-ID: <1cf19990-8989-83f5-3b2c-e1b1725509a3@iee.email> (raw)
In-Reply-To: <HJUKdhucsV1Ec9xNrCRNQLPylBS-oxmEZZzqT48oYfzyQ7hWXT5Kg3R4aF4JuI2FvVz9rjR1pysm7Xx53GRogtR1zNzDvRbRSu0P2ce876A=@164.ooo>

On 31/12/2022 23:23, Filip Lipien wrote:
>> 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].
> Please remain on the topic. Read my initial sentence again. What has "tagged" to do with related? And even if, the amount of 146,090 "tagged" questions is absolute madness. This is insane. Just look at the ratio in comparison to Python, a programming language. It is crazy to assume that this is fine and only proves my point. No, Git is not a complex programming language like Python, nor is it a Kernel API. It is supposed to be a user-facing tool made for humans.

The purpose of Git is to provide a Source Code Management system for
Linux. Linux development is *distributed*, and Linux is command line
orientated.

The need for a distributed SCM required a significant shift in mind set
compared to previous *control* systems that were historically based on
drawing and physical part management systems [1].
 
The ability to 'manufacture' duplicate copies of code, and then modify
them, at speed, makes those historical methods essentially impractical /
unworkable. Hence Git, with all it's foibles, has been widely adopted,
as control now lies with the user. Management can still be responsible
for 'authentication/designation' of specific revisions.

Git generally offers two world views, one that roughly matches the old
'change control' methods (diffs), and true 'local state' view. It is
easy to miss the subtle shift in world views.
>
> The fact is, that Junio C Hamano is doing a terrible job as a product manager. Because apparently, most users seem to have a problem with it. Why can this not be pointed out?

Junio is not a "product manager". He is not 'selling' to the wider user
base. He is maintaining a core element of the Linux ecosystem. I doubt
it's an easy job, balancing backward compatibility, future capability,
and broad usability, along with code quality, security and all the rest.

Learning Git is like learning Quantum Mechanics, it's just a few simple
rules, but the mind set shift is difficult. It has action at a distance,
and is amazingly effective.

In many ways it's the confusion between 'developer' facing, and 'user'
facing tooling. The nuances are different.

>
> ------- Original Message -------
> On Saturday, December 31st, 2022 at 8:19 PM, Theodore Ts'o <tytso@mit.edu> wrote:
>
>
>>
>> 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". 

In the beginning was Jacquard looms and Hollerith cards ;-)

>> 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 Stephenson - In the Beginning was the Command Line.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. :-)
--
Philip

[1] Mil Std 483, Def Stan 05-57, etc.

note, https://en.wikipedia.org/wiki/Configuration_management#Software
doesn't yet mention Git ;-)

  reply	other threads:[~2023-01-01 12:59 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
2022-12-31 23:23   ` Filip Lipien
2023-01-01 12:59     ` Philip Oakley [this message]
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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=1cf19990-8989-83f5-3b2c-e1b1725509a3@iee.email \
    --to=philipoakley@iee.email \
    --cc=aaa@164.ooo \
    --cc=git@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).