just me wrote:There are several recorded incidents of genocide in the Old Testament. There are some interesting points about it. 1) archeaology does not support it
This is correct. The archaeological record doesn't support the genocides in Numbers and Joshua. There are two main reasons archaeologists believe this. The most powerful is that in many cases the areas which were epicenters of the genocide were completely unpopulated during the time period of the supposed genocide. For example the slaughter of the Midianites in Numbers is highly dubious based on the fact that Midian was basically unpopulated during the time of Numbers and remained so for centuries thereafter. The destruction at A.I. in Joshua also suffers from the same problem, it seems to have been unpopulated during the required time period, but was destroyed centuries earlier.
The second reason is lack of destruction layers in the archaeological record. In many cases the sites can be shown to have been continuously populated during the time period, with no trace of a destruction layer. If there were only one or two sites which had this pattern, it could be written off as missing destruction layers (there's no law that every ancient destruction is accompanied by a destruction layer). But, since Joshua identifies many sites, and a large percentage of them have been identified and excavated, there should be some destruction layers present for a significant percentage of the sites. There isn't any.
just me wrote:2) some people are killed more than once or are still alive after being allegedly killed.
Yes, you see this in the Bible with the Amalekites. You also see it in Joshua/Judges. If you read Joshua, it's very clear that the invasion of Canaan was a huge wipeout. But, read the first two chapters of Judges, you get a very different story.
My conclusion is that there were probably multiple accounts of what happened and both were weaved into the story for completeness. The Bible includes multiple contradictory accounts, some minor contradictions, some fairly major. The modern response is to cry that this proves the Bible is unhistorical. Actually, I think it proves the exact opposite. Ancient history is full of multiple contradictory accounts. It's a modern presumption that unless a history is univocal, it doesn't qualify as history. The problem is that you just flushed a ton of ancient history down the toilet with that approach.
just me wrote:These are conflicts that I wonder how believers reconcile. I also wonder why there is the need to believe that god really commanded genocide and really has killed people. Why come up with justification and apologia at all? Why not be relieved that the archeaological record doesn't support that it ever happened afterall?
In general, I don't provide apologia when the evidence suggests that it did not happen. I just say, it didn't happen. The more you are married to the idea of a completely inerrant Bible, the more you have to defend this kind of stuff.
But there's something else interesting here. For most of Christian history, these stories have not been seen as a great idea, but have been read allegorically. This is a good thing, but something that I think most people get completely wrong nowadays. The standard idea nowadays is that everyone read the Bible as straight history up until science showed it was all crap and now only ignoramuses and baby eaters like the Bible. The problem is that allegorical readings of the Bible achieved a high point during the middle ages, long before science had any traction in the marketplace of ideas. Current modernist and fundamentalist views of the Bible are both remarkably similar and remarkably at odds with how the Bible has traditionally been read in Christianity (and Judaism for that matter).
But the problem is that most people are so steeped in modernism/fundamentalism (at the level of Biblical interpretation they are exactly the same) that they can't envision reading the Bible any other way than flat, literal, history. Nor do they see any value in reading it any other way.