Category Archives: King James Onlyism
HUNTING THE “MIGHTY HUNTER” – NIMROD
More Than the Antichrist Archetype?
One of the most intriguing characters in the Old Testament is Nimrod, son of Cush, and grandson of Ham. His name often comes up as the archetype of the Antichrist. It turns out that when we dig into the story surrounding Nimrod, there is much more to be said about his importance than just the speculation that he might be figure who arises again in the last days (“who was, is not, but will be again” – Revelation 17:8) as the Antichrist.
Most of you who read this follow me regularly. You are aware that … Read More
THE KEY ARGUMENT AGAINST THE SEPTUAGINT – IT WAS WRITTEN AFTER THE NEW TESTAMENT!
Perhaps the most incredible argument against the historical validity of the Septuagint (as a third-to-second-century-B.C. creation) is this: It was fabricated, following rather than preceding the composition of the New Testament (NT). It’s a heated area of debate because the King-James-only argument stands or falls based on when the LXX translation was commenced and completed. A valid LXX puts the King James Version at odds with itself, i.e., the two KJV Testaments really don’t agree with one another!
[The following is drawn from an Appendix to A BIOGRAPHY OF THE CHRISTIAN BIBLE.]
A typical unfavorable argument (against the Septuagint, LXX, … Read More
THE RECEIVED TEXT VS. THE CRITICAL TEXT: WHICH ONE IS RIGHT?
DOES A ‘RECEIVED TEXT’ IMPLY INERRANCY?
While champions of the superiority of the King James Bible argue that it is based on the “received text” and is categorically different from the “critical text,” this claim turns out to be ERRONEOUS. We only have to consider the history of how we got our Christian Bible to realize that the label “the received text” falsely assumes its composition was inspired and NOT the result of critical examination. This position contends that God inspired the one, perfectly, while the other was the result of “man manipulating God’s word.” This position believes today’s “critical … Read More
