No, lying does not prompt Romeo to kill the Count Paris. Paris's own loyalty to Juliet and stubbornness is what prompts Romeo to kill him. When Romeo arrives at Juliet's tomb, he finds Paris there, mourning her. Paris recognizes Romeo as the "banished Montague" who killed Tybalt, and he assumes that Romeo has come to do some harm to the bodies of the recently deceased Capulets. He also still believes that Juliet died in excess of grief over her cousin's death (which was Romeo's fault). Paris says, "Condemnèd villain, I do apprehend thee. / Obey and go with me, for thou must die" (5.3.63-64). He intends to fight Romeo and kill him in order to prevent him from exacting whatever further vengeance Paris believes he intends against the Capulets. Romeo expresses his earnest desire not to harm Paris, and he explains that he's actually come armed against himself. Romeo urges Paris to leave; however, Paris refuses and attempts to apprehend Romeo. Finally, they fight, and when Romeo mortally wounds Paris, Paris asks to be laid in the tomb with Juliet. Therefore, Paris doesn't lie and prompt Romeo to kill him; he simply refuses to leave Romeo alone at Juliet's grave and forces Romeo's hand by attempting to arrest him (an action that would prevent Romeo from carrying out his suicidal plan).
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 ...
Comments
Post a Comment