Showing posts with label certainty. Show all posts
Showing posts with label certainty. Show all posts

Monday, April 29, 2024

“Why I Trust the New Testament Is What God Wrote”: Contend 2024

54

Over the weekend, I spoke for one of the break-out sessions at Contend—an apologetics conference at New Orleans Baptist Theological Seminary that is geared for high school students. The title of my presentation was "Why I Trust the New Testament is What God Wrote," and that title was intentional. The talk wasn't so much to convince anybody that we do really have God's words as it was rather to tell them why I believe we do really have God's words.

My talk was based on what I presented a while back at the church where I was ordained. That itself was an interesting situation—it is a TR church that has always used the KJV or NKJV, but they also recognize that it's not an issue worth dividing over and consider other translations to be sufficient as well. My impression of the rationale at that church has always been that it was an unstated trust that TR translations are 'safe' in that God has obviously blessed their use, and since that's what the pastors typically used, they just stayed with it because there are more important things than becoming experts in textual criticism just to be sure that you have the best Bible when you already have a Bible that's not only good but perfectly sufficient. But they knew my position and actually asked me to speak about why we can trust the Bible. It was an interesting task to try to do that in a way that doesn't undermine the KJV/NKJV on the one hand or modern translations on the other (because plenty of people beyond myself at that church used translations like the ESV and LSB).

It may not be helpful to anyone, but in case it is, I wanted to post some of my slides from those two talks and give a few main points here.

1. Dunning and Kruger

I began (at the church; unfortunately this part had to be cut for Contend because I didn't have as much time) with explaining the Dunning-Kruger effect, which is named after the authors who described it in this 1999 article, and which Tom Nichols wrote about in his excellent book, The Death of Expertise (which should be required reading for anyone engaging in the TR/KJV issue). In short, when we first start to learn something, we don't know enough to know what we don't know, then there comes a time when we realize how much we don't know (and that can be unsettling), and finally, if we stick with it, we achieve competence. On a chart, these three phases are sometimes called Mount Stupid, the Valley of Despair, and the Plateau of Sustainability (I didn't come up with those names, but they fit). My casual observation is that a lot of the people who 'go wrong' when it comes to manuscripts and textual criticism do so because they get hurt falling from Mount Stupid into the Valley of Despair, so to avoid living in that pain, they climb back up Mount Stupid and build a fortress there. It's not the mountain that hurts, it's the fall. Basil Manly Jr. [The Bible Doctrine of Inspiration Explained and Vindicated] even observed this phenomenon in 1888.


2. Examples of Uncertainties

In the talk I did give a very brief "We have over 5,000 manuscripts" section, but I figure that most people who are coming to an SBC seminary for an apologetics event probably already have a baseline of belief in the Scriptures, so that part wasn't very long. It's probably what they came to hear though; sorry for the disappointment! I think it might be more helpful to dive right in to the uncomfortable part—uncertainties. Nobody likes to be uncertain about God's Word, but because of how God has acted in history, somebody has to sort out the differences among manuscripts, and if we are concerned about this, then we should have an accurate picture of what that looks like and what the degree of uncertainty actually is.

Monday, October 24, 2022

About that Dan Wallace quote

43

The quote

A line from Dan Wallace's foreword to Myths and Mistakes has been making the rounds on the internet, usually in the context of people who want to discredit textual criticism. If you've not seen it, here is what usually gets shared (Update: Thanks to Jeff Riddle, who caught my typos, which I think came from accidentally hitting cmd+x instead of cmd+c when copying the phrase to search on other sites; it has been corrected, as have the mis-phrasing in the first sentence, which I am not sure how I got wrong.):

“We do not have now – in our critical Greek texts or any translations – exactly what the authors of the New Testament wrote. Even if we did, we would not know it. There are many, many places in which the text of the New Testament is uncertain.” —Daniel B. Wallace, "Foreword" to Myths and Mistakes in New Testament Textual Criticism, edited by Elijah Hixson and Peter J. Gurry (Downers Grove: IVP Academic, 2019)
One website has it this way:
The quote according to one website (below a picture of Bozo the Clown).
UPDATE: A coworker of mine found this site down, so here is the site as of July 5th 2021.

In a recent book about the textus receptus, This quote shows up more than once, quoted by contributors Dane Johannsson (p. 112), Pooyan Mehrshahi (p. 174), and Christopher Sheffield (p. 212). In each of the three instances, the contributor gives the Wallace quote [update: "substantially exactly", by which I mean without the context; Johannsson and Mehrshahi add the word "thereof", which is not in the original quote] exactly as I quoted above (Update: the words are as I typed, not in all-caps as the screenshot has them).

This quote—again, exactly as I quoted above—is the very first one given in this list of "quotes that everybody should copy and paste" to try to discredit textual criticism. In fact, when I search that site for the phrase "Even if we did, we would not know it," I get 72 hits.

The quote even gets its very own page all to itself, here (with an interesting URL, I might add). I'm sure there are other examples as well. [Update: the URL has been corrected to give the quote in context.]

If this is all you've heard, it wouldn't be surprising—perhaps you would even be justified—if your reaction was something like this:
A normal Christian, new to textual criticism, hears the scary Dan Wallace quote out of context and reacts understandably.

The context

That sounds scary, but it's rare (if it ever happens) that it gets quoted in context. Here it is; I highlighted in yellow the sentences that you typically don't see when people share the quote—what Wallace says immediately before and after the words that usually get repeated:


Notice Wallace's point: "we also do not need to be overly skeptical." Wallace explicitly rejects "radical skepticism". What exactly, then, is Wallace describing? We can shed some light on that by looking at things he has said elsewhere. When we do, we see that in the spectrum between radical skepticism and absolute certainty, what Wallace is describing is much closer to the certainty end than to the skepticism end (which is near where E.F. Hills lands in the spectrum—like Wallace, Hills also rejects absolute certainty in every place).

E.F. Hills rejects absolute certainty of the text of the New Testament
(Believing Bible Study, 2nd ed. [1977], p. 217)
Hills continues with a statement that I can agree with: "In other words, God does not reveal every truth with equal clearness. Hence in New Testament textual criticism, as in every other department of knowledge, there are some details in regard to which we must be content to remain uncertain. But this circumstance does not in the least affect the fundamental certainty which we obtain from our confidence in Gods special, providential preservation of the holy Scriptures. Through this believing approach to the New Testament text we gain maximum certainty, all the certainty that any mere man can obtain, all the certainty that we need."

To take Wallace in his own words, here he is saying "The New Testament Text in all essentials and in the vast majority of particulars is absolutely certain."
Dan Wallace, saying something that doesn't look like radical skepticism to me.

What about the "many, many places in which the text of the New Testament is uncertain"? That might sound like it is a free-for-all in those places, where anything goes and anything is possible. Is that accurate though? [To be clear, I don't know if anybody made that inference from the quote, but in case they did:]

Here is a recent interview Wallace gave in which he says something that I have tried to point out to people when they ask me about it, and I think Wallace frames it helpfully. Here, he is talking about those places of uncertainty. Wallace says (screenshot and link below):

There's a few passages I could talk about, but understand that scholars have known what is in the original Greek New Testament for well over 150 years, because we have it above the line or below the line. It's not ... like um if you have a multiple choice it's either Text A, Text B, or Text C—it's never Text D—"none of the above." Never.

Wallace appearing on Preston Sprinkle's Theology in the Raw podcast.

I do think it would be helpful if we were more clear about these places of uncertainty—it's never "we have no idea what the original text is." Instead, it's "we are confident that in this place, it's one of these two [or rarely, three] options, but we're not completely sure which one. It can often be as simple as "Did Luke use one word for 'and' or a different word for 'and' here?"

Technical paragraph with examples of such 'uncertainty':
[9 of the 155 split line readings in ECM Acts is the 'uncertainty' between whether δέ or τέ is correct—at Acts 3:10, 12:17, 13:11, 13:52, 14:11, 15:6, 21:18, 22:23, and 24:27, and many others make about the same amount of difference as δέ/τέ. Similarly, 11 of the split line readings in the ECM Mark are transpositions involving all the same words: Mark 2:10, 3:27, 4:41, 5:19, 6:2, 6:38, 13:29, 13:30, 14:5, 15:29, and 15:34. That is to say, if we follow ECM Mark, there are 11 places where we can be sure which words belong in the text though we can't be sure if they should be in one order or a different order. Admittedly, not all of them are this inconsequential, but it would be inaccurate to say that none of them are.]

The problem

Now admittedly, one need not agree with Wallace to represent his own views fairly. One may genuinely think that modern textual criticism leads to radical skepticism in which we can't have any confidence in the NT text (though how many of its actual practitioners think so is perhaps a different discussion). One may not be able to distinguish between 0.1% uncertainty involving a choice between two knowns and 100% uncertainty in which anything is possible. And one might even think that having to choose between two readings where editions of the Textus Receptus differ is somehow categorically different from having to choose between two readings at an ECM split line.

That being said, is it really accurate to represent Wallace's words to mean something he explicitly rejects? What is hard for me to understand is how so many people can fail to mention what Wallace explicitly said, both immediately before and immediately after the section that gets quoted. The problem does seem to be quite pervasive.

When I go back to the website that had 72 hits for the phrase "Even if we did, we would not know it," I get zero hits when I search the words immediately prior ("must be avoided when we examine the New Testament Text"). The same is true of the words immediately following ("But we also do not need to be overly skeptical")—zero hits. Clearly, quoting Wallace in context doesn't seem to matter there.

Not one of the three quotations in the TR book gives the Wallace quote in the context of his rejection of radical skepticism. One even does the opposite: Christopher Sheffield (pp. 211–212) writes:

Daniel Wallace is one of the most prominent proponents of the modern Critical Text. In a foreword to the book Myths and Mistakes in New Testament Textual Criticism, he declares:

We do not have now – in our critical Greek texts or any translations – exactly what the authors of the New Testament wrote. Even if we did, we would not know it. There are many, many places in which the text of the New Testament is uncertain" (xii) [sic]

There you have it. We do not have the whole Word of God and even if we did, we wouldn’t know it. Listen carefully to what he is saying, “There are many, many places in which the text of the New Testament is uncertain.” (emphasis mine). Could there be anything more harmful to the child of God than to have some scholar take a proverbial Sharpie and write a giant question mark over every page of his Bible? That is what the modern Critical Text method does, and it can bear no good fruit in the child of God or in the church of Christ. Such a mindset does not provide patience, comfort, and hope (cf. Romans 15:4), but rather exasperation, anxiety, and despair. It will not produce stable believers with a growing confidence in their Bibles and willingness to labor and suffer for its proclamation, but only the opposite.
[I added the bold for my own emphasis. The italics are Sheffield's.]

Here, Sheffield's remarks seem to be in stark contradiction to what Wallace affirms both in his foreword to Myths and Mistakes and also in his interview that I posted. Admittedly, the interview was more recent than the publication of this book, but in a way that underscores my point—this confidence in the text was Wallace's position back when Sheffield was saying it wasn't. It seems to me that in most cases, the Wallace quote is given to 'prove' that Wallace (and by extension, modern textual criticism) is hopelessly uncertain with an implication that any verse is up for grabs—even though this type of uncertainty is explicitly what Wallace rejects.

In conclusion

1. Dan Wallace gets quoted out of context.
2. Quoting out of context is bad, so we should be extra careful to avoid it.


Final note:
No, Wallace did not ask me to write this. Yes, I do work for him, and I would have liked to get a response from him directly, but he wouldn't, as he typically doesn't respond to things like this. He did read a draft of this post though and agreed with how I represented him.