Or ya know, not making someone’s disability the leading term you use to describe someone. That what’s most important is their personhood and they’re not defined by some single dominant aspect. And that their disability isn’t part of their identity but is just a fact about them.
Language doesn’t do multiple inheritance well so has-a descriptions are easier to work recognizing that people are multifaceted.
I'm sure it depends on the person and the disability, but I'm diabetic and would much rather be referred to as that rather than "a person with diabetes". That's just exhausting.
Diabetes itself is awful. Whether or not it's the leading descriptor makes no difference with that, and I'd rather just use the non awkward terminology ("I'm diabetic" rather than "I'm a person with diabetes".) It would feel almost patronizing if everyone started referring to me that way.
Furthermore, for all that people apparently care about the accumulated effects of microaggressions... Suppose that, every time someone refers to your group—I'll use blindness for an example—they think "blind people—oh wait, I'd get in trouble for saying that, um, I mean, people who are blind". Might this develop a Pavlovian association of "blind people" = "uh-oh, might get in trouble"? Which, in turn, might lead to subtle resentment, mistreatment, and/or avoidance of blind people? It seems that, to rationally recommend one moniker over the other, one has to consider all the costs and benefits, and I don't think I've seen advocates of "person who is X" address this one.
Eh, I think it's common enough for people to say they feel like they're walking on eggshells because of all the sensitivity stuff, and I think I've seen a few people say that they now feel uneasy around minorities because they're afraid to encounter one who's been taught to have a chip on their shoulder and might throw a fit at the smallest microaggression. It's not a hard connection to draw.
The social justice crowd is unlikely to address it because, with their norms of discussion, mentioning it will likely attract mockery and redirection: "Oh no, we must protect the feelings of the poor white people! How oppressed they are! I'm sure it's just as bad as having ancestors who were enslaved and lynched!" The term "white fragility" might be used; in feminist circles, it might be "what about the menz!?". There's an instance in this thread (flagged) of someone mocking someone who complained about inconveniences. I generally term this "Look at these oppressed people; your complaint is invalid".
These argumentative norms seem to prevent the social justice crowd, as a group, from making decisions of the form "Let's make a minor effort to avoid needlessly offending the people that we're nominally trying to win over".
Depends if the actual reason you are talking about them is that characteristic, right? So talking about black people precisely on race topics seems necessary, whereas if you are talking about a particular neighborhood, it seems unnecessary and racist.
Don't worry I'm in full agreement, OOP is a terrible paradigm ever since it left Alan Kay's original inception which was closer to the has-a message passing paradigm that survives today. Rust's is a pleasure to use with traits instead of classes. Go's interface model is nice too, like a static duck typing. I've always preferred lots of interfaces in C# to abstract classes
Language doesn’t do multiple inheritance well so has-a descriptions are easier to work recognizing that people are multifaceted.