Skip to main content

According to David Sussman, what is the difference between coercion and torture, and why is coercion less wrong than torture?

In his article "What's Wrong with Torture?" Sussman writes that while coercion and torture can overlap, they are distinct because coercion operates only on the victim's rational responses and normal cognitive processes. Coercion involves telling the victim that the oppressor will act against his or her rational interests, and therefore the victim can use reasoning to respond to these threats. Torture, on the other hand, involves manipulating the victim by appealing to his or her emotions and vulnerabilities in a situation that involves disorientation. In other words, in the process of torture, a victim does not always know what is rational and cannot use his or her rational facilities to figure out the best course of action. It is possible to coerce another person only through using reason and rationality, while torture involves manipulating the other person's emotions.  


Coercion is not as bad as torture because it presents the victim with a rational set of actions to which he or she can respond with reason. However, when a victim is being tortured, he or she cannot submit to reason, as the outcome of submission will be a conclusion that involves an emotional or moral dilemma. In short, torture presents its victims with no rational options. 

Comments

Post a Comment

Popular posts from this blog

Is there a word/phrase for "unperformant"?

As a software engineer, I need to sometimes describe a piece of code as something that lacks performance or was not written with performance in mind. Example: This kind of coding style leads to unmaintainable and unperformant code. Based on my Google searches, this isn't a real word. What is the correct way to describe this? EDIT My usage of "performance" here is in regard to speed and efficiency. For example, the better the performance of code the faster the application runs. My question and example target the negative definition, which is in reference to preventing inefficient coding practices. Answer This kind of coding style leads to unmaintainable and unperformant code. In my opinion, reads more easily as: This coding style leads to unmaintainable and poorly performing code. The key to well-written documentation and reports lies in ease of understanding. Adding poorly understood words such as performant decreases that ease. In addressing the use of such a poorly ...
Post a Comment
Read more

Is 'efficate' a word in English?

I routinely hear the word "efficate" being used. For example, "The most powerful way to efficate a change in the system is to participate." I do not find entries for this word in common English dictionaries, but I do not have an unabridged dictionary. I have checked the OED (I'm not sure if it is considered unabridged), and it has no entry for "efficate". It does have an entry for "efficiate", which is used in the same way. Wordnik has an entry for "efficate" with over 1800 hits, thus providing some evidence for the frequency of use. I personally like the word and find the meaning very clear and obvious when others use it. If it's not currently an "officially documented" word, perhaps its continued use will result in it being better documented.
Post a Comment
Read more