Skip to main content

What are some of Romeo's faults in Romeo and Juliet?

One could argue Romeo is the most flawed character in the entire play. Let's take a closer look at some of Romeo's character traits and how they detrimentally affect him:


- Romeo is fickle in love and chooses to embark on conquests doomed from the start. Romeo begins the play with what he proclaims to be an undying love for Rosaline. This is problematic for two reasons. First, Rosaline is the niece of Lord Capulet and, thus, a member of a rivaling family. Second, she decided to take a vow of chastity, meaning that she is literally unavailable—physically, emotionally, AND spiritually. Within the space of a single act, Romeo experiences a radical shift in emotion, and sets his sights on Juliet Capulet instead. Again, this is an ill-fated conquest. Juliet is the daughter of Lord Capulet, who hopes Paris will be Juliet's husband. Romeo makes poor choices in women, selecting only those obviously out of his reach. This self-sabotaging behavior is compounded by Romeo's inconsistency; the only thing consistent about Romeo is how often he changes his mind!


- Romeo makes rash decisions, often as a result of his unchecked emotions. Romeo's impulsivity causes a lot of major problems throughout the play. His ridiculous lust for Rosaline leads him to foolishly attend the ball of a family who would have him murdered if they could get away with it. Romeo's hot-headed nature after Mercutio's death causes him to thoughtlessly kill Tybalt, Juliet's cousin. That same wild, selfish aggression causes Romeo to kill Paris outside of the Capulet crypt and commit suicide within it. Romeo's emotions are mercurial at best, and deadly at worst. 


Overall, this play might have ended very differently had Romeo learned to communicate, engage in responsible, adult relationships, and think things through before committing to life-altering decisions or actions.

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

What warning does Chuchundra issue to Rikki?

Chuchundra, the sniveling, fearful muskrat who creeps around walls because he is too terrified to go into the center of a room, meets Rikki in the middle of the night. He insults Rikki by begging him not to kill him. He then insults him by suggesting that Nag might mistake Chuchundra for Rikki. He says, "Those who kill snakes get killed by snakes."  He issues this warning to Rikki not to help keep Rikki safe but as a way of explaining why Rikki's presence gives him, Chuchundra, more reason to fear.  Chuchundra starts to tell Rikki what Chua the rat told him--but breaks it off when he realizes he might be overheard by Nag. He says, "Nag is everywhere, Rikki-Tikki." Rikki threatens to bite Chuchundra to get him to talk. Even then, Chuchundra won't overtly reveal any information. But he does say, "Can't you hear, Rikki-Tikki?" This is enough of a clue for the clever mongoose. He listens carefully and can just make out the "faintest scratch-s...