Skip to main content

Are there any juxtapositions in Macbeth's famous soliloquy that begins "Tomorrow, and tomorrow..."?

In this soliloquy, Macbeth expresses the despair he feels upon Lady Macbeth's death.  This despair is darkened further by the sense of meaninglessness and doom as Macbeth contemplates his empty future which was once so full of promise and ambition.  The juxtapositions in the passage serve to intensify this portrayal of despair.  


For example, there is the juxtaposition of light versus dark.  The past is marked by "lighted fools" while the future ends in the darkness of death.  "Out, out, brief candle!" describes the individual's death.  The interim, life, is "but a walking shadow."  Darkness can signify the corruption of Macbeth's soul in the course of the play's events as well as the growing influence of the "weird sisters" (demonic forces).  


Another juxtaposition is sound and silence.  There are parallels in the descriptions of life as a poor player strutting upon the stage only to be "heard no more" and life as a tale told by an idiot, "full of sound and fury,/Signifying nothing."  In both descriptions, Shakespeare juxtaposes the sounds of a life with the silence of death.  Ultimately, the noises of life mean "nothing"--just as the ambitions of Macbeth came to nothing and end in his death.

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.