Skip to main content

How does Macbeth die?

Macbeth is killed by Macduff on the battlefield in front of Dunsinane in the last scene of the last act. Their sword fighting begins onstage and then is carried offstage. They reenter the stage still fighting, and "Macbeth is slain." It would appear that Shakespeare did not want to show too much of the fighting onstage because there was always the danger that one of his principle actors would get hurt. Ordinarily, Macbeth would probably have won the swordfight. It has been demonstrated that he is a ferocious warrior capable of slaughtering dozens on the battlefield. But he is unnerved when Macduff tells him:



Despair thy charm,
And let the angel whom thou still hast served
Tell thee, Macduff was from his mother's womb
Untimely ripp'd.           V.7



Macduff replies:



Accursed be that tongue that tells me so,
For it hath cow'd my better part of man!




Macbeth does not fight with his accustomed vigor. He is on the defensive. He had been counting on the assurances of the three weird sisters, but he learns that they were equivocating. Birnam Wood has moved to Dunsinane and he is confronted by a highly motivated opponent who was delivered at birth by a crude Caesarian section. But the best that can be said of Macbeth by this point is that he goes down fighting and is even willing to take on 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 ...

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