620
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 20 Aug 2024
620 points (88.7% liked)
Showerthoughts
30023 readers
439 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
- All posts must be showerthoughts
- The entire showerthought must be in the title
- 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.
- Posts must be original/unique
- Adhere to Lemmy's Code of Conduct
founded 2 years ago
MODERATORS
Not just that, it's bad and makes no sense in its technical context.
Server client is far better.
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.
Nowadays its more ofte used for server hierarchies/functionality. Or well, a lot of software is changing now. Mariadb use Source and replica.
You are correct I swapped client with other such as worker, child, and helper,
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.
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.
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.