Skip to main content

What does Jonathan Edwards hope to accomplish with his message in Sinners in the Hands of an Angry God?

Jonathan Edwards' goal was to awaken people to what, to him, was the very real danger of continuing in their sin, to get them to repent and call on God for mercy. Though he intended to scare and sober his audience, his goal was not to drive them away, but ultimately to bring them to God.


Edwards preached the sermon in response to what he sensed was a complacent attitude in the town where he was preaching. People were professing Christians, but they assumed that by attending church, they had done all they needed to do. They were not thinking in terms of God as being a real entity whom they had wronged, and with whom they desperately needed to repair the relationship. Edwards sought to shake them out of their complacency by putting vividly before them just how ugly sin is in the sight of God, and how seriously God takes sin. Only then would they take their own sin equally seriously, enough to repent of it, actually stop doing it, and change their lifestyle while calling on God for help.


Thus, Edwards' use of the words "angry God" was not intended to tell his audience that God had rejected them forever. (Then they would give up, or lash out at God in reciprocal anger.) Rather, he was in essence saying, "Your attitude and lifestyle is angering God ... do something about it!" He points out that when people turn to God in repentance, God will quickly forgive.


Edwards' ideal response to such a sermon from his audience would be for them to repent, with genuine sorrow, over their sin; hate it, desire to leave it, and to beg with God to forgive them and draw them closer to Him, and to do all this, not in a "go-home-and-think-about-it" kind of way, but with a sense of urgency. This is exactly the response that many in the congregation had, even weeping and crying out in the middle of the service.

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

What warning does Chuchundra issue to Rikki?

Chuchundra, the sniveling, fearful muskrat who creeps around walls because he is too terrified to go into the center of a room, meets Rikki in the middle of the night. He insults Rikki by begging him not to kill him. He then insults him by suggesting that Nag might mistake Chuchundra for Rikki. He says, "Those who kill snakes get killed by snakes."  He issues this warning to Rikki not to help keep Rikki safe but as a way of explaining why Rikki's presence gives him, Chuchundra, more reason to fear.  Chuchundra starts to tell Rikki what Chua the rat told him--but breaks it off when he realizes he might be overheard by Nag. He says, "Nag is everywhere, Rikki-Tikki." Rikki threatens to bite Chuchundra to get him to talk. Even then, Chuchundra won't overtly reveal any information. But he does say, "Can't you hear, Rikki-Tikki?" This is enough of a clue for the clever mongoose. He listens carefully and can just make out the "faintest scratch-s...