this post was submitted on 20 Aug 2024
620 points (88.8% liked)

Showerthoughts

29792 readers
326 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. A showerthought should offer a unique perspective on an ordinary part of life.

Rules

  1. All posts must be showerthoughts
  2. The entire showerthought must be in the title
  3. Avoid politics
    • 3.1) NEW RULE as of 5 Nov 2024, trying it out
    • 3.2) Political posts often end up being circle jerks (not offering unique perspective) or enflaming (too much work for mods).
    • 3.3) Try c/politicaldiscussion, volunteer as a mod here, or start your own community.
  4. Posts must be original/unique
  5. Adhere to Lemmy's Code of Conduct

founded 1 year ago
MODERATORS
 

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

you are viewing a single comment's thread
view the rest of the comments
[–] Linkerbaan 3 points 3 months ago (2 children)

Not just that, it's bad and makes no sense in its technical context.

Server client is far better.

[–] [email protected] 16 points 3 months ago (2 children)

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.

[–] nemno 3 points 3 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.

[–] Linkerbaan 2 points 3 months ago* (last edited 3 months ago) (1 children)

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] 1 points 3 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] 1 points 3 months ago

that's because the server is rarely the master, the clients do work, and the server just exchanges the work of the clients, it's a lot more akin to a telephone exchange as opposed to a master/slave architecture.