All posts by David Todd

Almost Done With One More

When July began, I had three book proposals due, based on meetings I had with editors and agents (well, one editor and one agent) at the Blue Ridge Mountains Christian Writers Conference. The one I concentrated on first was the study guide of The Screwtape Letters. I finished and mailed that on July 2. I still haven’t heard back on that, but the Christian booksellers convention took a week out of that editor’s schedule.

The second one I decided to work on was for my baseball novel, In Front Of Fifty Thousand Screaming People. I began working on that parallel to the Screwtape one in June, but had not progressed much. For this proposal, I had some sample chapters writing to do. As I blogged before, I had trouble shifting gears from non-fiction back to fiction. Once I did, I was able to add to the chapters I already had completed, then finish the proposal itself. This all came together last night, when I typed the last edits on the sample chapters. I had typed the final edits on the proposal last Thursday. Now, when I say final edits, that is subject to one more read tonight, with any changes I might see as necessary. So, tomorrow, this will go in an e-mail to the agent who requested it.

Now it’s on to the third one, a Bible study titled The Dynamic Duo: Lessons From The Lives Of Elijah And Elisha. This one will take more work, at least in terms of sample chapters. As I stated before in this blog, I developed these lessons and taught them from March to early June this year. Each week I prepared a two-page student handout, which included comments on the text, sometimes and exercise, lots of maps for understanding, and lots of pictures taken from the web. For my sample chapters, I will have to do away with all the illustrations, and just go with words. So I really have to expand the writing from what I have now. My original goal was to have this one in by the end of July, but that clearly ain’t gonna happen. Maybe the end of August, but that might be optimistic.

Still, I have all the handouts with me today, to look at on the noon hour and decide how much of them I can use, how much I will have to add. It’s a start, and something I’m looking forward to. Though, I will have to change gears back to non-fiction.

Meanwhile, on the first proposal, waiting, waiting….

What I didn’t like about DUNE

The last couple of posts told what I liked about Dune. In this post, I want to say some of the things I didn’t like.

– A little short on back story: I can’t put my finger on specifics, but throughout the book, despite the way Herbert expertly works in back story, I wanted more. A little bit more of how the universe got to where it was.

– Just short on explanation: Many times I felt things happening in the book were not explained as clearly as I would have liked. I felt I lacked understanding on some things, and that was disturbing.

– Pagan-like religions: I am never comfortable reading about pagan religions, or witnessing their rituals, even if only in words. At several points after Paul and Jessica joined the Fremen, Herbert gives us this paganism. I read it, but didn’t particularly like it.

– Barron Harkonnen: He was too much a villain. From his obesity to his evil intents to the implied homosexuality (with that shown in a vile way), he was evil. The best advice I have seen on creating villains is that they must have some redeeming qualities, not be 100 percent evil. The fat Barron was, and that was a negative.

– the emperor’s gambit: I never did understand why the emperor set up Duke Leto, ordering ordering the Harkonnens off the planet then ordering Duke Leto to take over Arrakis, but then aiding and abetting the Harkonnen’s recapture of it. Why? What was he after? Late in the book was a suggestion that Duke Leto was so nice in the way he dealt with subjugated peoples, and he was so effective at training his fighting personnel, that the emperor felt threatened and had to do away with him. Maybe that was it, all of it, but I wish it had been better explained.

– the change in Paul: When Paul had his visions, described as prescient memory, and his personality changed, he was a less-likable character. And less understandable. I could probably write a whole post on this, but I’d have to go back and pick out some specific examples. I’ll just say I didn’t like Paul as much after his change than before.

Well, that’s it for Dune, I think. If you haven’t read it, I suggest reading it. It’s long, and sometimes tedious, but well worth the read.

Still more on DUNE

I’ll continue today discussing more that I liked about Dune.

– Omniscient POV: I mentioned this in one of my mid-way posts. I love the omniscient point of view. This is where the narrator sees everything from the narrator’s perspective, and can get inside the character’s heads to know their thoughts. The omniscient narrator sees what he sees, what each character sees, what each character thinks, and can even tell you what the narrator thinks. Herbert leaves off the latter, but does all the former. In one paragraph he sees what Paul-Muad’dib sees and what he is thinking. In the next paragraph, in the same scene, he sees what Jessica sees and what she is thinking. Omniscient POV has gone out of fashion. At writing classes, new authors are cautioned against using this POV. Go with third-person limited, they say, or even just third person. Too much chance of making a mistake with omniscient.

I just can’t agree with that. Most of the books I have liked–the sagas of Wouk and Michener–are in omniscient POV. To my way of thinking, this gives the reader a richer experience. We are not limited by what one character sees in a scene. We know what all characters see and what all characters think. That’s what I like, and Frank Herbert gave it to me in Dune.

– Violence is downplayed: I am not a big fan of violence, and I hate shoot-’em-up books and movies. In Dune, there is violence, but it is written so skillfully and so downplayed that I almost missed some of it. When Paul and Jessica were captive in a ‘thopter, looking for a way to escape, Paul winds up killing one of their captors. I didn’t realize he had done so until a little later in the scene there was only one captor left. I had to go back and re-read the earlier description, and then I saw it. Maybe I read right through it. Certainly we saw pieces of battles when the Harkonnens returned to take back Arrakis. But to me the violence was kept to a minimum. You knew some of it was going on in the background. It was foreshadowed a lot, but actual scenes of violence were few, and subtly written.

– The spice: Arrakis, as a desert planet, has little value to the universe, except for one thing: the spice, melange. Mildly addictive in small quantities, this stuff can be found on no other planet. Consequently men go to great lengths to find it, mine it, transport it, black-market it, etc. Apparently the giant sandworms manufacture it, though how they do this was not made clear, or at least I didn’t fully get it in the read. It turns the whites of eyes light blue, and the iris/pupil dark blue. At first I thought the Fremen having these eyes was genetic, but by the end of the book I understood it to be environmental, for Paul and Jessica’s eyes were beginning to change after a few years living as Fremem. I’d like to know more about the spice, as I’ll mention in another post.

– Paul & Jessica’s escape: I’m out of time and can’t write much, but this was superbly written. Over several chapters P & J are drugged and bound, taken before the vile Barron Harkonnen, taken off to be dumped in the desert, escape from those guys, are found and helped by Duncan Idaho and Liet Kynes, must go into the open desert again, must dodge sandworms, and eventually must convince a group of forty Fremen they are not enemies to be killed for their water, but friends who need help. Their adventures were a highlight of the book for me.

More coming. Next will be the things I didn’t like about Dune.

More on DUNE

I am at work, intending to write the next post in my review of Dune, but discover I do not have my notes with me. Let me just plunge in then, and do what I can without either the book or my notes at hand.

For today, a few things I liked about Dune

– the desert life descriptions: While Herbert did not go into great lengths to describe the deserts of Arrakis, he did show how the scarcity of water affected everything in that desert world. I loved the concept of the dew harvesters, with their swishing sickle-type contraptions. So effective was Herbert at this, that I cringed when Duke Leto, at his first state dinner on Arrakis, dumped half his glass of water on the floor, and his guests had to do the same. What a waste. I believe Leto was planning on making a point about this in future dinners, but of course never had the chance.

– the Fremen culture: This was another great achievement of Herbert. How much thought he must have given to a people who live in the desert without an oasis, who must dodge monster sand worms and yet do so expertly, who must avoid being enslaved by whatever family currently has the planet as its fiefdom, having developed a culture that accomplishes all of this. Such things as the still suits and tents, the sietches, riding the sandworms, etc. are quite well developed and written. Again, Herbert does not spoon-feed us with elaborate explanations of how this culture came into being. Enough information is given on most of these to understand them from the context.

– reliance on Arabic: Obviously much of the names and terms in the book are derived from the Arabic language, even using directly such words as jihad and hajj in the Arabic meaning. As one who lived five years in the Arab world, and who knows a smattering of Arabic, I found this enjoyable. Some terms, such as the words of greeting (can’t type it in since I don’t have the book here; will edit tonight) are close to the Arabic. I imagine some found this difficult or tedious. I found it enjoyable.

– the downplay of technology: In Dune, the technologies are assumed, not described. Space travel is a given, and no information is given on spacecraft. The ‘thopers, for atmospheric travel, are never really explained. Suspensers, poison snoopers, shields, and many other technological advances that are not in our 21st century world are not explained; they simply are. I found this good. The book was long enough without adding too much explanation of what they are and how they worked. Perhaps this is the way of all science fiction writing. Since I don’t read it much (the last was Isaac Asimov’s Foundation Trilogy and the two sequels back in the 70s), I wouldn’t know. But I liked it.

I am out of time, and probably have a long enough post. I’ll continue soon.

Book Review: DUNE

Dune by Frank Herbert, 1965, The Berkeley Publishing Group, Special markets Hardcover September 2005, ISBN 0-441-01405-4

How does one go about writing a review of Dune? It’s a massive job. I shall need three days to say most of what’s in my head. Imagine, therefore, how much more difficult it was to write the book in the first place. The achievement of Frank Herbert is immense. To create the planet Arrakis, with all its culture based on physical characteristics, and the worlds beyond Arrakis is a staggering work, easily rivaling the achievement of J.R.R. Tolkien.

I began reading Dune on June 15 this year, and finished July 19. As I said in previous posts (here and here), I found the beginning very hard reading. Herbert did not spoon-feed his readers. We have to figure it out from the barest of clues. On the first page I was confronted with the term Kwisatz Haderach, planets Caladan and Arrakis, the Atriedes family, and the curious term “suspensor lamp”. Strange words, strange concepts, hard going. I didn’t realize I had a “Terminology of the Imperium” section in the back. I assumed I had to figure these out from context or later illumination.

The second page presented the gom jabbar, Bene Gesserit, CHOAM, Landsraad, etc. The first five pages, even the first fifty pages, threw up one difficulty toward full understanding after another. I like to understand what I read. If I can’t figure out something from the context or internal explanation, I consult a dictionary, or even on occasion an encyclopedia. But where to go to understand Bene Gesserit? Nothing to do but read on and hope to figure it all out from accumulated context. I did, eventually, stumble on the glossary, and made frequent flips there. It wasn’t the most helpful, but consistent with Herbert’s aversion to spoon-feeding. I read fairly slowly, trying to maximize my understanding. Possibly the need to understand caused me not to focus on some plot elements, or the depth of character development.

Once I was past the first fifty pages, the extent of new terms diminished. Some others started to become familiar. I consulted the glossary less, and enjoyed the book more. The mind fog over Arrakis started to clear (and in so doing, I hope, provided something for the dew harvesters to collect), and the plot stood front and center. About the time Jessica and Paul had to escape from their Harkonnen captors (or were they Sardukuar?) was when I began to see the big picture.

On the next two days–I think; it could take longer–I’m going to cover what I liked and didn’t like about Dune. Today I’ll simply mention that I like the fact the book had no swearing, no overt sex scenes, and little violence. Oh, there were wars, battles, and knife fights, but the covering of this was superbly done by Herbert, such that you almost didn’t know it was a violent scene. The violence was not gratuitous, and the book did not rise or fall on the violence. This, I feel, is a mark of good writing.

So I conclude today by saying put me in the camp of fans of Dune. Some day I will re-read this, and I don’t re-read many books. Thanks to my son for this gift, which has enriched me. More later.

Book Review: The Dark Side of Camelot

I finished Dune yesterday, but I’ll need a few days to write my review; it will probably extend over two or three days. So today I will review a book I finished shortly before starting this blog: The Dark Side of Camelot by Seymour M. Hersh; 1997; Little, Brown and Company; ISBN 0316359556.

I have read much about the Kennedy family: the assassinations, the presidency, the ancestors, and the descendants. There is no shortage of books in this subject, for the Kennedy saga combines much of what made America great: immigration, entrepreneuism, politics. However, as Seymour Hersh reports, a dark side also existed. Past books have touched on this to varying degrees, and most people today who dig just a little bit into the Kennedy story know it is not always pretty.

Hersh set out to focus on John F. Kennedy’s run for the presidency and his time in that office. He begins with recounting events from November 22, 1963. He focuses on what Bobby Kennedy did, how he immediately moved to hide JFK’s private files, put them under lock and key. He hid the president’s medical records, to keep the world from learning just what a physical basket case JFK was. As he says, “But it was the man closest to John F. Kennedy who needed to put aside his grief and begin immediately to hide all evidence of Kennedy’s secret life from the nation–as well as from the new president….” And, “The brothers understood, as the public did not, that they were just one news story away from cataclysmic political scandal.”

Kennedy’s legacy is one of liberal strength, of diplomatic successes, of great speeches and hard work, etc. Hersh is able to pull the mask off the true JFK and unravel some of this unjustified legacy. Most people have heard about his womanizing, but the extent of moral depravity in our 35th president is astounding. After a late start in the Oval office most mornings, Kennedy would eat lunch there when Jacqui was away, then would go to the White House pool for a naked swimming party with some of his aids and White House secretaries. Hersh explain how when Kennedy was on the road, his aide David Powers was responsible for procuring the hookers who would fill the evening for JKF and others. As a consequence, JFK had round after round of venereal disease, and took massive doses of antibiotics, as well as steroids for other ailments.

Hersh does not confine himself to Kennedy’s personal life, however. Clearly documented are: the purchasing of the Democratic nomination in 1960 with the help of the Mafia and Daddy Kennedy’s money; the probable stealing of the election in November of that year; the bumbling approach to State issues, where every action was couched, not so much by what was best for America, but by what was politically expedient; the cavalier attitude to the Bay of Pigs invasion by Kennedy and those around him; the way they (JFK and RFK) almost threw away victory in the Cuban missile crisis; and Kennedy’s true plans for Vietnam. It is all an incredible revelation.

Hersh wrote his book at exactly the right time. The 1990s were thirty years removed from the presidency that the media called Camelot. Many of the people–the little people no one ever heard of, and the aides to aides–who played a part in the presidency were still alive, and enough years had passed that they were ready to talk. Secret service men spoke freely about how they felt about having to stand outside hotel suite doors while the president was consorting with prostitutes. Those involved in various diplomatic “successes” talked about the truth of the crisis and what the Kennedys knew.

The book has some flaws. It is not documented with rigorous footnotes to sources. The end of the book has “Chapter Notes”, wherein Hersh tells of his sources, who he talked with for each chapter, and the nature of what he learned. The way the book is written leads me to conclude it is accurate; I’d just wish he’d have done more footnotes. Then, there is Hersh’s habit of saying, “In an interview for this book in…”. After the first half dozen times we get the picture that he conducted extensive interviews. After 100 times it was annoying. After 500 times….

This is an excellent read. I encourage all to read it, especially if you still believe JFK was a great president.

Sidelines Syndrome

I first encountered Sidelines Syndrome when I was in junior high, a skinny lad who loved both academics and sports but who excelled only at the former and struggled with the latter. I didn’t know what to call it then.

I experienced it mainly on Sundays, in the fall, and it continued strongly all the way through high school. We went to mass at 9:00 AM, and got home around 10:30 AM or a little later. Cereal and toast were consumed, Dad fell asleep either on the dining room floor or in his bedroom, and it was time to read, do homework, or watch whatever pre-game football shows they had on in the 1960s. Eventually the game itself would start. How great it was to watch the New York football Giants, with Y.A. Tittle and later Fran Tarkenton at quarterback, Homer Jones at flanker, and…others whose names I can’t remember. I think Frank Gifford may have already retired. But I prate.

However, by the end of the first quarter, I was tired of watching and wanted to be doing. So I turned off the television, went outside, and started playing basketball alone. Not sure what my younger brother was doing; perhaps he sometimes joined me in the wide part of the driveway, next to the detached, two-car garage, where Dad had put up the hoop and backboard. Within a half-hour, certainly before the end of the first half, my neighbor Bobby, same grade as me, would come out and we’d have a friendly competition. An hour later and we were throwing the football in the street. Other neighborhood kids would join us, and we started a pick-up game in the street. The “field” stretched three telephone poles, the middle pole being the first down. It was always Bobby and me against all the others, all much younger than us. Bobby was Fran Tarkenton and I was Homer Jones. The ten or fifteen kids we played against didn’t stand a chance. But again I prate.

Sidelines Syndrome, as I define it now, is the physical or psychological reaction of body, soul, and spirit to being on the sidelines rather than being in the game. As teenagers, SS caused us to have an overwhelming urge of needing to be in the game, not watching others play the game on television even if they were quantum leaps ahead of us in skill and ability. We had to be out playing, not watching. I’ve noticed that SS has the exact opposite effect on us as we age. Instead of wanting to be in the game, we are glad to be on the sidelines; it lulls us to complacency, tiredness, and an overwhelming desire to sleep through half the game. At least it does me.

Last night, I experienced my first case of teenager SS in years. After working late, I went to Barnes & Noble to read, relax, research, and drink that large house blend that I mentioned in yesterday’s post. I began reading Noah Lukeman’s The First Five Pages. I read about ten pages, then felt an overwhelming urge to be writing instead of reading about writing. I couldn’t concentrate. So I put that down and began reading in The Complete Idiot’s Guide to Writing Poetry. I managed to research one minor topic, then SS interrupted the neurotransmitters and I had to lay it aside. Next was a book about fifty skills a writer should have, or something like that. I couldn’t get past the table of contents. The same was true with “Poets and Writers” and “Writers Journal” magazines. Concentration was impossible. I had to be writing.

So I went home, fixed dinner, went to my reading chair, and began planning out what I think will be my next book, a Bible study, and doing some research on it. SS was satisfied, my brain fully engaged, and productive words and concepts flowed. As the evening progressed and way led on to way, I quit about 1:15 AM, a blog post made and three sell-sheets drafted for three future books. I was satisfied; my brain was satisfied, a teen-age type attack of SS fully suppressed, and a 5:55 AM alarm setting turned on. Hey, maybe I’m getting younger!

Don’t bother to look up Sidelines Syndrome in a medical book, or Google it, or check it in Wikipedia. It doesn’t exist as a clinically defined medical or psychological phenomenon. I assure you it exists, however, and needs to be dealt with in the right way. Maybe this post will spur those professions to get off their duffs and figure this out—quickly. I can’t take many more nights of less than five hours sleep.

Something New

Today I gave the beginning six chapters, thirty-four pages, of In Front of Fifty Thousand Screaming People to my key beta reader. He is not a writer, or a critique group partner, but rather a rabid baseball fan. He read the first two chapters a couple of years ago, and loved it. From time to time he’s pestered me about where the book stood, if I was writing any more. I had to keep telling him no, so far life and other writing projects were in the way. We’ll see what he says about it. I thought of another man I could give these chapters to and see what he thinks about it. I may e-mail them to him tomorrow.

Meanwhile, I worked late tonight (till 6:30 PM) due to having taken time off during the day to run an errand, then went to Barnes & Noble to browse the writing books and magazines. I sat for two blessed hours with three books, two magazines, and a large house blend, and had a wonderful time. I took a few notes from two books of references I will use in an on-line poetry workshop I’ll be facilitating in a month’s time.

But about a week ago, as if I didn’t have enough writing related stuff to do, I began a new project, a new Bible study. I just finished teaching “The Dynamic Duo: Lessons From the Lives of Elijah and Elisha”. This is one of the projects I pitched to an editor at the Blue Ridge conference, and for which he wants a proposal. I have a lot of work to do converting my weekly handouts into passable sample chapters and writing the proposal, but my mind cannot focus on that right now, not until I have the FTSP proposal out the door.

However, I needed a project–something mainly for the future–to fill in the odd half hour when I don’t feel there is enough time to work on one of my major, current projects. Since I co-teach an adult Sunday school class, and it will at some time be my turn to teach again, and since I enjoy developing and teaching my own material rather than something prepared, I’ve been exploring what I will teach next. And, since preparing these studies seems to be something I can do, and something that editors might be interested in, I am approaching this new study with the idea that I will write the whole book before I teach the study, rather than just have handouts and expand them into a book later.

So, I have begun planning a study with the tentative title “From Slavery to Nationhood: How God Used the Forty Years of Wandering”. It will come from Exodus, maybe Leviticus, Numbers, Deuteronomy, and perhaps a wrap-up lesson from Joshua. I’m planning a study that could be taught in from about eight to about sixteen weeks, depending on how a given class wanted to do it. So I’ve read selected chapters in Exodus and Leviticus, and most of the first twenty-one chapters in Numbers. Based on my reading, I already have sixteen potential lessons. I think, by the time I finish, I’ll have about twenty. Then I’ll have to cull out the weaker ones, and begin the actual lesson prep. That’s really the fun part. I get to combine detailed Bible study, research, and writing into one package.

I will probably teach this beginning in January, so I’ve got some time, but not much. Meanwhile, ideas for another umpteen Bible studies are beginning to compete with novels and non-fiction books and historical-political newspaper columns for space between my ears. At least I know ideas are not a problem.

A Productive Evening

My wife is gone again, with our daughter and son-in-law in the big OKC, tending to our grandchild. When she’s gone, I try to maintain our normal routines. I found out I sleep much better that way. So last night, I fixed and ate supper first thing, but instead of then going into the living room to read (as we normally do), I went straight to the computer in the “Dungeon”, as we call our computer room, intending to do some personal business stuff. I found out I couldn’t do the task due to lack of the necessary papers, wasted a bit of time on computer games, and headed back upstairs to read. Twenty pages later in Dune, and I was ready for the Dungeon again.

The project: make some more progress on In Front of Fifty Thousand Screaming People. I had hoped to have the proposal ready to send last Thursday, so I’m obviously behind on my intentions. The actual proposal document is done, subject to tweaking and expansion of the competition section. What I lacked was about five pages of text. I’m supposed to have the first thirty with the proposal, and I only had twenty-five.

Even though I have outlined the book, so that I know the major events that must take place to put my main character into the cross-fire at the World Series (more on that someday, perhaps), I have not outlined it to the point where I know each scene. Those are coming as I get the inspiration, still switching gears from non-fiction to fiction. I have two scenes out of sequence, later in the book, mostly finished, but I needed that next chapter, that next scene, to have the full thirty pages to send. Plus editing, of course.

Last night I couldn’t seem to concentrate on the task at hand. I got some other things done, such as filing, organization, reading writing blogs, re-read the last chapter in sequence and did a few edits. But what to do with that elusive scene wouldn’t materialize. Should I switch to one of the Mafia Dons, and have them going through the routines of business? Should I do a scene at the farm in Kansas, how the family was reacting to Ronnie’s success? Or should I do another baseball scene? None of these seemed right at that point in the story. I thought of scenes later in the book I could work on, but that wouldn’t get me where I needed to be as soon as possible. Was this my first case of writer’s block? Computer games became a diversion.

Then, about 10 PM, the perfect next scene hit me. I’ve been intending to have Ronnie, the main character, interact with a reporter for the Chicago Tribune, a man I’d introduced briefly in the second chapter. Why not have their first one-on-one interview now. I was immediately taken to the Tribune newsroom, to the sports desk, where John Lind was trying to figure out how to interview the farm boy cum pitching sensation, and pounding keys.

At midnight, I had an almost finished Chapter 6, and was up to thirty-one or thirty-two pages at the start of the book. That put me way, way out of routine, for I don’t normally go to bed that late. When I went upstairs and to bed, my mind was full of plot and dialog, and no way could I sleep. Twenty minutes later I got up and went to my reading chair. I couldn’t face another chapter of Dune, so I wrote some in my journal, then picked up my Bible and read in Numbers, deciding on the next two possible lessons in my desert wandering Bible study. The words on the printed page were big and bold, the way they always are when my mind is sharpest. How could this be, a sharp mind at 1:30 in the morning? Nevertheless, I had a great time until tiredness came over me in waves about 2:00 AM.

I used to think my most creative time was between 10 PM and 2 AM. Years ago this manifested itself in solving all kinds of engineering problems I took home with me. Then the routines of life crept in, and I no longer worked on creative things at those hours. Is a change coming? Stay tuned.

When friends fall out

In my continuing (and slow) reading of John Wesley’s letters, I came today to his April 27, 1741 letter to George Whitefield. Whitefield was in Georgia, America, and has written Wesley on December 24, 1740, a letter that appears to have been critical of a number of things Wesley was doing: handling money, deeds for properties, ‘adornment’ of sanctuaries. Most important, however, seems to have been the growing rift between the two over doctrinal issues. Wesley was an Arminian and Whitefield a Calvinist concerning the issue of the permanency of salvation.

This difference must have been under the surface, or seemed unimportant, as the two began the great work of the revival. Certainly, it is hard to imagine Whitefield begging Wesley to come to Bristol to substitute for him in a revival that was breaking out there (Whitefield having to be elsewhere) if he thought Wesley to be in error in his doctrine. I just now found Whitefield’s letter on line, but have not yet read it. It contains five main points spread out over twelve pages of twelve point font, so it looks like I have lots of interesting reading in the days ahead. I will likely add this to the Wesley letters book, so that I have the full impact for when I read these again, perhaps in a decade or two. Apparently, Whitefield had the letter published in London, with a wide distribution.

Whatever their differences, and whoever was at fault, I’m saddened to see these two giants of the faith have a falling out. Somehow we have to make room in our hearts for those who interpret the gospel differently than we do. For Whitefield to have said Wesley preached a different gospel, and so they could have no fellowship together, seems extreme.

When Paul and Barnabas had their famous falling out, the result was the work was multiplied: two missionary teams went out, with more workers, than would have happened had they stayed together. Later in life, these two giants of the apostolic church were reconciled in friendship. Their dispute was over administrative issues, not doctrine, but still, could not Whitefield and Wesley have looked to their example? Well, maybe they did, sort of, for they divided their efforts.

I have much more to read on this, and possibly will come back and modify this post or make another.