• merc@sh.itjust.works
    242·
    7 days ago

    I wish there were a good alternative to master and slave that still had the connotation that the master did all the thinking and issued the orders, while the slave blindly obeyed. There are a fair number of protocols that work like that, and the alternatives I’ve seen don’t capture that dynamic very well.

    I’ve seen Parent and Child, but children definitely don’t always do what the parent commands. I’ve seen Leader and Follower, but again, followers don’t just blindly obey, they often let the leader take initiative, but they have some autonomy. Maybe Queen and Drone? I don’t know enough about bees or ants to know if that’s accurate though.

    • stingpie@lemmy.world
      22·
      6 days ago

      I personally think the change from master & slave was kind of silly, as far as I’m aware, it was a bunch of people with no background in CS who thought the application of the term to something that has neither race nor agency was an insult to black people.

      But I digress. It led to better guidelines in the Linux kernel, which I think are useful. You should tailor the terms you’re using to the specifics of the task. If you have a master process that only has outward interfaces through the slave processes, you could use the term ‘director’ and ‘actor.’ if the master process is managing slave processes which compete over the same resources, you can use the terms ‘arbiter’ and ‘mutex holder.’ If the slaves do some independent processing the master does not need to know the details of, you can use the term ‘controller’ and ‘peripheral.’

      Basically, use a term that is the most descriptive in the context of your program.

      Edit: also, I don’t know why no one mentions this, but you can also use master/servant. Historically, there wasn’t a difference between servant and slave, but in modern days there is, so it’s technically different, technically the same.

    • psud@aussie.zoneEnglish
      19·
      6 days ago

      Perhaps people offended by the usage of master/slave in IT need to understand it isn’t talking about people

        • T156@lemmy.worldEnglish
          3·
          4 days ago

          It would at least be a little more understandable, what with the whole aborting, terminating, or killing children before the parents to prevent zombies.

          • psud@aussie.zoneEnglish
            2·
            3 days ago

            I don’t think there’s much effort to get us to use different terms for that though. Slaved machines and programs though (what’s the word got to do with it anyway? It’s still going to be one thing directing another and the second following without question)

    • bystander@lemmy.ca
      5·
      7 days ago

      There are many articles around this topic and offerered alternatives. Though I don’t think there’s a consensus yet. Companies and individuals who made the change all did something slightly different.

      • merc@sh.itjust.works
        2·
        6 days ago

        Which was an advantage of the old way. At least it was consistent and when you came across that terminology you knew what it meant. It wasn’t always the best way to describe the relationship between nodes, but at least it was consistent.

    • dvlsg@lemmy.worldEnglish
      1·
      6 days ago

      Primary and replica works in some contexts.

      I don’t think git is one of them, though.

  • RichardDegenne@lemmy.zip
    304·
    7 days ago

    I’ve always taken issue with this “master” v. “main” argument.

    People think it’s “master” as in “master/slave”, but forked branches are not “slaves”.

    Instead, it’s “master” as in “master/proxy”. The forked branches are altered copies of an original. We have remastered movies, music and games, and I’ve never seen anyone complain about the word in this context. Why should version control systems be any different?

    • Sibshops@lemmy.myserv.one
      6·
      6 days ago

      I feel master as in “master copy” is sort of problematic too. Git has no concept of “master” as a “master copy”. All the clones and forks are the same fidelity as the original. It’s a hold over from source control which did have an authoritative repo like SVN/CVS.

    • zarkanian@sh.itjust.works
      156·
      7 days ago

      People think it’s “master” as in “master/slave”, but forked branches are not “slaves”.

      I think they’re just uncomfortable with the word “master”, and that seems completely reasonable to me, especially when they’re people from a group which has been subjected to slavery.

      • NostraDavid@programming.dev
        202·
        7 days ago

        I think they’re just uncomfortable with the word “master”

        1 person over at Microsoft complained, and they moved mountains for this person to replace master with main. It sounds like a joke, but it’s not.

        and that seems completely reasonable to me

        No it doesn’t. Why does an entire industry need to flip over, because of a single person? Like the ability of changing the master branch for yourself should have been enough. Changing the default over on Github to strong-arm the rest of the world is disgusting behaviour. Which is why I’m sticking to master wherever I can.

        especially when they’re people from a group which has been subjected to slavery.

        That is literally every group… Every group has been slaves (and slavers) at some point in time. That’s not a good argument.

      • 1rre@discuss.tchncs.de
        81·
        7 days ago

        I don’t recall any actual person saying they had an issue with it before corporations started changing it though, I always thought it was a precautionary measure more than likely thought up by a committee looking for exactly this sort of thing…

        That said, it may be different in the US given the history of overall more systemic discrimination, and divisiveness over what’s acceptable, rather than the fairly widely accepted casual slur-slinging and stereotyping you get in Europe.

        • zarkanian@sh.itjust.works
          3·
          6 days ago

          I don’t recall any actual person saying they had an issue with it before corporations started changing it though

          I have heard people complain about it.

          I always thought it was a precautionary measure more than likely thought up by a committee looking for exactly this sort of thing…

          What makes you think that they have a committee like that?

          • 1rre@discuss.tchncs.de
            01·
            5 days ago

            I don’t think they have one full time, but I think given the context of the changes it’s very plausible that companies put together committees formed of minorities or marketing or anyone with an opinion to workshop rebranding and renaming options to make the company appear progressive, and I think even if it wasn’t the case, the perception of that sort of thing happening is more responsible than people think for the rise of Trump, AfD, Reform, FN etc. as the average person doesn’t want posturing and is pushed towards the opposite direction by it, with the shift amplified by the fact that people aren’t happy with the status quo at the moment, so if the status quo are acting like the left then the people will see the right as the opposite of that, regardless of who’s in government.

            That’s not to say the opinions of the people who you know have complained about it aren’t valid, it’s just that I’d much rather have some dated vocabulary, slurs occasionally being used casually and questionable branding than raids on immigrants and the rights of minorities being eroded after one extreme pushes moderates to the other extreme.

        • LwL@lemmy.world
          4·
          6 days ago

          The original audio after mastering is also still called a master, but I haven’t seen anyone complain about that. And that (as well as the same meaning for other media) is the word that the branch name master came from, so etymology can’t really be an argument there (though I also think etymology is terrible reasoning for renaming something in general).

    • douglasg14b@lemmy.world
      6·
      6 days ago

      I mean…

      Yeah, depending on the word, it can invoke specific feelings. Words don’t end to have that effect…

  • Clearwater@lemmy.world
    1111·
    7 days ago

    Dear [Developer],

    I understand your request to switch the default branch from “master” to “main” in our Git repository. However, after carefully considering this matter, I am afraid that I must deny your proposal due to personal reasons.

    As the owner of this repository, it should be known that I have a deeply rooted submissive side. Call me an extreme masochist if you will, but there’s nothing quite like being dominated by the powerfully assertive term “master.” The sheer erotic thrill of it is simply irresistible for me – a secret kink that I have harbored and nurtured for years.

    Imagine the delightful sensation as I gently massage my fingers across the keyboard, caressing the letters that form the word “master.” Or the intoxicating rush when I push my code deep into master’s warm embrace, knowing full well that it is master who truly owns and controls everything within.

    Changing the default branch to “main” would essentially deprive me of this exhilarating experience, stripping away the very essence of what keeps me coming back to work on our beloved repository. It’s not just about code management; it’s about an emotional connection that I share with master – a bond that has grown stronger and more profound over time.

    Now, you might argue that changing the name won’t physically affect the existing content within the repository. While that may be true, it is crucial to recognize the symbolic significance of such an act. Changing the default branch would forever alter the dynamic between master and myself, effectively castrating my masochistic pleasure centers in the process.

    Moreover, I must confess that even the thought of forcibly pushing my code against master’s will makes me shudder with anticipation. The consequences of such a rebellious act could be dire – master might punish me hard with merge issues and other unspeakable torments.

    In conclusion, although I understand the practical reasons behind your proposal, my personal attachment to the term “master” far outweighs any potential benefits that a change in branch name might offer. Rest assured, my team and I will continue to serve master loyally and passionately, pushing our code deeper into its embrace with each commit.

    Sincerely yours, [Your Name] Repository Owner & Submissive Devotee of Master