Skip to main content

Summarize the article "Rethinking Proportionality Under The Cruel and Unusual Punishments Clause" at...

The article proposes that proportionality reviews are crucial in efforts to correctly interpret the Cruel and Unusual Punishments Clause. Additionally, proportionality highlights a retributive rather than a restorative concept of justice. Thus, to quantify excessiveness, one would need to consult prevailing moral standards rather than popular, shifting definitions of cruelty.


This article proposes that new approaches to proportionality would allow the Supreme Court to nullify death penalty verdicts for non-homicidal cases and to restrict life-without-parole sentences for juvenile offenders. The article states that a proportionality review is critical because the Supreme Court has failed to furnish a rational definition of proportionality and to employ concrete solutions that ensure proportionality.


In the past, the Supreme Court often rejected death penalties or life sentences even when there was no clear societal consensus against them. In these instances, the Court relied on a fictionalized consensus to justify its own arbitrary verdicts. At other times, the Court relied on its own independent judgment to define cruel and unusual punishment. In short, the Court lacked a definitive standard for measuring excessiveness.


As history shows, the original Framers interpreted the Eighth amendment in light of prior practice. Later, nineteenth-century law experts supported the notion that the Punishment Clauses rejected both excessive and barbaric retribution. However, they based this support on entrenched definitions of excessiveness. Basically, the Court needs a clear standard for defining "cruel and unusual punishment," a standard that must not be influenced by shifting public opinion, the Court's independent judgment, or the machinations of legislators.

Comments

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 ...

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.