Hello PCMR community!
On July 13th, we asked the community for your opinion if you would like to change the name of this community.
Results of the Survey :
- Yes - 28.1%
- No - 71.9% (winner)
Of the 1,201 responses received, we as a community have democratically decided that we should not change the name from PC Master Race. I am grateful to our community for your input, as this was a difficult topic to navigate together.
If you would like to review the history of this, please check out this post here: https://lemmy.world/post/1430610
We'll pin this post for some time and then consider adding a bullet into the sidebar for this Community to help stave off further discussions around this topic as the community has already decided collectively.
Kind regards,
The Moderator Team
@[email protected] @[email protected] @[email protected] @[email protected] @[email protected] @[email protected] @[email protected] @[email protected] @[email protected] @[email protected]
EDIT 30-Aug-2023:
Due to some of the recent targeted attacks against Lemmy.world, I noticed that the image I shared with this post was purged from their servers.
Here's a new screenshot of the results for posterity: https://i.postimg.cc/jqNg5gWx/pcmrsurvey.png
The concept of a master branch reaches back to CVS (that's Concurrent Version System, not a pharmacy), and Subversion. Makes sense it wouldn't make sense to you. Frankly it doesn't make sense to
gitat all, but that's a much larger discussion.The concept of a "master copy" has been around and in widespread use for around a century. It has nothing to do with either software nor social (in)justice. It's just the thing you photocopy so you don't end up making photocopies of photocopies. IMO It should make sense to anyone who, you know, has seen and used paper within their lifespan.
Some terminology, like "master and slave" for IO between devices, did always used to make me really uncomfortable whenever I heard it. But the branch name for software was probably fine.
Yeah, LP records have master copy and those have been around for some time (before going away and coming back again)
More than a century
Ever since Hammurabi
It's been a long time since I've used SVN by aren't things like branching more difficult? I guess for personal it doesn't matter.
Not really. If memory serves it's just
svn checkout branch_nameI have never used Git professionally but I'll tell you the three biggest pain points when working with SVN that I know Git has proper solutions.
No local commits. On the latest SVN versions there is the concept of "shelves" which just basically puts your changes in a separate folder... as of last I checked it was still in Beta but it works decently.
Common code is a pain in SVN. The only way you can do this is using the externals property which has annoyances that seem to be handled better by Git Subtrees.
Commit squashing doesn't exist in SVN. Not a problem for me personally but I've worked with some people that make me really wish I could squash their commits.
Git is really inefficient for large binary files because of the decentralization. SVN for media and Git for text-based files makes sense. Otherwise— I only used SVN briefly, and then fortunately only for media— But yeah, Git is probably better and more useful overall.
I wouldn't want to go back to svn. I've gotten very used to git's ability to carve up changes, etc.