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

  • @[email protected]
    link
    fedilink
    184 months ago

    No, that’s completely dependent on what you are referring too. I have never heard anyone ever referring to a server as “master” or a client as a “slave”. The slave/master terminology is often used for storage. I.E. Master drive and slave drive.

    • @[email protected]
      link
      fedilink
      3
      edit-2
      4 months ago

      You are correct I swapped client with other such as worker, child, and helper,

      Master–slave (technology)

      In 2018, after a heated debate, developers of Python replaced the term. Python switched to main, parent, and server; and worker, child, and helper, depending on context.

      The Linux kernel adopted a similar policy to use more specific terms in new code and documentation.

      My problem with the term “slave” is that it does not indicate there is a delegation of work going, on but rather that the subdevice is somehow fully “owned” by the master device. Whereas in reality the master is more like a manager telling a worker what to do.

      • @[email protected]
        link
        fedilink
        14 months ago

        In some cases the sub device is pretty much owned by the “master” device.

        I’m mostly thinking of IDE since that’s the only place I ever hear anyone use master/slave except GIT where master is used.

    • @[email protected]
      link
      fedilink
      34 months ago

      Nowadays its more ofte used for server hierarchies/functionality. Or well, a lot of software is changing now. Mariadb use Source and replica.