Skip to main content

What are seven decisions that Friar Laurence makes in Romeo and Juliet?

Friar Laurence makes several important decisions during the course of Shakespeare's Romeo and Juliet. First, he decides to marry Romeo and Juliet because he believes it will end the often violent feud between the Montagues and Capulets. Second, he makes a conscious decision to advise Romeo to slow down in his love for Juliet. He tells Romeo, "Wisely and slow. They stumble that run fast." Third, in Act III, Scene 3, he decides that once Romeo has spent some time in Mantua he will announce that Romeo and Juliet are married, attempt to reconcile the families and beg the Prince's pardon so Romeo may return to Verona.


Fourth, he makes the unfortunate decision that Juliet should take a potion and fake her death. His plan is for the girl to appear dead so the family will take her to the Capulet tomb where Romeo will retrieve her when she awakens. Fifth, he decides to give the message informing Romeo of his plot to Friar John to carry to Mantua. Friar John is delayed in Verona by a plague threat and Romeo never receives the message. Sixth, he decides to leave the tomb just after Juliet wakes up because he is afraid for his reputation and his life if he is caught in the tomb with Juliet and the dead bodies of Romeo and Paris. Seventh, he decides that he needs to tell the truth to the Prince and so recounts the entire story of Romeo and Juliet's love and eventual suicides. 

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.