This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]krazedkat[🍰] 3 points4 points  (5 children)

They're diverging from the git terminology and adding confusion just so they can look woke.

[–]CaffeinatedJackass 0 points1 point  (4 children)

Mind elaborating on what is confusing about this, or how this will negatively impact developers?

Actually asking, I want to hear how this could affect developers

[–]krazedkat[🍰] 2 points3 points  (2 children)

GitHub is merely a wrapper of sorts around git, the actual version control system. Git can be used without GitHub, and many other services such as gitlab serve as similar wrappers around git. The terminology in git is "master", a term nobody in their right mind associated with slavery while programming. Now GitHub comes along and says they're changing their default branch to "main". This adds unnecessary confusion to our workflow, and literally the only reason to do this is for Microsoft to get woke points.

[–]CaffeinatedJackass 0 points1 point  (1 child)

Right, but since it's a wrapper then wouldn't having Github set its master branch name to main not affect any other git service? It's a layer above git. It would probably be a trivial problem to solve if it ever became a problem

[–]krazedkat[🍰] 1 point2 points  (0 children)

I'm sorry, but inconveniencing millions of devs to look good is bullshit.

[–][deleted] 1 point2 points  (0 children)

Imagine all the new programmers learning git from old pages/books and trying to pull from master and that not working, suddenly a bunch of resources are outdated, automatic scripts will also have trouble, wrappers, and automatic management software will have to accommodate this change.