4 ms·
I mean, this is true. But traits are also very useful. Feels a bit like saying "driving is dangerous; avoid driving where possible". Also "allow-list" is so gr
by IshKebab 3y ago
I mean, this is true. But traits are also very useful. Feels a bit like saying "driving is dangerous; avoid driving where possible".
Also "allow-list" is so gross. Maybe pick something less divisive for future examples.
- nmjohn 3y ago> Also "allow-list" is so gross. Maybe pick something less divisive for future examples. What is gross or divisive about that?
- twic 3y agoI'm guessing this is a reference to the movement by some people to use that term instead of "whitelist" on the grounds that the latter is racist. There's a division over whether this is silly or not.
- fargle 3y agothe entire idea of having a "allow" list is itself exclusionary and divisive. why are some clients allowed and some are not? </sarc>
- IshKebab 3y agoLots of people (including me) think it sounds extremely stupid and "whitelist" was perfectly fine anyway. Reminds me of "mebi-byte", which is similarly gross (but at least that had sensible motivation).
- deredede 3y agoLots of people think whitelist is not fine, and decide to use another term whose meaning is perfectly clear and understandable. You don't like that term, but what would you have people use that's less divisive? Clearly "whitelist" does not work, since it was the initial source of the issues.
- IshKebab 3y agoThe example in this article could have been any kind of list.
- zzo38computer 3y agoI agree with you, "whitelist" is a perfectly fine word, and "allow-list" doesn't sound good. I also agree that "mebi-byte" doesn't sound good either, but yes, at least it is sensible. However, just because a word is OK does not mean it is applicable to all contexts. You can call the list "AllowedClients" or something else like that instead, which explains what is being allowed (since there might be multiple kinds of restrictions that you might wish to define based on lists). (Of course, this is a whitelist mode, and can be described as such.) However, if the program already exists, then changing the name of the setting would be even worse (unless the old name is still available as an alias, but you must be careful to ensure you do not mess up anything by doing so), since that would just break compatibility (you can change the documentation though if the existing documentation is unclear). Also, in some contexts a word can be confusing and a different word is preferable. For example, if the list has something to do with colours, then using the terms "whitelist" and "blacklist" might be confusing and perhaps should not be used. Likewise, singular "they" is OK, but if singular they is confusing in that context then you should use different words instead. Still, if some people do not like "whitelist", you do not have to use it, but you should consider what words to use which are appropriate and descriptive. Fortunately, sometimes they do, but unfortunately sometimes they don't because their only consideration is to be not racist, instead of to actually be good. I also do not like the word "tonne"; I prefer "megagram" (which is more descriptive, just as easy to understand, and not confused with "ton").
- zzo38computer 3y ago> I mean, this is true. But traits are also very useful. Feels a bit like saying "driving is dangerous; avoid driving where possible". I agree. Just because it can be misused does not mean it is no good for anything. Note that you can declare types explicitly, and is usually how I do when I write anything in Haskell anyways, which makes the program clearer. Also, changing the types after the rest of the program is already written, is going to be a problem in any programming language even without ad-hoc polymorphism, if you do not then consider everything that needs to be changed due to that. > Also "allow-list" is so gross. Maybe pick something less divisive for future examples. I agree with this, too. You can call it "allowed clients" or "list of allowed clients" if you want to, which is better in my opinion. (Simply "allow-list" does not even describe very well what it is for; what is being allowed?)
- tome 3y agoLists of "Allow" and "Deny" have been around a long time, for example in Apache for probably nearly 30 years. https://httpd.apache.org/docs/2.4/mod/mod_access_compat.html#allow https://httpd.apache.org/docs/2.4/mod/mod_access_compat.html...
- IshKebab 3y agoI don't see "allow-list" or "deny-list" anywhere there?
- deleted 3y ago[deleted]