619
If "Master/Slave" terminology in computing sounds bad now, why not change it to "Dom/Sub"?
(lemmy.dbzer0.com)
this post was submitted on 20 Aug 2024
619 points (88.7% liked)
Showerthoughts
29665 readers
1438 users here now
A "Showerthought" is a simple term used to describe the thoughts that pop into your head while you're doing everyday things like taking a shower, driving, or just daydreaming. The best ones are thoughts that many people can relate to and they find something funny or interesting in regular stuff.
Rules
- All posts must be showerthoughts
- The entire showerthought must be in the title
- Avoid politics (NEW RULE as of 5 Nov 2024, trying it out)
- Posts must be original/unique
- Adhere to Lemmy's Code of Conduct
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Master can also mean proficiency. If you say you've mastered a trade it doesn't mean you enslaved the trade, you simply have complete knowledge of the trade.
So in that context, the master branch is the complete branch. The branch that other branches stem from because it's the one with code from all the teams. You could branch from another team member's branch but if that branch hasn't merged from master in a while, it won't have all the knowledge (code). When you merge in master you're getting knowledge from elsewhere from the branch that's aware of more things than your branch is: the branch that has mastery of the code, the master branch.
That's not how the terms entered computing though. We always used master in opposition of one or multiple slaves. It implies that one component has control and orders the other one around.
So in a git commit (since they mentioned branches)... What's the slave? Since your the one gatekeeping the word you should know right? How come Git can't be Master in the context they provided when there is no existence of a slave commit?
I'm not sure where you're going with this. I haven't gatekept anything, you can use whatever term you want, that's none of my business. You can happily read my other comment. To me, "master" makes no sense if there are no "slaves". That's why I don't use it. It doesn't make sense to use it. You do you, that's your business.
https://mastering.com/how-to-master-a-song/
To master something, has a number of meanings that don't require the use of "slaves".
https://www.merriam-webster.com/dictionary/master
Definitions most definitions of the word have nothing to do with slaves.
Edit: In this case, I believe that we all treat Git the same as this definition in specific...
So just because you only know of "master" in regards to "slaves"... that doesn't make you right.
Never said it made me right. Just didn't make sense to me. You can still use whatever you like, as I do.
And yet you said this... Acting like you speak for the entirety of industry, when I bring up one specific facet of our industry that isn't using the term juxtaposition to "slaves"... but rather to other concepts of "master", you now magically change your tune.
Look, I come from the hardware part of the industry and have never seen anyone talk about "master records" in software but always about master devices controlling slave devices. I'll give you that, apparently "master records" are a thing (although I'm curious in what part of the industry). At the same time, it seems so niche and weird to me that there's no point for me to use it. I'll stick with main because it just makes more sense and seems a lot more intuitive to people than to think about master records and what not. You do you, I personally absolutely do not care at all what you go with in your projects.