Skip to main content

Was International Covenant on Economic, Social and Culture Rights (ICESCR) a politically motivated response to the realities of the Cold War? Were...

The original concept of ICESCR itself may not necessarily have been a byproduct of the Cold War, but its subsequent drafting and ratification definitely were.


ICESCR has its origins in the Universal Declaration of Human Rights, adopted by the UN in 1948 as a reaction to the atrocities of World War II. After adoption of the UDHR, work began on drafting formal covenants to enforce its underlying principles and the overall framework became known as the International Bill of Human Rights). The drafting, adoption and ratification took decades, during which the Cold War became the overwhelmingly dominant force in geopolitics. In that atmosphere, the ICESCR could not help but become a sort of Cold War political football in nature, with arguments over its provisions stemming from various nations’ competing and sometimes contradictory perspectives.


Nations signed on with a variety of motivations. Some were sincere, while others ratified it as a sort of moral cover, not having any intention of abiding by its provisions but wanting to give their regimes the appearance of moral legitimacy. Still others, most notably the USA, saw ratification of the treaty fall victim to internal politics that had little to do with international geopolitical realities.

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.