Skip to main content

Why is it tragic that Gatsby chooses Daisy to embody his dream?

I'm not sure I can agree with this claim. We may find that the real tragedy lies elsewhere. It is possible that we can identify the source of Gatsby's tragedy as his own greed, rather than his "choosing" of Daisy. Nick describes the way Gatsby felt when he was first courting Daisy, how he knew that it was a "colossal accident" that he was in her home, that he was "penniless" and had nothing like what she already had. However,



"He took what he could get, ravenously and unscrupulously -- eventually he took Daisy one still October night, took her because he had no real right to touch her hand."



Gatsby lied to Daisy, allowed her to believe that he came from a family like hers, that he could offer her a life like the one she knew, and "he had deliberately given [her] a sense of security."  It was only after he had already committed himself to her that he began to actually love her.  


If Gatsby had not behaved in such an unscrupulous way, deliberately deceiving a young woman who didn't know any better than to be trusting, then his life wouldn't have ended tragically. It was his greed, his own flaws that started him down this path, and so I think it is necessary that we fault him, at least in part, for his sad end.  He used her, or he tried to, and so we cannot let him completely off the hook and blame Daisy alone.

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