Hacker News Reader

Comment by logicalmonster | Hacker News Reader

The title makes this article appear like some modern bit of political correctness, but if you check it out I think this policy is basically calling out lazy journalists who defaulted to describing conflicts as something like "ethnic tension" instead of trying to investigate and figure out the complex land dispute or other nuanced issue that caused a fight.

The thing that people should be asking here is if journalists can't be bothered to get matters of life and death correct, what else are they wrong about?

View on HN

Indeed. One could even draw an analogy between lazy journalists who use a word like "ethnic" as a shortcut for describing the actual situation and lazy forum commenters who just toss a labored 1984 quote out instead of explaining why this instance of language modification is bad while other instances of language modification (such as the neologism "troon," a word that already had a meaning but that meaning has been redefined in common usage) are acceptable.

1984 is great because it bifurcates most responses in a revealing way: there are people who understand it as a cautionary tale against something that hasn't happened, and people who understand its many wonderful metaphors as representing recurring themes in human politics. So many of the phrases the former crowd likes to trot out would tickle Syme to death: people come up with their own NewSpeak in the form of thought-terminating cliches to opt out of reason entirely.

edit to bring it back to the topic: "ethnic" as a catch-all is actually a brilliant example of what NewSpeak is a metaphor for.

That’s what the source article is saying, but I think they’re wrong. It would be very misleading to describe something like the Bosnian War solely in terms of the political conflict about post-Yugoslav governance; a critical factor, without which the story makes no sense, is the genuine hatred between Serbs and Bosniaks that was common at the time. Srebrenica didn’t happen because a chain of escalation made it inevitable, or because some war objective put the victims tragically in the way, it happened because the Army of Republika Srpska did not think the victims’ lives were particularly important.

It is not the point of the article that actual conflicts between ethnicities should be reframed as something other than what they are; it's that their journalists have to describe the animus between Serbs and Bosniaks directly, and not roll the whole thing up into "an ethnic conflict". They're not avoiding the concept of ethnicity, just the generalizing, overly-broad (for their purposes) term.

But it's often not right to describe the animus "directly", if that's understood to mean (as they describe in the article) uncritically reporting what the people involved say about the conflict. The Troubles are the best English-language example, because there are piles and piles of primary source material with inflammatory and incompatible claims about the nature of the conflict. Was it religious, or racial, or linguistic, or geographic? All of the above and none, depending on who you ask. In fact, you'll note that "the Troubles" as a term is a response to the same issue - it would be extraordinarily unhelpful if news organizations felt obligated to choose between calling the conflict "IRA terrorism" or "British colonial aggression", even though basically every participant believed one of those two terms to be more accurate and precise.

I guess to some degree it does depend on what their purposes are, because there's value in understanding what average people in the area are thinking. But it's hard to imagine a news organization that never needs to mention a conflict without taking a position on it, and easy to imagine an organization which silently glosses over the issue because they assume there's a right side and trust the sympathetic voices they're talking to are on it.

Indeed. They are encouraging use of more precise language not censoring opinions.

There is an expression "missing the forest for all the trees". Big picture abstraction, and precise details are both useful and have their place.

There is also bias when constructing a subjective big picture. Bias is more important in journalism. Perhaps editors should weigh language like this and edit publications since that is their job. It would be better to ban the word ethnicity but allow exceptions when the journalist feels it is needed and can justify it.

Are they not also being lazy by banning the terms “ethnic cleansing”, “ethnicity” and “ethnic foods”?

No? Explain.

No they are not because phrases like forced relocation, Catholics, and sushi are more accurate.

“Ethnic food” is really what bugs me. WTF does that mean? Explain the cuisine please, I’m a foodie!

“Look in the ethnic foods isle for your matzo, dried seaweed, ghee and El Yuacteco.”

It’s basically the isle that could be labeled “packaged food for foodies”

This sort of imprecise, reductive othering illustrates what's problematic about the "ethnic foods" aisle (and "ethnic tensions").

Yeah I’d rather that stuff show up where it normally would. It’s just lazy to shove it all in an “ethnic” aisle.

Ok, so what was the holocaust?

Forced relocation? Mass killing? Both, and other things, so “cleansing”

Of who? Jews? Gypsies? Gays? Blacks? All of those, so not “religious” or “racial”. Instead, “ethnic”

Sadly, ethnic cleansing has happened repeatedly since (and before) then. It is the most precise, description that is not too narrow.

If we can’t name the crime, then how do we describe it or bring the guilty to justice?

The holocaust wasn’t an ethnic cleansing it was a genocide.

“Ethnic Cleansing” is when you force the ethnic Germans out of Kaliningrad (née Königsberg) and replace them with ethnic Russians. Genocide is when you round up the undesirables and systematically murder them.

My sincere advice is go learn a thing or two before commenting on topics like this again.

Be wary of any unfalsifiable frameworks.

> instead of trying to investigate and figure out the complex land dispute or other nuanced issue that caused a fight.

Because the original cause is often irrelevant. A random spat about land might be what sparks conflict, but ethnic tension is what fuels it and keeps it going. And yes, "ethnic" is a complex word, mixing issues of religion, culture, language, ancestry, "tribe"-level social organization and whatnot. Guess what, these things get mixed up all the time anyway, and having a single word to describe the resulting mess is highly useful. The world is complex. Deal with it.

"The ethnic tension increased. People fought because of ethnic tension. The ethnic tension led to conflict that killed people. The US President denounced the ethnic tension."

Look mom, I'm a journalist now. PayPal me, New York Times.

It feels like taking multiple complex overlapping causes and tossing one word on top of them is the opposite of dealing with complexity.

When we debug, do we tell other engineers that we're solving a "software problem," or do we use qualifiers?

On the contrary, having multiple levels of description is a key tool in dealing with complexity. You can always provide more information about the actual mix of overlapping causes pertaining to any given case, but that should come after a broader description is provided to frame the overall context.

"Software problem" is too broad. If software engineers are working on it, of course it's a software problem.

Analogously, the point the article appears to make is that if humans are involved in a civil war, of course there are ethnic tensions.

The point is saying ethnic is ambiguous in this context. So using it fails to specify what’s actually going on.

Would you be fine if someone described the troubles in Northern Ireland as ethnic tension, or knowing more about what happened would you use some other description?

> Would you be fine if someone described the troubles in Northern Ireland as ethnic tension

Why not? It's a lot more accurate than the usual description of "Protestants and Catholics" while still being simple and clear.

Yep, that's the counter argument right there. Sometimes it's better to be vaguely accurate than precisely missing much of the point.

Vaguely accurate is just another way of saying wrong.

No, "vaguely accurate" is a way of avoiding labels which are more precise and wrong. It's better to describe a disputed large quantity with the vague but accurate label of "millions" than choose a random scholar of unknown quality's estimate to 3 s.f as the correct figure.

It's better to summarise the Troubles in Northern Ireland vaguely accurately as "ethnic tensions" than precisely wrongly as a religious war between two schools of Christianity.

Saying gas is about 4$ right now is vaguely accurate, of course it’s also wrong. Consider the phrase “not even vaguely accurate” means it’s not just wrong it’s very wrong.

Being vaguely accurate on a history test may give partial credit, but the news should to be held to a higher standard.

> Why not?

Because it wasn’t purely ethnic in nature with Protestants and Catholics on both sides of the conflict. Trying to summarize it as ethic conflict was therefore also also incorrect. Which why using ethic tensions is so often misleading, it seems appropriate in many situations when it really isn’t.

I’d like to deal with it. My preferred way to deal with this complexity is to have an information diet that includes sincere attempts to capture this complexity, by reporting what is specifically happening with “ethnic tensions” in Ukraine, or the US, or Xinjiang. These are very different processes that are illuminated through details like, for instance, a “random spat” about land. It sounds like these folks are on the same page.

I can see why an organization that does international journalism would taboo “ethnic tension” on the presumption that there is a lot more to be said in order to capture the events and processed they are reporting on.

To me, it seems that you are claiming that "ethnic tension" is a pattern of human behavior which is independent of actual circumstances.

Reply on news.ycombinator.com