Yes; I keep asking about this.
Why is that your opinion? What are your reasons for choosing that alternative?
I've never found that my own "adversities" actually argue anything...and I'm sure you haven't experienced that either.
I'm just thinking about Job. I'm trying to unpack the narrative, and I'm looking for reasons why you rule out chapters 1-2 as having any literal significance. I'm perfectly happy to hear what those reasons are, really. I'm quite interested. No backhanded reason.One question the text asks is about the source of adversity. Mythology is a way of addressing such questions. Are we to conclude from the story of Adam and Eve that a tree is the source of knowledge or knowledge of good and evil? That there was a talking serpent? That there is another tree in the garden that if we could eat from it we would live forever?
Absolutely. What are those terms?I think the text must be addressed on its own terms,So while you may wish to dismiss the literal level of possibility there, you've got to admit that the text favours the literal first, and your allegorical interpretation only at the second level.
Of course not, if we have compelling reason to suppose it's myth or poetry of a non-literal kind. I'm just waiting to see what the compelling reasons for choosing the latter over any literal referents might be......but that does not mean we have to believe that what is being told is a historical account.
If we are to take sons of God literally then there must have been a female god who gave birth to sons, or parthenogenesis, or non-biological reproduction. All of which raises a whole host (pun intended) of questions.
Well, this is a different issue. But the term "Son" is positional, not temporal; for which reason, Christians speak of Christ as "the Eternal Son."
No: because "hide one's face" is a commonly-recognized idiom for "not speaking to," or "not communicating with." But that's certainly not obviously the case in the first two chapters of Job as a whole -- there's not a two-chapter-long idiom being reeled out there -- or if we suppose there is, we'd have to give compelling reasons why we think that's so, because normal idioms are much shorter and less detailed than the account in Job 1 and 2.When Job asks God:
Are we to take this to mean that God is a physical being with a face and that he is hiding it from Job?Why do you hide your face (13:24)
It's not an equivalent presupposition, though. Normative reading is to take text for what it says, unless reason can be shown that sufficiently counts against the taking of it that way.Because I take it to be a mythological account. Its truth is not a matter of a factual telling of events but of something we cannot see in actual events. A literal telling of events does not tell us why things happen as they do. The story begins like a fairy tale:Why is it that you think that? Is it that you have a specific reason, or that you just don't like the idea much? I just don't see the latter as an unequivocal reason to dismiss the more obvious level of text. But I'm open to hearing why it is.
If you wish to read it as a literal account that is up to you. We all bring our presuppositions with us.There was a man in the land of Uz whose name was Job; and this man was perfect and upright, and one that feared God and abstained from evil.
I grant the presence of the "there was a man" formulation at the start. Good point. But as I have said earlier, there's absolutely nothing that makes the allegorical and literal an either-or proposition; a history can have a kind of traditional, legendary start, and still be actual history. We'd have to decide on more than that, I would say. Otherwise, we'd have to conclude that the Trojan War never happened, because Homer wrote about it in traditional poet's language. That would seem capricious, would it not?
That's unfortunate, perhaps. Because nothing is more central to Christianity than the reality of the Resurrection, which was (if we believe the multiple historical record at all) prophesied by Jesus Christ Himself, affirmed by later witnesses and the disciples, and explained as essential to the Christian faith by the greatest exponent of that faith, the Apostle Paul. We can certainly say that someone who shares that belief does have the right to call themselves "Christian": but that's not such an easy claim to defend for anyone who does not believe in the Resurrection as a literal event. The whole history of Christianity is against them on that, of course.I am not going to get into a discussion of the resurrection
But we're dealing with Job at the moment. It's clear that the Resurrection is a singularly poor example to call into question by way of analogy, to argue that Job can't be literal. Everybody who's anybody in the Christian world takes the Resurrection to be the literal-and-allegorically-significant event par excellence in human history.
Right. That's a major theme of Job: adversity per se is not evil, nor is it a signal of the judgment of God against someone. But that would create a problem for your Adversary-adversity theory, because the Satan is certainly depicted as evil, no? So how could he and "adversity" be one and the same, even mythically speaking, without also implying that adversity WAS a kind of evil? After all, you've made them mythically identical there.But calling something evil does not mean one thinks it is due to the disapproval of God. That is the question they wrestle with - does evil signal the disapproval of God? God did not disprove of his perfect servant Job, so that cannot be the source of evil.
Then I won't try to do so. But if you read to the end of the book, he dies happy and blessed -- as it says, "an old man, and full of days." One thing for sure that the Book of Job teaches: you learn more about God through your suffering, and through taking the right attitude to it, then you will ever learn by being rich and comfortable. And if the knowledge of God turns out to be the most important thing in the universe, then what would one not wisely give up to have more of it?There is no argument that you can make to convince me that losing his family and being inflicted with terrible pain and disease was the best thing for him.So now we have to wonder if adversity wasn't the best thing for him, whether he knew it or not, don't we?
Oh, I wouldn't argue with the possibility of two readings of the word. Do we not have a word like "bow," which can mean "the front of a ship," or "a gesture of respect," or "a manner of tying ribbon," or "a weapon," among other things? Context is the determiner of how we ought to read a given word, even in English. The issue is what is the right way to understand the particular use in reference to Job's circumstances (adversity?) and to the Adversary.Adversity and evil are two ways in which the Hebrew term ra’ are translated. See Strong’s Concordance: http://biblehub.com/hebrew/7451.htm. As I pointed out, the Hebrew word itself does not even always mean evil. Would you say that Job is not about evil because what is ra’ is not always evil, as with the case of the table that has a bad (ra') leg?So I don't think we can read the Book of Job as a treatise on how evil adversity always is.
You can re-imagine Job as merely a story about "adversity." But if you do, then it has nothing at all to say about evil, since adversity is actually not inherently evil at all.
May I suggest that you'll get more traction from de-coupling the idea of "evil" from the idea of "adversity"? After all, "adversity" is merely a state of affairs, of "things being contrary." But "evil" is a value judgment that may or may not be applied justly to given cases. Thus there could be such a thing as "good adversity" (as in an athletic achievement) and "evil adversity." Certainly one thing Job does not teach is that we are to regard adversity itself as inherently and always evil.