Originally posted by skeevy420
Announcement
Collapse
No announcement yet.
LLVM Developers Plotting Path Forward For Moving To A New Git Branch Name
Collapse
X
-
Last edited by illwieckz; 19 June 2020, 09:22 PM.
- Likes 7
-
Originally posted by hughw View PostDon’t you see that the whole aim of Newspeak is to narrow the range of thought? In the end we shall make thoughtcrime literally impossible, because there will be no words in which to express it.
- Likes 6
Comment
-
Is there any references to 'slave' in git terminology? (I honestly don't know). If there is, then I think it reasonable to consider 'master' a problematic (even if not necessarily racist) term. If not, than I can't in any good faith have an issue with its usage in the context. (Just as, to use an example above, "Dungeon Master" could really only be an issue if the players are called "Dungeon Slaves", which they aren't!).
The whole Master-Slave=Racism thing is rather ex-colonial-centric, too, but since we are predominately talking about it in the context of ex-colonial languages like English, that doesn't necessarily invalidate the pro-change argument.
OTOH, irrespective of etymology, I like allow/deny-list over black/white-list simply on the grounds of clarity of meaning sans cultural context.Last edited by Viki Ai; 19 June 2020, 09:25 PM.
- Likes 7
Comment
-
Originally posted by elldekaa View PostOn the contrary, whitelist/blacklist terms seem to have everything to do with racism: http://jmla.pitt.edu/ojs/jmla/article/view/490
Good initiative from LLVM community
Such terminology not only reflects racist culture, but also serves to reinforce, legitimize, and perpetuate it. On this issue, it instructive to read comments by Ossie Davis on the use of English as a racial affront:[…]
And wait… how this have to do in a medical library? This has all the aspects of a scam, the recent The Lancet fiasco must have warned you…Last edited by illwieckz; 19 June 2020, 10:47 PM.
- Likes 7
Comment
-
LLVM developers really don't have more important problems to solve than a branch name, because some idiot said that this name is related to racism? It's just a word, without a context there is nothing wrong with any word and in this case we don't have any context related to racism, so what a problem? In near future some color names will be banned because they describe our skin color... What a world...Last edited by nadro; 19 June 2020, 10:27 PM.
- Likes 4
Comment
-
Originally posted by Viki Ai View PostIs there any references to 'slave' in git terminology? (I honestly don't know). If there is, then I think it reasonable to consider 'master' a problematic (even if not necessarily racist) term. If not, than I can't in any good faith have an issue with its usage in the context. (Just as, to use an example above, "Dungeon Master" could really only be an issue if the players are called "Dungeon Slaves", which they aren't!).
The whole Master-Slave=Racism thing is rather ex-colonial-centric, too, but since we are predominately talking about it in the context of ex-colonial languages like English, that doesn't necessarily invalidate the pro-change argument.
OTOH, irrespective of etymology, I like allow/deny-list over black/white-list simply on the grounds of clarity of meaning sans cultural context.
You've been playing it wrong if you don't have a safe word and Dungeon Slaves
- Likes 3
Comment
-
Originally posted by skeevy420 View Post
Your last sentence is basically my stance on the matter. Master, blacklist, and whitelist are all Euro-American terms, regardless of which part of the culture and history we're trying to attribute the meaning towards, so changing Master to Main, blacklist to denylist, and whitelist to allowlist makes sense in regards to clarity and meaning since we'd be replacing cultural terms with actual descriptive terms. I doubt very many of us would disagree to terminology changes based on that line of thinking.
The next step in that direction would be to make localizable programming language keywords, such as "if", "while", "for"... Just because they are in English and discriminate non-English speakers. This happens in Excel formulas, by the way. Variables should be allowed to contain any Unicode character, as happens in python3 if I remember correctly.
Try programming using French, Spanish or any second language you have a basic knowledge of, and you will feel how many non-native English speakers feel when they start to program.
International communication would be much harder. Code would be harder to share. The cons outweigh the benefits, in my opinion. And then, since we are choosing to stick to English, I don't think it makes sense to drop white-light-good black-dark-bad semantics because they are Euro-American, it's just a detail, and very minor in comparison to learning the basics of a whole language.
- Likes 5
Comment
Comment