Skip to main content

What is so enjoyable about "The Pardoner's Tale" from The Canterbury Tales?

"The Pardoner's Tale" is enjoyable because both the prologue and the tale itself satirize human failings. In the prologue, the Pardoner, himself a greedy character who is open about his cupidity, relates how he defrauds his parishioners. While he preaches that greed is the root of evil, he also admits that "It's greed alone that makes me sermonize." He sells relics to make money, and he preaches to acquire money while watching others live in poverty.


In "The Pardoner's Tale," three unholy youths, condemned to death for their sins, hear while drinking in a pub that their friend, also drunk, was slain by a character named Death. They promise each other to slay Death--which is of course a fruitless and darkly funny task--and they wind up dying themselves. What kills them all is their own stupidity and greed, as two of them wait to slay the man who has gone for food and drink. After two of them slay the first man, they drink the wine that the other brought them (and that is poisoned). They all wind up dead, as by trying to meet Death, they wind up dead. The humor in this story comes from the tendency of people to think they can outwit death and from the way in which humans only wind up hurting themselves through their greed.

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

A man has a garden measuring 84 meters by 56 meters. He divides it into the minimum number of square plots. What is the length of the square plots?

We wish to divide this man's garden into the minimum number of square plots possible. A square has all four sides with the same length.Our garden is a rectangle, so the answer is clearly not 1 square plot. If we choose the wrong length for our squares, we may end up with missing holes or we may not be able to fit our squares inside the garden. So we have 84 meters in one direction and 56 meters in the other direction. When we start dividing the garden in square plots, we are "filling" those lengths in their respective directions. At each direction, there must be an integer number of squares (otherwise, we get holes or we leave the garden), so that all the square plots fill up the garden nicely. Thus, our job here is to find the greatest common divisor of 84 and 56. For this, we prime factor both of them: `56 = 2*2*2*7` `84 = 2*2*3*7` We can see that the prime factors and multiplicities in common are `2*2*7 = 28` . This is the desired length of the square plots. If you wi...