It sounds way less offensive to those who decry the original terminology’s problematic roots but still keeps its meaning intact.

  • Fades@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    7 months ago

    No it doesn’t sound bad, words don’t need to be thrown away forever just because they’ve been used to describe unfair treatment. I’m so sick of having to relabel so many things that are so far divorced from the social issues they are used to describe. It’s so pointless and has no impact, the code doesn’t care which is master and which is the slave for they are simply descriptive labels.

    Are we supposed to never use the words master or slave ever again?? What’s next?

    My dev friends, no matter their race, all say the exact same thing. We still use master over main, come at us I guess.

      • yogsototh@programming.dev
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        7 months ago

        I work for s company that suddenly asked to rename a lot of stuff. This had consequences. It cost time, money, and created a disconnect between internal to the dev vocabulary that couldn’t be changed easily and user facing vocabulary. Also we were lucky but this could gave broken some long used API that we are proud not to version because the policy we have internally is “we will NEVER break the API”. And so far, for 8 years we still haven’t.