Re: Consensus on a new default branch name

From: Oleg <lego_12239@rambler.ru>
Date: Jun 16, 2020, 17:11 UTC
Message-ID: <20200616171048.GA18874@legohost>
In-Reply-To: <20200616160005.GB667151@coredump.intra.peff.net>

On Tue, Jun 16, 2020 at 12:00:05PM -0400, Jeff King wrote:

Show 8 quoted lines

> On Tue, Jun 16, 2020 at 05:52:52PM +0300, Oleg wrote:
> > Jeff, where do you get your statistics? github, for example, have around
> > 100 million repos. How many of them want to do it?
> 
> Not statistics, but anecdotally, many major projects and communities
> have expressed interest in switching. Some of them are listed here:
> 
>   https://www.zdnet.com/article/github-to-replace-master-with-alternative-term-to-avoid-slavery-references/

This is not "many", Jeff :-D. There is info just about *few* major projects (i counted not more than *15*!), that also politically biased and are intimidated.

> I don't think 100 million is the right number to think about. Many of
> those aren't active, or aren't collaborative. A project like Chrome
> changing their branch name has a much bigger impact than somebody's
> homework repo with three commits.

Jeff, this is a discrimination ;-). And no. This isn't right. How many repos on github is inactive? May be 20 millions? Add to 80 millions gitlab and all another git repos from the world. I think we can easily collect around 150-200 million of active repos. Do you really think that count of developers of these all projects be less than count of Chrome developers? Why do 15 projects (politically biased) outweighs 200 millions of projects? Is this example of democracy or rationale mind? May be some there is corruption :-)?

> I was curious about some raw numbers, though, so I picked a random
> sample of ~25k GitHub repositories that had been pushed to in the last
> 30 days.  About 6% have a default branch name besides "master". There's

I think if you get repos from, for example, february instead of *last* 30 days, then you will get a yet little numbers. Because the last 21 days people are insane, if you understand me.

And even so - 6% :-D. Jeff, this is really needed thing! :-D This small numbers show just about one thing - this is useless feature. Of course, i talk about normal people. In any time, there are a few "not ordinary" persons and jokers.

> But it seems to me that with 6% non-master names, most tools are going
> to run into these cases sooner or later, and have to deal with it. I'd
> be much more worried about one-off scripts that see a small, non-uniform
> set of repositories.

Look, now this is a problem of rare "geniuses". Why do you want to bring these problems to all of us :-)? What did we do you?

> I think it's clear that this _is_ a politically-driven change. It is not
> helping the software in any technical way to change the name. The

Yes. You are absolutely right.

> question is whether the more abstract benefits to people are worth the
> potential costs.

Of course, not. This is obvious.

> But I don't think anybody has been able to quantify the benefits in a
> meaningful way. Or at least a way that everyone agrees on.

Jeff, everything is simpler. You lie to youself about it :-). *Everybody* adequate person will say you that there are *no* benefits at all. Only troubles, troubles and troubles. And we are already seeing this. There is no need for a time machine. This will helps nobody. This changes willn't materialize food for homeless and willn't protect someone from humiliation. But in current time, when people click "like" button instead of doing real things for others and think that they do "everything right" and this helps somebody :-), this is hard to understand. If you would find any slave which is offended by "master" word, then this conversation was meaningful. But now it looks like people who have never been masters appologize to people who have never been slaves. And are doing this, note please, in very strange manner.

Look, if you really try to make somebody life better, just image that you have no access to git code. How can you help? Search the better way that will really helps somebody. Don't break git. And after several monthes, when common sense will return to us, we will look again on this "useful" change.

-- 
Олег Неманов (Oleg Nemanov)