Re:The Go Language was rid of blacklist/whitelist and master...
by codegladiator on Sunday June 07, 2020 @07:08AM
(#23446506)
The leader/follower for master/slave seems pretty clear, similarly for blocklist/allowlist. Your argument seems to be 'because we have been doing it like this' or 'has been used in so many places' which I don't agree with too much as a reason to keep using it.
This change seems to actually bring in better terms and clearly understandable.
Re:The Go Language was rid of blacklist/whitelist and master...
by rfoo on Sunday June 07, 2020 @07:12AM
(#23446540)
Sorry, but if you actually click into the link before arguing with me, you would see they replaced "master" and "slave" in pseudoterminal context with "tty" and "processTty", not leader/follower because their relationship are really not leader and follower.
https://go-review.googlesource.com/c/go/+/236857/5/src/os/si...
Re:The Go Language was rid of blacklist/whitelist and master...
by codegladiator on Sunday June 07, 2020 @07:17AM
(#23446561)
Fair enough. I did check the link but didn't see that one.
Master/Slave demonstrate this better. For example, in the context of pseudoterminals, primary/secondary is certainly not precise words to use, it is quite hard to come up with "obvious" words without re-educating everyone. (oh, and it's baked in the API name in various specifications, like "ptsname" => "pseudo terminal slave name")