Showerthoughts

29244 readers

557 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
Posts must be original/unique
Be good to others - no bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia
Adhere to Lemmy's Code of Conduct

founded 1 year ago

MODERATORS

[email protected]

620

If "Master/Slave" terminology in computing sounds bad now, why not change it to "Dom/Sub"? (lemmy.dbzer0.com)

submitted 1 month ago by [email protected] to c/[email protected]

462 comments fedilink hide all child comments

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

[–] [email protected] 3 points 1 month 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 1 month 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.

[–] [email protected] 3 points 1 month ago

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

[–] [email protected] 2 points 1 month ago* (last edited 1 month 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 1 month 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 1 month 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.