>
> In this word developers said "We 100% support BLM, we against any racism.
> Some of community members have sent proposal for renaming blacklist, but we
> 100% sure, that this term has nothing to do with racism. Moreover, terms
> can't explain things 100% clear, we just use those terms to
I'm sorry for my bad English
On Monday, June 22, 2020 at 4:40:07 PM UTC+3, John Obelenus wrote:
>
> Alex I find the notion that you think changing terms that have bad racial
> connotations to be "embarrassing" to be entirely without merit. It is not
> embarrassing to consider the feelings of
The point about the arithmetic semantics is a good one. I'm curious to
know how often this is actually a problem. I think it will happen
strictly less frequently than the localize case, which /is/ handled in
both a backwards and forward-compatible way, and I hate to throw the
baby out with the
Alex I find the notion that you think changing terms that have bad racial
connotations to be "embarrassing" to be entirely without merit. It is not
embarrassing to consider the feelings of Black and other minority people
when using language. Moreover, racism is not simply a US only phenomenon.
Daryl,
I've never called anyone egocentric here, maybe thinking in a very
short-term - yes (like a person, who is making decision just by current
needs and not thinking about future at all)
> With regard to the current "hot" topics (master/slave and blacklist /
deny), these may be viewed as
