Skip to main content

How is fate described in Macbeth?

In Macbeth, fate is made to seem like an unquestionable force, something that determines and directs the course of our lives. It is made to seem this way by the Weird Sisters and the way they speak to Macbeth and Banquo about their futures. When the witches hail Macbeth as Thane of Glamis, Thane of Cawdor, and the future king, they do so without qualification; there is no if this, then that. They simply present him with what appear to be facts about Macbeth's future without saying what actions he must take to become Thane of Cawdor or king. The same goes for Banquo; the witches tell him that he will father a line of kings without explaining how Banquo's lineage will rule.  


It is the same with the three apparitions the Weird Sisters later conjure for Macbeth. They present the king with two statements that seem to be assurances of a secure fate, but turn out to be enigmatically-worded statements of fact instead. The witches tell Macbeth that "none of woman born / Shall harm Macbeth" and "Macbeth shall never vanquished be until / Great Birnam Wood to high Dunsinane Hill / Shall come against him" (IV.1.91-92, 105-107). The witches seem to present fate as factual, non-negotiable, and out of one's hands; however, it is really Macbeth's own flaws that prevent him from seeing his tragic end is the result of his own behavior, not fate.

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.