Update to Git changes the default of init.defaultBranch to main

Re:Update to Git changes the default of init.defaultBranch t... by bluntfang on Wednesday November 18, 2020 @11:30AM (#25138718)

I feel like complaining about a disagreement in direction of an open source project while not wanting to put effort in directing it in the way you like via the normal channels, forking or contribution, to be immature.

[ Parent | on HN ]

Re:Update to Git changes the default of init.defaultBranch t... by revnode on Wednesday November 18, 2020 @11:54AM (#25139094)

I feel like demanding contribution as a response to criticism of open source software is immature. Just because you decided to let everyone see and use your code, doesn't mean someone can't say something negative about it. That is not some sort of privilege reserved for contributors.

[ Parent | on HN ]

Re:Update to Git changes the default of init.defaultBranch t... by aaomidi on Wednesday November 18, 2020 @01:10PM (#25140139)

So what are the downsides of git changing this?

How is this going to impact your day to day work flow?

[ Parent | on HN ]

Re:Update to Git changes the default of init.defaultBranch t... by RhysU on Wednesday November 18, 2020 @02:46PM (#25141510)

"Lemme go run main" is now ambiguous. The main entry point? Or the main branch?

[ Parent | on HN ]

Re:Update to Git changes the default of init.defaultBranch t... by bluntfang on Wednesday November 18, 2020 @12:57PM (#25139983)

>Just because you decided to let everyone see and use your code, doesn't mean someone can't say something negative about it. That is not some sort of privilege reserved for contributors.

Of course not. It's just extremely immature when there are direct ways via work and effort (forking or contributing) to gain social capital in the community to influence change and direction.

[ Parent | on HN ]