Old Bible People

How is it possible that people in Genesis lived 900+ years?

I do not necessarily see the need to prove the Bible scientifically, but I do belief that the Bible is accurate. Therefore, I believe that Adam, Noah, Methuselah, etc., really did live 900+ years. Whether or not there was some sort of water canopy or not, I don’t know, but it does appear that the reduction in life span started happening following the Flood, so the most likely explanation in my mind is that there was some sort of change that happened as a result of the flood.

If you follow the genealogies listed in Genesis 5, the Flood takes place 1656 years after Adam’s creation. There are 9 generations between Adam and Noah. Noah was 600 when the Flood began, so those 9 generations are spaced across approximately 1000 years.

After the Flood, there are another 9 generations from Shem to Abram. Using the ages listed in Genesis 11, these 9 generations span 450 years. Looking at the total lifespan of all these individuals, it’s relatively flat until Noah (although Lamech died a bit “young”), and then it starts a steep decline (see attached image; note: I left out Enoch since he didn’t actually die). It seems reasonable to me that the Flood during Noah’s time played a role in shortening the lifespans. If the shortened lifespans were due to the fall of man back in Eden, or the absence of the Tree of Life fruit, you should see a steady decline. It should also be noted that the scale of the curve may be deceiving. I show all the generations equally spaced, but in reality the “flat part” from Adam to Noah spans a time period more than twice as long as the “decline” from Noah to Terah. If I scaled the x-axis according to time, the drop-off would appear even more distinct.

On a side note…

Noah was 500 years old when he became father of Shem, Ham and Japeth (Genesis
5:32) – all in one year? Shem was 100 when he fathered Arphaxad (Genesis 11:10).

Genesis 11:10 also reveals that Arphaxad was born 2 years after the flood. Since the flood started with Noah was 600 years old, Arphaxad was born when Noah was 602 years old and Shem was 100 years old. That means Noah was 502 when Shem was born. Genesis 5:32 most likely means Noah was 500 years old when he became a father. Since Ham is referred to as the youngest in Genesis 9:24, and Shem was born when Noah was 502, the son he had when he was 500 must have been Japheth. The confusing thing is that some translations refer to Shem as the “older brother of Japheth” in Genesis 10:21, whereas other translations refer to Shem as the brother of “Japheth the elder.” While Japheth, Shem, Ham seems like the most likely birth order to me, that’s a topic for another thread.

This doesn’t have anything to do with WHY people lived a long time or what happened to change that, but here’s another interesting look at the various lifespans. Shem was still alive for another 150 years after Abram was born. I don’t have Isaac on the chart, but Abraham had Isaac when he was 100, so Shem was still around for another 50 years after Isaac was born. I don’t know if they lived in the same area or not, but it’s possible that Isaac knew his great, great, great, great, great, great, great, great grandfather. Shem could have even been at Isaac and Rebekah’s wedding (Isaac was 40 when they got married), but he missed Jacob and Esau by 10 years (Isaac was 60 when they were born).

Divorce

I think the strongest case against divorce is to look at what marriage symbolizes. God uses imagery to help us understand our relationship with Him. We relate to Him as children to a parent or as servants to a master. We understand these relationships because we experience them every day on earth. There is no greater image of our relationship with God than that of a husband and wife. Of all the parallels that are drawn in scripture, this is the one that gets the most attention and the one that comes the closest to reflecting what our relationship with God was designed to be.

God says He will never leave us or forsake us, and scripture is filled with His continual pursuit of His chosen people (despite their desertion and unfaithfulness). For a husband or wife to divorce their spouse, flies in the face of all that marriage is supposed to signify.

I find it interesting that Matthew, Mark, and Luke all record the occasion when the Pharisees questioned Jesus about divorce, but Matthew is the only one who mentions the exception for maritial unfaithfulness. Clearly, while Jesus made this allowance, the thing that really stuck out was His emphatic insistence that husbands and wives should never separate (“what God has joined together, let man not separate”).

When it comes to “what’s done is done, can I get remarried?” I think there are a couple of slippery slopes to be avoided. One is the idea that as long as the other party gets remarried, and therefore “becomes unfaithful,” you are therefore free. This would open the door to marry and divorce willy-nilly provided you always make sure your ex gets remarried first. It also places a great deal of importance on timing; ie., who was unfaithful first. It essentially means two people can take the exact same actions, but one of them is guilty of adultery and the other gets off scot free. This clearly is not what God had in mind. I think the allowance for divorce in the case of marital unfaithfulness is restricted to when it occurs in the context of the marital relationship. I don’t think it is a “way out” for two people who have severed their relationship, regardless of whether they are technically (either legally or in God’s eyes) still married or not.

I also think the “lust = adultery = just cause for divorce” concept is a slippery slope. When Jesus said in Matthew 5:28 that lust is equivalent to committing adultery, the word for adultery is moicheuo?. In Matthew 5:32 and 19:9, the word for unfaithfulness or fornication is porneia. Even without looking at the Greek words, I would have a problem with this concept because it again opens up a huge “loophole” to allow unhappy people to get out of their marriage, and I don’t believe that’s what God had in mind.

Does that mean someone who made a mistake and married the wrong person, or made a mistake and got divorced when they should have stayed married is doomed to suffer the consequences for the rest of their life? Well, at the risk of sounding harsh, I definitely think it’s a viewpoint that should be considered. Nowhere does God promise to remove the consequences of our own sin, or even the sin of others. He is more concerned with our holiness than He is with our happiness. The truth of the matter is, we are most likely to be happy when we are holy.

Here are links to scriptures that talk about divorce and scholarly articles on the subject:

Nave’s Topical Bible

Torrey’s Topical Handbook

International Standard Bible Encyclopedia: Divorce in the OT

International Standard Bible Encyclopedia: Divorce in the NT

Baker’s Evangelical Dictionary

Chick Tracts

I like the idea of putting Bible doctrine and gospel messages in comic book style tracts. I haven’t read all of the Chick tracts, but I assume there are some that I could give to someone without any qualms. However, there are also some that I would never give to anyone. “Angels?” (about Christian rock) and “The Attack” (about the KJV Bible) are two that are utterly ridiculous.

All (or at least a lot) of the tracts can be read at www.chick.com. I looked at one about Mormonism, and all the claims are footnoted. Anyone who cares to investigate the claims can go to the LDS sources to see if they are taken out of context or come from legitimate LDS authorities or just random LDS adherants.

Let’s look at a couple specifics of The Attack.

He calls the Alexandrian Manuscripts “satanic.” You can argue that they aren’t as accurate, but to call them “satanic” is ridiculous. He says the Alexandrian Manuscripts “down-play the diety of Christ, the virgin birth, salvation by grace through faith, etc.” This is a bogus claim. The only way to support this claim is by taking isolated verses and comparing them to the KJV, with the assumption that if it doesn’t match the KJV it’s corrupted. This is circular reasoning. Every translation of the Bible I have seen affirms the diety of Christ, the virgin birth, salvation by grace through faith, etc.

He claims that the NASB “denies the virgin birth” by changing Luke 2:33. First off, the NASB doesn’t “change” anything. They simply translated the Greek word “pate?r.” If you want to argue that the word was changed in the version of the Greek manuscript they used, fine, but don’t blame the NASB translators for the change. It’s also false to say the NASB denies the virgin birth. If they were going to do that, they would also have changed Isaiah 7:14 (“a virgin will be with child and bear a son”), Matthew 1:18 (“before they came together she was found to be with child by the Holy Spirit”), Matthew 1:23 (“the virgin shall be with child and shall bear a son”), Matthew 1:25 (“but kept her a virgin until she gave birth to a Son”), and others. If you want to be picky about calling Joseph Jesus’ father, let’s see what the KJV has in Luke 2:48. Mary says to Jesus, “thy father and I have sought thee sorrowing.” Mind you, this is the KJV, and Mary obviously knows that Jesus is not Joseph’s biological son, and yet she calls Joseph his “father.”

He goes on to accuse other Bible versions of being “corrupted” and “tampering” with Scripture for leaving out the Comma Johanneum in 1 John 5:7. He doesn’t bother to tell you that of the 8 Greek manuscripts that have these words, it was written in the margin by a later hand on four of them. That doesn’t speak well to it’s authenticity. (http://www.bible-researcher.com/comma.html)

Now that I think about it, his willingness to twist the truth and spread misinformation would cause me to have some qualms about handing out even some of the tracts that have only good content. I wouldn’t want someone to think that Chick Publications was a trusted authority on Biblical issues and be misled by some of their outlandish teachings.

I don’t mind someone defending the KJV as the “best” translation, but when they attack any other translation as satanic, they go overboard and lose their credibility.

Two Wolves

This modern-day parable was posted on bibleforums.org:

One evening an old Cherokee told his grandson about a battle that goes on
inside people. He said, “My son, the battle is between 2 “wolves” inside us
all.

One is Evil. It is anger, envy, jealousy, sorrow, regret,greed, arrogance,
self-pity, guilt, resentment, inferiority, lies, false pride, superiority, and
ego.

The other is Good. It is joy, peace, love, hope, serenity, humility,
kindness, benevolence, empathy, generosity, truth, compassion and faith.”

The grandson thought about it for a minute and then asked his
grandfather:”Which wolf wins?”

The old Cherokee simply replied, “The one you feed.”

A well-meaning individual replied that the story was not biblical. I submit that it can be interpreted biblically.

This story, the origins of which are unknown (possibly invented by a preacher as an illustration), is not unbiblical. The full context of what Paul said in Romans 7 helps us see that.

Continue reading

Bible Translations

Translation philosophy

Bible translations commonly adopt primarily one of two philosophies for determining the correct English translation of the Hebrew or Greek text. The first is “formal equivalence” or “word-for-word.” Here the translator takes each Hebrew or Greek word and attempts to translate it into the equivalent English word. An alternative approach is “dynamic equivalence” or “thought-for-thought.” In this case, the translator first attempts to determine the meaning of a complete phrase in the original language, then picks the English words that best convey the same meaning. The translators of the Holman Christian Standard Bible (and perhaps other translations) have opted to use “optimal equivalence” which might be explained as “as literal as possible, as free as necessary.”

I like the idea of “optimal equivalency.” The way I would phrase it is, “word-for-word as much as possible, unless it produces confusion.” I tried to think of an example where a word-for-word translation would create confusion, and although it’s not a great example, consider the following scenario: let’s say I’m translating the phrase “la bota negra” from Spanish to English. I look up each word in the Spanish-English dictionary, and I see that la=the, bota=boot, and negra=black. So the literal English translation would be “the boot black.” According to the American Heritage Dictionary, a boot-black is “a person who cleans and polishes shoes for a living.” However, anyone familiar with Spanish knows that the modifier (adjective) comes after the noun, whereas in English we put the modifier in front of the noun, so the correct English translation would be “the black boot.” This would be a case where a truly literal word-for-word translation would be a bad idea. Then, of course, sometimes a truly literal word-for-word translation isn’t even possible, because there is no one-to-one correspondance of the Greek or Hebrew word with an English word.

There’s also the issue that what is clear to one person might be confusing to someone else. Something that might be easily understood by an English major might be quite confusing to someone who struggled to graduate highschool. In that case, there is certainly a place for a variety of translations at different reading levels. Unfortunately, simplifying a translation can also require sacrificing some accuracy sometimes.

What if the original language is confusing? Should the translator take his best stab at the intended meaning, or leave it ambiguous so the reader can take it either way? This is a judgement call that the translator has to make, in part depending on how much confidence he has in his ability to interpret the true intent of the passage.

Continue reading