Dr No - a BBC Radio drama

Based on Ian Fleming’s novel, BBC Radio 4’s Dr No stars Toby Stephens as James Bond and David Suchet as Dr Julius No

I grew up on radio dramas—mostly religious ones like “Adventures in Odyssey” or “Patch the Pirate” or, when, to my grief, I woke up in the deep watches of the night with WRAF on my clock radio, the harrowing “Unshackled”—and have enjoyed rediscovering them as an adult and a father. My own kids are getting to know the town of Odyssey’s large cast of characters, and we especially loved “Odyssey”-veteran Paul McCusker’s joyous and intelligent radio drama The Legends of Robin Hood.

But BBC Radio’s literary adaptations have become particular favorites of my family. We’re a third of the way through their classic Lord of the Rings starring Ian Holm, and we have enjoyed their radio adaptations of Treasure Island and the Richard Hannay adventures The Thirty-Nine Steps and Greenmantle. And there is a great favorite among my kids, The Mark of Zorro, starring Val Kilmer, which I reviewed here a year ago today. Last weekend, I finally delved into their James Bond series.

The first in this series adapts—like the first Bond film—the fifth of Ian Fleming’s original novels, Dr No.

Dr No takes place several months after From Russia With Love, which ends on a stunning cliffhanger requiring Bond, in the followup, to have undergone extensive convalescence. The radio drama opens with Bond’s briefing from M, who wants to make sure Bond is fully recovered but still gives Bond what he thinks will be an easy assignment. One Commander Strangways, a key intelligence operative in Jamaica, has gone missing along with his secretary. The gossips have already concluded that the pair created false identities for themselves and eloped, but M wants Bond to make sure.

Bond departs Britain both relaxed and resentful. He is glad to be back in the Caribbean and working with a Jamaican local, Quarrel, who gave him life-saving assistance in Live and Let Die, but his familiarity with Jamaica and his resentment of the simple job given to him by M cause him to let his guard down. He immediately regrets it. A Chinese girl claiming to work for the Daily Gleaner snaps his photo as he arrives at the airport, and reappears when he and Quarrel have dinner and drinks at a Kingston dive. His suspicions are aroused and never allayed.

Bond encounters another Chinese girl working as a secretary for a local contact. The contact informs Bond that Strangways had been investigating one Dr Julius No, the reclusive owner and operator of a guano mine—which he works exclusively with imported Chinese labor—on nearby Crab Key. Asked to retrieve the files on the case, the secretary reveals that they are missing.

Though Quarrel warns him off of approaching Crab Key, which has a bad reputation—especially after a series of strange accidents involving representatives of the Audobon Society, who have taken an interest in the rare birds that nest on Dr No’s island—Bond decides to investigate more directly.

Quarrel and Bond make the 20-mile voyage to Crab Key by night and, the next morning, meet Honeychile Rider as she gathers shells on the beach. When Dr No’s men arrive and machine gun Honey’s canoe, the three form an ad hoc team as they work both to uncover what Dr No is doing and to survive long enough to escape the island. Not all of them will make it, and the danger will only grow crueler and more grotesque once Dr No captures them.

BBC Radio 4’s adaptation, first broadcast in 2008, hews very closely to Ian Fleming’s novel, even retaining many of the rough edges I would have expected to be sanded off in a modern adaptation—and kudos to them for letting the story be of its time and place. Sticking close to Fleming’s originals is always a plus. Dr No has always impressed me with its strong writing, characterization—especially for Honey Rider—suspense, and grim, brutal survivalist climax. Take what you imagine a Bond film to be like, remove the campiness of the worst of the movies, and cross it with The Most Dangerous Game, and you’re approaching the tone of this book. The adaptation conveys Bond’s doggedness and Dr No’s cruelty expertly, and the story builds steadily in excitement and intensity right up until the end.

The voice acting is excellent across the board. Toby Stephens, who played Bond villain Gustav Graves in the execrable Die Another Die and gave an outstanding audiobook performance of From Russia With Love, is very good as James Bond. Stephens’s Bond combines intelligence and a hard edge where screen Bonds often skew toward one or the other. Lisa Dillon and Clarke Peters offer solid support as Honeychile Rider and Quarrel—Quarrel and Bond’s strong laird and gamekeeper relationship is an often overlooked friendship in the Bond stories—and fans of certain British media will enjoy Peter Capaldi’s brief appearance as The Armourer, Major Boothroyd, the character who first equipped Bond with the Walther PPK and who eventually evolved into the films’ Q.

The standout, however, is David Suchet as Dr No. The villain only appears in the film third or so of the story and has limited “onscreen” time with Bond, but Suchet makes the most of it. His halting, metallic, alien voice is eerie and threatening, and the way he delivers his life story and cold, amoral, transhumanist worldview to Bond and Honey seems believable rather than the mere “monologuing” lampooned in The Incredibles. If, like me, you know Suchet primarily as Poirot, this performance should prove a startling surprise.

Dr No also features good sound effects that set the scene well, especially scenes on the beaches, in the mangrove swamps, and in the warehouses, subterranean quarters, and deathtraps of Crab Key. The adaptation’s original music by Mark Holden and Sam Barbour is a nice accent to the story, invoking the sound of classic Bond film scores without aping it.

For those with children, Dr No may be on the intense side. I listened to it with my kids and they were engrossed by it, finding the story unbearably suspenseful and Dr No unbearably creepy. I selected this one to listen to with them both because it was the first in this series and because I knew the novel had more action and less sex than some of the other stories. That held true for the adaptation, too. Aside from a scattering of mild language—most of it rather blunt discussions of Dr No’s bird guano—it was a good listen for my kids.

If the adaptation has any flaws, it is only through sins of omission rather than commission. This radio drama is just under ninety minutes long, and so while all the major events of the novel are present, they have been streamlined. The novel’s characters are presented well and excellently performed, but some of the depth of the novel has been lost. Bond’s resentments and his interiority are downplayed. Honey tells a shortened version of her tragic backstory—which I wrote about briefly a few months ago—but her goals and her reason for being on Crab Key are not elaborated upon. Likewise, I know why Bond was in the hospital for so long before the events of this story, but someone less familiar with the novels may not. I had to explain a little bit of that to my kids. But these are minor complaints.

The upside of this short adaptation is precisely that it is short—right at an hour and a half, an hour and a half spent on a perfectly paced and executed action-suspense story, perfect for a shorter holiday road trip or a quiet evening listening to the radio.

I had heard lots of good things about these radio adaptations of Fleming’s novels, and now I know why. I’m looking forward to listening to the next in the series, the 2010 dramatization of Goldfinger, starring Stephens as Bond and Ian McKellen as Auric Goldfinger. You can listen to Dr No, Goldfinger, and the rest of the series in this YouTube playlist.

If you’re traveling over the holidays I hope BBC Radio 4’s Dr No will give y’all a good hour and a half of thrills, and that you’ll go on to listen to more, as I plan to. Even better, read some Ian Fleming in the new year! Regardless, have a merry Christmas, and thanks for reading.

Five years of blogging

Today marks the fifth anniversary of this blog. Five years—half a decade—does not amount to much in the end, but this website and blog began in a time that now feels utterly remote to me. I had just started a new job, my first full-time teaching position, and was getting used to a commute I could now do in my sleep. Sarah and I only had two kids, one only a few months old. We weren’t quite aware of it just yet, but we were outgrowing our apartment. And the year before, I had self-published my first novel and a novella I had whipped up in two weeks. There was kind enthusiasm among friends but few sales.

I created this website to coincide with and, hopefully, help promote the release of Dark Full of Enemies, a novel which had itself lain dormant for almost five years, from its completion just before Sarah and I got married until that winter of 2017. I had written but not yet finished revising Griswoldville, and I hoped a website would help with that project, too.

It may surprise y’all, now, but I almost deleted the blog option when I first started building this site. I had even scoffed when I saw it on the default version of the template. Thanks, but no thanks, had been my attitude. I don’t want to get fired for something I write there. And who reads blogs, anyway?

But I hesitated. I had run a blog in college, one of those free blogging sites that one now only encounters in the dirty alleys and out-of-the-way park benches of Google searches, and I had found it great fun. This remembrance also brought to mind the diary I had kept for four or five years, daily from January of 2008 through most of grad school, then sporadically, catching up when I missed days here and there, and finally sputtering out sometime in the years between grad school and marriage.

What that Blogspot page and the diary had in common, though, that made me hesitate to write off blogging on this new site, was practice—both in the sense of training and in the Alasdair MacIntyre sense of a life-shaping routine. A regularly maintained blog is good practice.

When I had kept that blog during and just after college, I had also produced one almost complete World War II novel as well as the manuscript that became No Snakes in Iceland. When I had kept that diary, I had also finished No Snakes in Iceland, put it through its first rounds of readers and revisions, and written the rough draft of Dark Full of Enemies. Habitually writing something, I decided, would prepare me for the day I need to write the important thing.

And so here I am.

I have no regular schedule and no real plan. I just know that I need to write here occasionally, often enough to keep limber, the same way I need exercise. (More than ever, in fact.) Five or six posts a month feels, to me, like I’m staying on track. And I have no set topic. This blog, to borrow a concept from Alan Jacobs, whose blog I regularly read, is a commonplace book, and so whatever catches my eye, interests me, irritates me, makes me stop to think, or that I enjoy and want to tell others about may wind up here.

So now, half a decade after launching this blog, my wife and I have three kids, we live in a house in a slightly more country part of a crowded county, I have published two more novels and yet another is going through the usual cycles of hibernation, reading, and revision—and I have hundreds of posts here. (I have the specific number written down in my office at school, and am now on Christmas break. Excellent foresight.) These have been fun to write—good practice, just as I’d hoped, as well as a place to ruminate and occasionally just vent—and have connected me to some good people whom I might never have “met” otherwise. I am deeply grateful.

A few statistical giblets for those of y’all who are interested:

Traffic to my site, most of which goes to the blog, has steadily increased every year since I started. In 2019, with two years to get established, the site got over 6,700 distinct visits. In 2020 that nearly doubled to over 12,500. In 2021 it doubled again: 25,390. And already this year, with a couple weeks to go, it’s received 36,000. Pageviews are even higher, though I am no web analytics expert and can’t tell you much of what this signifies. Now all I need to do is turn this traffic into book sales!

At any rate, the website and blog have served their purpose: I am getting practice, and people are reading and, occasionally, seeking out and buying my books. And I’m most thankful for that.

Again, I’m thankful for those of y’all who regularly read what I post here, especially considering what an idiosyncratic jumble of topics it must seem to be, and thanks most of all to those who have reached out over the years. Hearing from y’all has been an encouragement, a fun source of conversation, and it has made me a better writer. Just last week one of y’all caught a glaring error in my post about run-on sentences, which I was able to fix—or at least slap a Band-Aid on.

I’m looking forward, God willing, to five more years of writing practice here! Thank y’all for being here, and thanks, as always, for reading.

Deception in the name of crisis management

Last week I finished reading Sean McMeekin’s mammoth study Stalin’s War: A New History of World War II. It’s a weighty book in both senses, by turns overwhelming, depressing, and infuriating. I may or may not write a full review here, but it will certainly be in my year-end reading recommendations. For the time being, here are two passages quoted by McMeekin that struck me pretty forcefully, which I present with a minimum of context and comment.

The first comes from Nikolai Verzhbitski, a Russian journalist who recorded the following in his diary on October 18, 1941, when the Germans had advanced to within a hundred miles of Moscow from the both west and the south. Verzhbitski describes a Moscow prostrated by the invasion:

Who gave the order to close the factories? To pay off the workers? Who was behind the whole muddle, the mass flight, the looting, the confusion in everyone’s minds? . . . Everyone is boiling with indignation, talking out loud, shouting that they have been betrayed, that “the captains were the first to abandon ship” and took their valuables with them into the bargain. People are saying things out loud that three days ago would have brought them before a military tribunal. There are queues: noisy, emotional, quarrelsome, agonising. The hysteria at the top has transmitted itself to the masses.

That’s the crisis and the way the leadership botched it, and, according to Verzhbitski, the people saw clearly the many ways in which their leadership failed them:

People are beginning to remember and to count up all the humiliations, the oppression, the injustices, the clampdowns, the bureaucratic arrogance of the officials, the conceit and the self-confidence of the party bureaucrats, the draconian decrees, the shortages, the systematic deception of the masses, the lying and flattery of the toadies in the newspapers. . . . People are speaking from their hearts. Will it be possible to defend a city where such moods prevail?

This kind of deception, as it turns out, is contagious, and at least some people were alive to that fact. McMeekin quotes an address from Senator Robert La Follette Jr delivered on June 23, 1941, the day after the beginning of Operation Barbarossa:

[I]n the next few weeks the American people will witness the greatest whitewash act in all history. They will be told to forget the purges in Russia by the OGPU, the persecution of religion, the confiscation of property, the invasion of Finland and the vulture role Stalin played in seizing half of prostrate Poland, all of Latvia, Estonia, and Lithuania. These will be made to seem the acts of a “democracy” preparing to fight Nazism.

Amnesty for Stalin, perhaps? “Let’s acknowledge that [he] made complicated choices in the face of deep uncertainty.” That was more or less the Roosevelt approach, anyway—minus any acknowledgement.

McMeekin also charts the consequences—in the United States!—of criticizing Stalin and the Soviets: purges in the federal bureaucracy, often conforming to enemies lists provided by the Russians; the replacement of diplomatic and military leaders with either Roosevelt lackies or actively pro-Soviet agents; the burial or rewriting of inconvenient reports; official coordination with the press to suppress damaging stories, smear dissenters, and spread Soviet spin; and, of course, widespread, purposeful deception. All in order to win the war, of course.

The more things change. And, of course, Verzhbitski’s concluding question remains pertinent.

The passage of Verzhbitski’s diary quoted by McMeekin comes from Moscow 1941: A City and Its People at War, by Rodric Braithwaite, who quotes the diary at greater length. La Follette’s speech was reported in the New York Herald Tribune’s June 24, 1941 issue, which I haven’t been able to access (for free) in full.

Frozen II’s big dam problem

Runeard’s Dam in Frozen II

This month Before They Were Live, a Christian Humanist Radio Network podcast covering every film in the Disney animated canon in chronological order, finally reached Frozen II. Or, as my kids used to call it—with unwitting accuracy—Frozen Number Two. Hosts Josh and Michial have a great discussion about the film’s strengths and its many, many shortcomings, but there’s one aspect of the film I’m going to take this sliver of an excuse to vent about—the dam built by Anna and Elsa’s grandfather.

Having a daughter who was four when Frozen II came out (so you know where I was opening weekend), having watched it far too many times since, and—the sticking point for me—having once written a book about destroying a dam in Norway, I have thoughts.

Frozen II’s dam was built as “a gift of peace” to the Northuldra people, the film’s thinly-disguised Sami, who live in the Enchanted Forest, a region both far, far away (i.e. a couple hours’ walk) from Arendelle and near enough to be at the head of the same fjord. Over the course of the film, Anna and Elsa learn that the dam was actually a Trojan horse attack on the peaceful Northuldra because of their grandfather’s wicked suspicion of magic-practicing peoples. The dam has, somehow, shrouded the Enchanted Forest in an everlasting fog. Only destroying the dam will dispel the fog and make things right, but doing so will also unleash a torrent of water that will destroy Arendelle. It’s a social justice trolley problem.

So—what’s been bugging me since that Saturday morning three years ago:

First, what is this dam doing? People don’t just build dams for fun. The Frozen movies apparently take place in the early 1840s, so this is too early for the dam to provide anyone with hydroelectric power, but it also doesn’t seem to be providing anyone with hydraulic power, either. Even if that was the intention, it’s too far away from Arendelle to do them any good. Flood control is the most plausible reason, but even this is a stretch given the environment. As for the recipients of this dam, the Northuldra are reindeer herders—why give them a dam at all? And even if it was offered, why would they accept?

Beyond serving no obvious purpose, Frozen II’s dam doesn’t even function like a dam. The water of the deep lake behind it does not apparently flow over the dam—or anywhere else. Having no hydro station, it doesn’t even have intakes that could redirect the water through the cliffs to the valley below the dam. Here’s the dam that I scaled up in imagining the Grettisfjord dam in Dark Full of Enemies. Look at it on Google’s satellite view and you can see on the right, the southeastern side of the lake, the intakes for the pipeline to the power station downriver. Frozen II’s dam is just a literal wall plopped in the wilderness that created a lake that somehow just sits there.

In Before They Were Live, Josh and Michial hesitate to fault Frozen II for sloppy storytelling, but I am less inclined to be charitable. The dam makes it clear that the story is secondary to the politics. It is a symbol and only a symbol. It has to be there so it can be destroyed, just like the Northuldra have to unnecessarily accept the gift of useless infrastructure so they can be haplessly victimized. And all of this has to happen so that the audience can vicariously grieve over generational injustice and accept that the cost of Doing Better is utter, year zero, civilizational destruction.

And that brings me to my biggest problem with Frozen II on this score: the seemingly minor detail that man-made lakes can be drained. The lake could be drained, the fog dissipated, the dam demolished bloodlessly, in controlled conditions that would not annihilate everything downriver. (Seriously, read about dam failures, both unintentional—here’s one from my neck of the woods—and otherwise. Anna might as well atone by nuking Arendelle.) The destruction at the end of the film—which is prevented by a deus ex machina anyway, because all recent Disney films toothlessly refuse to follow through on their own logic—is completely unnecessary.

Josh unfavorably compares Frozen II to other, better films’ “fairy tale logic,” arguing that Frozen II lacks it. He’s right. Frozen II’s story is governed by Jacobin logic. Bolshevik logic.

I’m only half kidding, and only barely overstating it. Regardless of whether you agree with the politics or not, this is bad storytelling. Fortunately—since I do not agree with the film’s politics—the storytelling is so bad, the plot is so slipshod and scattered, and the climactic action so blunted in its effect on the characters, that few people who are not already ideological fellow travelers will end the film having had some kind of awakening. But, Lord knows, I could be wrong.

I’ve embedded the latest episode of Before They Were Live in this post—give it a listen! And I highly recommend subscribing to the show. Josh and Michial bring great dedication and insight to the show, and their discussions always maintain a high standard. Though I wouldn’t call myself a Disney enthusiast by any means, each new episode sidelines whatever else I’m listening to. I think y’all will enjoy it, too.

You can visit the show’s official website here and the Christian Humanist Radio Network’s main page here. The CHRN also has a Facebook page which you can like or follow for regular updates on all of their shows.

What run-on sentences are (and aren't)

Back in January I grew sufficiently annoyed with misunderstandings of what passive voice is to write about that here. Now it’s December and as the result of a more recent irritation I’m bookending 2022 with another post on misunderstood grammar, this time concerning a much rarer creature from the bad writing bestiary.

In the “Dumb Sentences” segment of a recent episode of 372 Pages We’ll Never Get Back, a bad books podcast hosted by Mike Nelson of “Mystery Science Theater 3000” and Conor Lastowka of RiffTrax, a listener submitted the following sample from the show’s current read, a cozy mystery called Murder in Christmas River:

But then, a pickup truck pulled up, and a boy got out and pulled his guitar from the flatbed, and he walked over and sat down, and mesmerized everyone there with his playing and singing.

The listener who mailed this sentence in criticized it as a self-evidently ridiculous “run-on sentence.” The writing is inelegant, inconsistently punctuated, and somehow both vague and very specifically cliched, but this is not a run-on sentence.

What a run-on sentence is

A run-on sentence is a fusion of two independent clauses, clauses that could stand on their own as sentences, into one sentence with no division between the two clauses. Some further explanations:

• From Grammarly: “Run-on sentences, also known as fused sentences, occur when two complete sentences are squashed together without using a coordinating conjunction or proper punctuation, such as a period or a semicolon.”

• From UNC Chapel Hill’s Writing Center: “These are also called fused sentences. You are making a run-on when you put two complete sentences (a subject and its predicate and another subject and its predicate) together in one sentence without separating them properly.”

• From the University of Michigan’s Sweetland Center for Writing: “A run-on sentence is two or more independent clauses incorrectly presented in a single sentence.”

A run-on sentence is not

• Any long sentence.

This is much simpler to explain than the many things people mistake for passive voice, because the one thing people commonly mistake for a run-on sentence is a sentence that, to them, subjectively, just goes on too long. Because it runs on, you see.

But that’s not why the run-on sentence has that name. The mental image conjured by “run-on sentence” should be more like the head-on collision of two trucks than someone wheezing his way through a marathon.

Here are a few things that I’ve seen called run-on sentences that are not:

The opening paragraph of “Great Caesar’s Ghost,” Kevin D Williamson’s marvelous takedown of an annually observed imperial spectacle here in the US:

The annual State of the Union pageant is a hideous, dispiriting, ugly, monotonous, un-American, un-republican, anti-democratic, dreary, backward, monarchical, retch-inducing, depressing, shameful, crypto-imperial display of official self-aggrandizement and piteous toadying, a black Mass during which every unholy order of teacup totalitarian and cringing courtier gathers under the towering dome of a faux-Roman temple to listen to a speech with no content given by a man with no content, to rise and to be seated as is called for by the order of worship—it is a wonder they have not started genuflecting—with one wretched representative of their number squirreled away in some well-upholstered Washington hidey-hole in order to preserve the illusion that those gathered constitute a special class of humanity without whom we could not live.

This is all one long, elaborately structured sentence—especially in its second half, with parenthetical interjections and dependent clauses—but it is grammatically correct. (Subject: State of the Union. Verb: is. Predicate: all the rest.) It is not a run-on sentence.

Occasionally people mistake a sentence as a run-on not because of its length but because of a stylistic choice, such as Cormac McCarthy’s use of polysyndeton—the repeated use of conjunctions like and, especially as a substitute for commas. Here’s an example pulled at random from McCarthy’s novel Blood Meridian:

The last one fell in a doorway and Tobin turned and drew the other pistol from his belt and stepped to the other side of the horse and looked up the street and across the square for any sign of movement there or among the buildings.

Here’s another from earlier in the book:

They posted guards atop the azotea and unsaddled the horses and drove them out to graze and the judge took one of the packanimals and emptied out the panniers and went off to explore the works.

Again, these are all long sentences that could be broken up into separate ones, but they are joined grammatically correctly with a conjunction. This is a stylistic choice, not a mistake. To break these sentences up would be to lose their tonal effect, one of both busy movement, solemnity, and distance.

I think the author criticized in the listener e-mail to 372 Pages was straining for this effect—a more artistic way to suggest a boy’s activities over an entire evening. It was not well done but not that badly done either, and the author certainly did not commit the catastrophic grammatical blunder of writing a run-on sentence.

Actual run-on sentences

Real run-on sentences are not a matter of stylistic difference or minor mistakes, like spelling errors or typos, but a grotesque mashing together of two sentences that produces obviously wrong grammar. I use the word obviously deliberately. You can dither about stylistic choices all day but there is no mistaking a run-on as anything but an error.

The run-on is such an elementary mistake that I actually had a hard time finding mentions of it in my books on writing. Even the classic, Strunk and White, only mentions the comma splice (see below). But the run-on is covered thoroughly in a lot of writing aids for students, like that UNC guide I linked to above. Here’s the example provided there:

My favorite Mediterranean spread is hummus it is very garlicky.

Here’s one from another university writing center:

Raffi sings upbeat children's songs he is an excellent musician.

Anyone reading these sentences would immediately see the mistake.

As a result, it is exceedingly rare to see an actual run-on sentence in professionally published writing. But they are rife in informal writing, especially—speaking from my own experience—student writing.

Here’s an exmample of a run-on sentence I recently spotted in the wild. This comes from a letter by Maria Clemm, Edgar Allan Poe’s beloved mother-in-law, recounting his last words to her as he left on a business trip from which he never returned:

God bless my own darling Muddy do not fear for your Eddy see how good I will be while I am away from you, and will come back to love and comfort you.

This is three sentences fused into one, but I think anyone would be forgiving of an old lady writing a personal recollection by hand in an era in which letters were not held to the same standards of punctuation (or even capitalization, as in this letter by Thomas Jefferson) as published writing. But in rare cases real run-on sentences do show up in modern, professional writing.

The run-on’s more respectable cousin

Let me pause here to note the existence of the comma splice, which makes almost the same mistake as the run-on sentence but separates the two clauses with a single comma, like this:

Greg Maddux played for the Braves for elevens seasons, he was one of their best pitchers.

The comma splice is sometimes conflated with the run-on (as in Dreyer’s English, where he treats them as the same thing), but I learned them as separate mistakes and I’m going to stick with that. My reason: comma splices can sometimes work as a stylistic choice (see the quotation from Garner’s Modern English Usage here), but a run-on is always a mistake.

Identifying and fixing run-on sentences

To return briefly to what a run-on sentence is, it is not just a long or grammatically complex sentence, but will have:

• two or more independent clauses and

• no conjunction or separating puncuation.

The result, as I’ve tried to emphasize, is obviously incorrect. Real run-on sentences sound childish. When you run across one or, God forbid, accidentally write one, identification is not usually the problem. (Misidentification is, which is why I wrote this.)

Fixing them can be relatively easy, depending on how much you care about style. The two simplest mechanical fixes are:

• Sticking a semicolon between the two clauses. Like Cormac McCarthy, I hate semicolons and would prefer two separate sentences to the unholy hybrids created by this punctuation, but separating the clauses this way is grammatically correct and a legitimate option.

• Breaking the clauses into separate sentences. My preferred solution, but one that—again, if you care about style and sound—might turn a run-on into a pair or string of equally childish-sounding simple sentences.

After choosing either of these solutions you can go on to weigh the stylistic choices and all the wonderfully complex artistic questions they raise—sound, tone, structure, rhythm, connotation, and on and on. You may end up reworking an entire paragraph, or more. But sometimes, as anyone who drives an older car will understand, just getting the obvious mechanical problem fixed is the most important step.

Conclusion

My main problem with run-on sentences is not the error itself, which, as I’ve suggested above, is 1) easily indentifiable and 2) easy to fix. My main problem with run-on sentences is the term itself. “Run-on sentence” is misleading, suggesting to many people for a long time that any long or complex sentence is somehow a mistake, and I wish there were a more precise term for this elementary error. Perhaps “fused sentence,” the alternate term used in a few of the definitions I quoted earlier, is the best candidate. It certainly suggests what the actual mistake is with more precision than “run-on.”

But until a term like “fused sentence” or something else can displace the one we’re most familiar with, I hope this will be a helpful guide to what a real run-on sentence is, and that people will go easier on authors who try something a little different and come up a little short.

Missing the point

Or, “Inadequacy of response revisited.”

Ben Sixsmith, a young British writer and a contributing editor of The Critic whose work I enjoy, recently published an interesting review of a new book on “Self-Injury as Art and Entertainment” in the Washington Examiner. This ostensibly academic study includes a chapter on “Jackass,” a show that apparently “takes aim at America.” I’m guessing it also does a lot of “calling into question” and, especially, “interrogating.”

The less said about the state of academia, the better, perhaps, but the book’s “opportunistically ideological” section on “Jackass” is where Sixsmith zeroes in. Having noted that the author suggests that the show’s self-inflicted comic violence is some kind of reaction to “the contextualizing bleakness of America” post-September 11th even though “Jackass” premiered in 2000, Sixsmith makes a more broadly applicable point:

It might seem peculiar to take an analysis of an obscene stunt show quite this seriously, but the point I am prowling toward is that intellectual analysis of pop culture that purports to expose its hidden aesthetic or social relevance often misses the point on the most basic level. Writers would never get away with saying The Waste Land was inspired by World War II, but the lofty heights from which they judge more unsophisticated entertainment allows mistakes to sit unnoticed.

The charge of “politicization” is often philistinic. All culture can have political or at least social implications. When culture is assessed through a specific political lens, though, it can diminish rather than expand its significance.

Coincidentally, this morning a friend passed along this video essay on antiwar filmmaking and the new adaptation of All Quiet on the Western Front. It compares 1917 unfavorably to the new All Quiet because it is not bleak or nihilistic enough to get an antiwar message across but does so without stopping to consider whether that was actually the point of 1917.

You might recognize that this is similar to Slate’s accusation in 2020 that, by not explicitly sermonizing against nationalism, 1917 was an “irresponsibly nationalistic” film. As I wrote then:

These are manifest absurdities, but are apparently what Slate writers and their ilk want out of a movie like 1917. Tell us how bad the British officer class was. Don’t other the Germans. Don’t “validate the nationalist impulses that led to such terrible bloodshed.” Don’t give us a movie, give us a disquisition. Give us a sermon. Give us a Slate article.

All of which cheapens or, in Sixsmith’s well-chosen words, diminishes the story and its power.

See again my remarks on inadequate political or ideological responses to art from a couple of months ago. Or go, as is always recommended, to Chesterton: “Missing the point is a very fine art; and has been carried to something like perfection by politicians and Pressmen to-day.”

Notes on rereading Storm of Steel

Ernst Jünger as a Private early in the war, as an Iron Cross recipient in 1916, as a highly decorated officer wearing his Pour-le-Merite postwar, in 1920

Last week I ran across the following meme. It perfectly captures the chief contrast between two of the great authors produced by the First World War—Erich Maria Remarque, author of All Quiet on the Western Front, and Ernst Jünger, author of Storm of Steel—as well as the perspectives of their books:

I laughed, of course, and gleefully reshared it with the caption “I never get tired of recommending Jünger to students precisely because they aren’t prepared for this.”

The “this” being the fundamental mismatch between what they expect thematically, didactically, from a harrowing war story and what they actually get from Storm of Steel. They’ve all gotten the canned antiwar messaging of high school reading lists (All Quiet being one of the books that created the template for a genre that hasn’t changed much in a hundred years), and have absorbed the structure or arc of any basic antiwar story without even realizing it.

But here’s a memoir, I tell them, in which the author essentially spends 300 pages telling you: The war was a continuous, 24/7, 365-day-a-year horror show. It was terrible from beginning to end. It was hell. And I loved it.

They don’t know what to do with that. And yet they always end up responding strongly to the long excerpt I have them read from the chapter on Guillemont.

But beyond being amusing, this meme got me wanting to reread Storm of Steel, something I’ve been intending to do for years. So the day I ran across this, I got exactly that edition* off my shelf and started reading. Four days later, I had already finished.

The following isn’t exactly a review, more a series of notes or observations as I reread it all the way through for the first time in ten years.

Tone

The most striking thing about Storm of Steel is its tone. I say striking because it takes hold of the reader immediately and strongly affects him all the way through—and yet it is difficult to describe. Google Ernst Jünger or Storm of Steel and take a few minutes looking at the jarring difference of opinions on his work. You’ll find people accusing it of being pro-war or jingoistic and others describing it as clearly antiwar. Neither opinion is based on any overt statement in the book, because Jünger never raises political questions and has nothing to say about the causes of the war or the justness of the techniques with which it was waged.

And so readers have to fall back on what he describes and how he describes it. That’s where his remarkable tone comes in.

I struggle to describe it myself. There is no one word for it. I’ve seen people describe it as cold or inhuman. These are flatly wrong, and critics who describe the book this way are usually assuming something about Jünger personally and projecting that onto the book. Dispassionate suggests itself, though Jünger describes plenty of high emotion, from elation to terror, and even describes himself weeping on multiple occasions.

Perhaps the best word is forthright. Jünger’s narration and descriptions, analytically observed and cataloged with his entomologist’s eye,** are bracingly, disturbingly forthright. He tells but does not explain, much less praise or condemn. These concerns lie outside his purpose, which is to relate what he lived through and what it was like. And he narrates everything in the book with the same unflappable forthrightness, whether his rookie mistakes on sentry duty, the miserable conditions of trench life, the joy of finding an abandoned store of wine, the variety and effects of British and French grenades, the corpses of the dead, the death of a little girl killed by British shrapnel, the excitement of going over the top, the terror of hand-to-hand combat, the experience of being hit by shell fragments, caught in barbed wire, shot through the chest.

All of these are narrated so bluntly, so matter-of-factly, that they seem to need no literary adornment, though Jünger was a skilled craftsman and carefully worked over his diaries to produce this book. The result is uniquely horrifying—and thrilling.

That’s the subject of the meme above, in which Remarque reacts to the horror in the expected, clichéd way, and Jünger decidedly does not.*** I think that’s also why so many people interpret Jünger so differently. War described this unflinchingly shouldn’t be exciting… should it? What do we make of someone who finds that he enjoys and excels at something so horrible? Hence the accusations of coldness or inhumanity, or, further, of jingoism or fascism or social Darwinism or worse.

Sympathy

But actually reading the book, one finds enjoyment of danger and conflict without bloodlust. Jünger describes killing plenty of enemy soldiers—often point-blank, intimately—but just as often he passes up the chance to kill an enemy. Interestingly, this happens more often in the later, wilder, more violent passages of the book from Operation Michael (Spring 1918) onward, and, in one episode late in the war, Jünger explicitly contrasts himself with a ferocious stormtroop leader he joins in an attack. Jünger, you might be surprised to learn by this point of the book, is invigorated by someone yet more eager than himself.

Similarly, Jünger takes no joy in destruction for its own sake. While never editorializing or effusively emoting over it, it is clear that the destruction of whole towns and villages and the annihilation of landscapes is a bad thing. And every time he encounters his enemies outside combat, he looks upon them with sympathy and even respect. Likewise with the French or Flemish civilians in the rear—he shows no disdain, no exploitative greed, no animosity whatsoever, and always interacts politely and even familiarly. Most often the civilians appear as friendly or affectionate figures, and Jünger presents their evacuation when the war reaches their homes as unfortunate. Again, without explicitly saying so.

Thrilling or horrifying? Ja.

All of which only brings us back, again and again, like Jünger himself, to the combat. And it is thrilling. Seldom have I read a true story with as much continuous excitement as when Jünger goes into the line with his company, endures British and French bombardment, gets stranded far ahead of the German lines and shoots his way out, is surprised by but manages to defeat a British Indian colonial unit far larger than his own, or, especially, when he begins the breathtaking, overwhelming assaults in the Spring 1918 offensive, with his men rushing over battlefields that have sat immovable for three years.

It is also horrible, with the destruction of lives by shrapnel, bullets, gas, infection, artillery—powerful enough simply to vaporize some men—and dumb accident all presented bluntly, in unstinting detail, like a naturalist describing lions taking apart a zebra. It could provoke what some on the internet call mood whiplash, but somehow Jünger conveys all of this to the reader as a sensible, coherent, unified experience.

One suspects that it really could not be thrilling without being horrible—and vice versa. This is a tension Jünger clearly felt and that Storm of Steel makes the reader feel like no other book, all of which is part of Jünger’s forthrightness. Most other war novels and memoirs skew toward the horrible; a few, mostly from long ago, toward the thrilling or exciting or even the morally uplifting.

Jünger refuses easier understandings of what he lived through. His work suggests that the people horrified by war are right. And so are the people thrilled by it. Throughout Storm of Steel, Jünger is describing a state, a condition, and how do you rage against a state? War just is.

Philosophizing

One gets all of this from reading between the lines, from letting the Storm pass over you, so to speak, and listening to the lightning and feeling the wind and the pelting rain. Jünger describes bluntly but doesn’t preach, at least not most of the time. There are isolated passages of reflection in which Jünger drifts into what Mark Twain—brutally but, to be frank, accurately—described as “the sort of luminous intellectual fog” of German philosophizing,† but he avoids the world-historical opining of Remarque or other explicitly antiwar authors.

One thinks of Dalton Trumbo’s novel Johnny Got His Gun, which begins as a brilliant modernist stream-of-conscious story and ends as a straightforward Marxist sermon, or the unfortunate Willy Peter Reese, who was killed on the Eastern Front during World War II and left behind an unfinished memoir so densely packed with philosophical and poetical musings as to be almost unreadable for long stretches.‡

The edition of Storm of Steel I read this time includes a short foreword by Karl Marlantes, veteran of Vietnam and author of the brilliant novel Matterhorn based on his experiences as a Marine platoon commander. Marlantes is the perfect person to introduce Jünger. Like Storm of Steel, Matterhorn is vividly and painstakingly descriptive and avoids overt philosophizing or didactic messaging, deriving its power from the forcefulness with which it presents what happened. Both have an absorbing, dreamlike quality once they take hold of the reader. In some places, both are a fever-dream.

Marlantes’s verdict on Jünger, with whom he feels an affinity despite also being separated by a vast gulf: he was “a different breed of man: the born warrior.”

Conclusion

Like I said, this is more a grab-bag of notes, observations, and meditations than a straightforward review. Like the war Jünger fought in and wrote about, Storm of Steel is fundamentally impossible to summarize and can only be described, and is therefore prone to misinterpretation. One has to experience it. And I strongly recommend experiencing Storm of Steel to everyone.

Notes:

*I do not own any German edition of the original, In Stahlgewittern, though that is on my wish list. This edition is the Michael Hofmann translation of Jünger’s last revision of the book in 1961. There is an online fan culture for the “original” 1929 English translation of Jünger’s second revision, though that translation is rife with inaccuracies and most widely available in a print-on-demand reprint that is apparently loaded with typos.

**The memoir that I think offers the closest point of comparison in tone and style to Storm of Steel—while still being a very different book—is EB Sledge’s With the Old Breed. Tellingly, both men became zoologists after the war.

***A further contrast between the two books that I’ll just drop here: Linguistically, their titles also suggest a key difference in tone and perspective. Remarque’s book, in German, is Im Westen nichts neues, i.e. “Nothing new in the West.” Im Westen is in the dative case, suggesting stasis and therefore pointlessness. Nichts neues, nothing new, is the book’s central, bitter irony. But Jünger’s title, In Stahlgewittern (a Gewitter is a thunderstorm), is in the accusative case, which in German suggests movement (one stands in a room datively, but goes in[to] the room accusatively). Grammatically, the title could just as accurately be translated Into the Steel Storm. This is precisely Jünger’s journey in the book, and where he takes the reader.

†To see more of Jünger in this mode, read Copse 125, a memoir in which he expanded upon one specific monthlong stretch in the trenches in the summer of 1918. The contrast is striking. I read it this past spring.

‡I read Reese’s book A Stranger to Myself a few years ago, also in a translation by Hofmann. Interestingly, where Hofmann includes as footnotes passages from Reese’s diaries—which, like Jünger, he had used as the raw material to construct a memoir—they are much more vivid, direct, and concrete than the memoir he based on them.

Devotion and Glass Onion

Jonathan Majors and Glen Powell as Jesse Brown and Tom Hudner in Devotion, and Daniel Craig as Benoit Blanc in Glass Onion

My family’s Thanksgiving Break arrived just in time this year, giving both my wife and I some much-needed rest and our kids a lot of good time at home, all together. As an added bonus, the break started off well for me when my father-in-law took me to see a movie, and then my wife and I spent the evening of Black Friday on a date that included steaks and another movie. And what is more, both movies were good. After months of nothing interesting in cinemas, this has been a good couple of days.

The films are Devotion and Glass Onion. I intended to review Devotion the morning after seeing it, but just because I’m on break doesn’t mean I’m not busy. After seeing Glass Onion last night with my wife and wanting to review that, too, I decided to put together a joint review of both. I hope one or both of these will sound appealing to y’all, and that you’ll find something here to enjoy.

Devotion

Devotion, based on the book by Adam Makos, tells the true story of Ensign Jesse Brown and Lieutenant Tom Hudner, naval aviators who saw action in the Korean War. The movie transpires over the course of 1950, when Hudner was transferred to a naval air station in Rhode Island and met Brown, the first African-American naval aviator and therefore still a curiosity to outsiders despite being mostly accepted by his fellow pilots. When their commander assigns them as wingmen for fighter training, Hudner and Brown test each other in skill and daring, slaloming through the masts of sailboats and buzzing a house in the nearest town. It’s friendly and professional, but they’re also clearly feeling each other out.

The early tensions of the Cold War loom in the background, and after their squadron is issued powerful and dangerous new aircraft—the F4U Corsair—Brown and Hudner deploy to the Mediterranean and finally to Korea. Here, late in the year, after the Chinese intervene and stream across the Yalu River into North Korea, overrunning American and UN positions and surrounding and pinning down Marine units at the Chosin Reservoir, Brown and Hudner provide close air support, attacking ground targets, strafing Chinese units as they mass for attack, blowing up bridges. It’s facing MiGs and anti-aircraft fire in Korea that will most sorely test Brown and Hudner’s skills and friendship.

As played by Jonathan Majors and Glen Powell (also of Top Gun: Maverick, making this his second naval aviation role this year), Brown and Hudner are a study in contrasts. Brown is stolid, stoic, but with something simmering just below the surface; Hudner is gregarious and upbeat but by no means naïve. Brown is a married family man and a teetotaler; Hudner is single, on the prowl, and doesn’t mind throwing one back with the boys.

One could call this standard buddy movie material but Majors and Powell play it with great skill and subtlety, making Brown and Hudner feel like real men with real depth to them, and so what begins as a professional relationship with some low-key rivalry grows into a friendship that takes on great weight and meaning by the end. The more they get to know each other, the more each grows. Iron sharpeneth iron.

The acting is good across the board, especially Majors and Powell but also Christina Jackson as Brown’s wife Daisy, who takes the usually thankless role of the wife waiting for her husband back home and gives it serious heart. As strong as Brown and Hudner’s relationship becomes over the course of Devotion, it’s Hudner’s relationship with Daisy that gives the film is greatest emotional weight. Fittingly, they have a coda together.

The main draws for me were the aviation and the Korean War setting. Both are excellently done in Devotion. Korea doesn’t get much attention nowadays—it has really earned its nickname of “The Forgotten War”—and I’m glad to see a good film that provides a small but clear window into the topic. The film stresses both the continuities of this conflict with World War II (having fought in that war gives an aviator an authority that even rank doesn’t) and change (the integration of the armed forces, most obviously, as well as a change in opponents). The handful of battle scenes showing the ground conflict are well-executed—a nighttime attack in which more and more and more Chinese troops appear in the flickering, wavering light of flares was even scary.

The aviation also proved excellent. I’ve learned since watching Devotion that director JD Dillard insisted on practical effects, real aircraft, and real flying wherever possible, and the film has a strong sense of verisimilitude and authenticity as a result. The filmmakers’ painstaking attention to detail makes everything feel real. Devotion’s flying sequences may not have quite the palpable sensory thrill of Top Gun: Maverick, but they’re close, and for the same reasons. The combination of practical effects and real planes with Erik Messerschmidt’s rich, moody, classically styled cinematography also means that Devotion looks great, far better than a comparable film like Midway.

Furthermore, the aviators in this film act and talk like real pilots, worrying over things like weather, visibility, maintenance, windspeed and direction, the approach when landing on an aircraft carrier, and more. Brown, for example, excels in his F8F Bearcat but worries about the overwhelming torque and limited cockpit visibility in the Corsair. This is not just about verisimilitude, but sets up important events later in the movie. It’s just good, solid filmmaking.

I have not yet read Makos’s book and can’t vouch for the truthfulness or accuracy of every detail of Devotion’s story. Certainly some aspects of the film feel like stock Hollywood elements, especially a racist Marine who keeps reappearing and challenging Brown. But the rest strikes me as true to the source material. I especially liked that a crucial moment in the plot is motivated by the respect Brown and a white aviator have for each other because they’re both Southerners. The respect afforded all the characters in all their particularity gives the film a complexity that makes not only the action but the situation feel real.

Devotion’s refusal to make sweeping statements, avoiding political grandstanding or simplistic caricature in favor of closely examining the friendship between two wingmen, makes it a more subtle, nuanced, mature examination of racial division and healing—not to mention comradeship, courage, professionalism, and love—than I’ve seen anywhere in a long time. But more than that, it’s a well-crafted and moving telling of an important true story, and that alone makes it worth seeing.

Glass Onion

Following up my review of Devotion with a review of Glass Onion means going from the sublime to the ridiculous. And that’s not necessarily a bad thing.

Glass Onion opens (in May 2020, the last halcyon days of the pandemic before society started eating itself) with a series of oddballs receiving an elaborate puzzle box. Communicating with each other by phone, they work their way through the puzzles to receive a signed invitation to a private island getaway from an old acquaintance, tech billionaire Miles Bron (Ed Norton). They convene in Greece for the boat ride to the Glass Onion, Miles’s elaborate, showoffy mansion where he keeps a Porsche on display on the roof (since there are no roads on the island) and has rented the Mona Lisa from the Louvre. The guests are Claire (Kathryn Hahn), an annoying liberal politician from New England; Birdie (Kate Hudson), an annoying fashionista with a talent for saying stupidly offensive things and is being kept from her phone by her assistant (Jessica Henwick); Duke (Dave Bautista), an annoying manosphere Twitch streamer who arrives with his girlfriend, Whiskey (Madelyn Cline); and Lionel (Leslie Odom Jr), who is just a scientist.

But two unexpected guests arrive as well. One is Benoit Blanc (Daniel Craig), who has no connection with Miles but has dark forebodings about unexplained invitations to gatherings like this. The other is Andi (Janelle Monáe), a cofounder of Miles’s tech company who was elbowed out of her leadership role, her fortune, and more. She was invited, but it was clearly pro forma. No one expected her to come, and they are disturbed that she has. Blanc notes, observes, hypothesizes.

Blanc is also greatly bothered. Miles has planned this get-together as a murder mystery roleplaying game. Why would he suggest the idea of himself, murdered, to a house full of people who wouldn’t mind doing exactly that?

I can’t write much more without giving anything away, and I certainly don’t want to do that. But a clue as to what to expect from Glass Onion arrives early, delivered by Yo-Yo Ma, of all people, at a bizarre Covid party held at Birdie’s penthouse apartment. When a music box in Miles’s puzzle begins playing a classical tune, Yo-Yo Ma explains that the tune is Bach’s Little Fugue in G Minor, a fugue being a seemingly simple tune that, when played back and layered over itself, changes, revealing extraordinary complexity and unexpected surprises. The central metaphor of a glass onion, which is both layered and clear at the same time, also suggests a great deal about the way the film works.

And that is one of the joys of Glass Onion—the complexity, the careful construction, the doubling back and revelation. It had a lot of genuine surprises and was brilliantly crafted. I’d even rate its plotting as better than Knives Out. The other joy is the humor. Glass Onion is hilarious from beginning to end, with a lot of well-earned laughs deriving from character and well-executed setups and punchlines, not just references and allusions as in a lot of other comedy these days. There’s also plenty of pure silliness, but the fact that a lot of the jokes also work as plot points or signposts for the viewer points back to the quality of the film’s construction.

The cinematography is good, the costumes and sets are great, and the performances—cartoonish as the characters are—are good. Craig is especially good as Blanc. In the first half of the movie I wondered why Blanc, who was mostly cool and collected in Knives Out, was so befuddled and buffoonish in this one. But in the second half… And Janelle Monáe, whose natural sanctimony I usually find off-putting, was truly brilliant in a role that turns out to be a bit of a fugue or glass onion itself.

I did have a few misgivings about Glass Onion. The setup and middle act were brilliant, but the film missteps tonally in the end. Some of the climactic action is bothersomely childish. Again, I can’t elaborate without giving too much away. And while the characters were all wildly entertaining and well-performed, they were still broad caricatures whose foibles and flaws felt like familiar types and some of the jokes at their expense were low-hanging fruit. Dave Bautista’s manosphere influencer, for instance, rants about masculinity and is obsessed with guns but lives at home with his mom. Got it. One suspects Rian Johnson spends way too much time online. Fortunately, almost all of the characaters reveal more about themselves as the film goes on, doubling back, layering.

But these are minor problems. Knives Out, the first Benoit Blanc mystery, was one of my favorite movies of the year when it came out in 2019. I wrote that it “was the most fun I’ve had at the movies this year.” That’s probably also true of Glass Onion.

Conclusion

I’m glad to say that after a long cinematic dry spell this year, I’ve gotten to see two good films in just a matter of days. Devotion and Glass Onion are solid, well-constructed movies and well worth seeing in theatres. Glass Onion in particular is a Netflix film and as far as I know will only be in theatres for a week. I hope y’all will check it and Devotion out.

Happy Thanksgiving!

After-action report: 15th International Conference on World War II

John “Lucky” Luckadoo, 100-year old veteran of the 100th Bomb Group, at the National WWII Museum

Over the weekend, the National WWII Museum in New Orleans hosted the 15th International Conference on World War II. The theme this year was “Resistance,” and the Museum had an excellent lineup of sessions, panelists, and speakers. Unfortunately, tickets were prohibitively expensive, and when I first looked at the program back in the late spring I wrote it off as something that wouldn’t happen. So I’m especially grateful to an old classmate who now teaches history at another college here in South Carolina for telling me about the Museum’s free streaming option just a few days before the conference started.

I wasn’t able to “attend” every session, but those that I did were exceptionally good and I wanted to catalog them here, along with a few notes, thoughts, and book recommendations—either books by the panelists or books recommended during a panel discussion. I hope this will provide a good resource for y’all as well.

Thursday, November 17th

Resistance from Within: Germany and Austria, chaired by Jason Dewey, panelists Nathan Stoltzfus and Günter Bischof

Stoltzfus described resistance movements within Germany while Bischof, an Austrian, concentrated on the wide array of Austrian anti-Nazi activity in the years immediately following the Anschluß in 1938. Both emphasized mass support for the Nazis—for whatever reason, including the restoration of national glory, economic revival, militarism or revanchism, or, the elephant in the room, anti-Semitism—as a major obstacle for resisters.

Living Under the Rising Sun, chaired by Richard Frank, panelists Ricardo Jose and Ethan Mark

I was unable to attend this session as it straddled my back-to-back classes Thursday morning classes, but a colleague told me it was excellent and passed along Richard Frank’s recommendation of the book below. I’ve had this on my to-read list since it came out, but this recommendation will bump it up in priority. Frank, by the way, is a name I’ve been familiar with for a long time (I have his most recent book, Tower of Skulls, on my desk waiting to be read right now), and he proved a highlight of every panel he either chaired or participated in.

Book recommendations: Implacable Foes: War in the Pacific, 1944-1945, by Waldo Heinrichs and Marc Gallicchio

Between Hitler and Stalin on the Eastern Front, chaired by Jennifer Popowycz, panelists Robert Citino and Alexandra Richie

Perhaps my favorite academic panel. I’ve known Citino’s work a long time—his study The German Way of War was immensely helpful to me when I first started studying modern German history and German military history specifically. I was unfamiliar with Richie, though reazlied I had heard of her book Warsaw 1944: Hitler, Himmler, and the Warsaw Uprising. Both were impressive, and together they had an eloquent, nuanced conversation about the extremely complicated and tricky subject of resistance in Eastern Europe.

Citino specifically critiqued the “Manichean” view of the war common to Americans, a view in which one sorts all participants into simplistic “good” and “evil” categories. This is dangerous, Citino implied, because it does not prepare the student of history for things like, for example, Latvian partisans who were anti-Nazi (good!) because they were ardent nationalists (hmm…) who wanted a Latvia for Latvians, specifically one free of Jews (uh-oh). The war was considerably more complicated for the occupied in the East than the Allies vs Axis global-strategic perspective many hold by default.

Richie especially impressed me with her encyclopedic and carefully explained view of Polish resistance to both the Nazis and Soviets, whether predicated on nationalism, Catholicism, Communism, something else, or some combination of these. Her closing remarks on how the Polish experience of World War II and the Cold War has given the Poles a keen sense of the value of freedom—and the worthiness of sacrifice to preserve it—was moving.

Book recommendations: Irena’s Children: A True Story of Courage, by Tilar Mazzeo

Missed sessions:

• Living Under the Rising Sun, chaired by Richard Frank, panelists Ricardo Jose and Ethan Mark—Included discussion of the Philippines and Indonesia under Japanese occupation.

• Fighting a Common Foe in Asia, chaired by Allan Millett, panelists Xiaobing Li and Dixee Bartholomew—Included coverage of the “united” effort of Nationalist Chinese forces and Mao’s Communists against the Japanese and the American OSS’s assistance to Ho Chi Minh’s Communist guerrillas in Indochina.

• External Threat, Internal Struggles: Europe Under Occupation, chaired by Mark Calhoun, panelists Sarah Bennett Farmer and Jason Dawsey—Included discussion of the French resistance and Italian partisans.

• Conference Opening—Richard Overy presented on his newest book, Blood and Ruins: The Last Imperial War, 1931-1945, which is another book high up in my to-read list.

The Museum has the entire day’s sessions in one video file on Vimeo here.

Friday, November 18th

Losing at War: Battlefield Blunders and the Men Who Made Them, chaired by John Curatola, panelists James Holland and Conrad Crane

I missed the first few minutes of this panel owing to office hours obligations, but the rest of it was quite excellent. James Holland (Tom’s brother), well-spoken as usual, with a startlingly precise command of figures and statistics, paired well with Crane, who made the point early on that while tactical decisions are more exciting to study, logistics and preparation are usually more important overall to the outcome of battles. “Amateurs study tactics; professionals study logistics.” Crane also warned against “theoritis,” the neglect of real-world conditions in favor of theories that could only work under impossibly ideal conditions.

The Q&A proved especially fun, as everyone who studies World War II for even a few minutes comes to firm conclusions about who won, who lost, and why, and Holland and Crane were particularly good off-the-cuff here.

I took exception to one minor offhand remark by Holland re. the production of the Tiger tank as a “strategic” error considering how many resources each Tiger gobbled up. Holland made the valid point that, given Germany’s logistical situation, it made sense to focus on quality rather than quantity (cf. Soviet tank production), but that the Tiger was overcomplicated to produce, difficult to maintain or repair, and hard to drive. “This was like putting an eighteen-year old who doesn’t know how to drive in a Lamborghini,” or words to that effect. The points on design, production, maintenance, and repair I agree with, but the Tiger was not actually difficult to drive or learn how to operate, having intuitive controls, a well-positioned internal layout, and—unlike many other tanks including the Sherman, which Holland specifically described at one point—a steering wheel.

I gave up on arguing with people about the Tiger a long time ago—I think it’s cool and impressive, and I’m just going to enjoy it—but this was fresh on my mind thanks to this video essay on the Tiger’s strengths in “soft factors” from the inimitable Lazerpig. I feel a little silly recommending that, but it’s good.

Well, there I go coming to firm conclusions. At any rate, this was a fun and excellent panel.

Book recommendations: Hell in the Hürtgen Forest: The Ordeal and Triumph of an American Infantry Regiment, by Robert Rush

Asia Aflame, chaired by Richard Frank, panelists Xiaobing Li and Ethan Mark

A good, wide-ranging panel on Imperial Japan in Korea, China, Burma, India, and other mainland Asian territories that covered everything from strategy and resources to the experiences of ordinary soldiers, civilians, Korean “comfort women” pressed into prostitution for the Japanese army, and the long-lived after effects of the war in all of these places. (A nurse with experience in China pointed out during the Q&A that she struggled to impress upon some elderly Chinese grandmothers in the late 90s that childhood obesity was a serious problem, the assumption among that generation being that fat babies were healthy—because it was fat babies that survived the Japanese.) There was also an interesting side discussion of Japan’s actual longterm goals. Did they want to conquer North America in a “Man in the High Castle scenario”? Short answer: No.

Book recommendations: Visions of Victory: The Hopes of Eight World War II Leaders, by Gerhard Weinberg

The Old Breed, K Company and Eugene Sledge, chaired by Richard Frank, panelists Saul David and Henry Sledge

One of the outstanding sessions I was able to attend. David has recently published a unit history of K Company, 3rd Battalion, 5th Marines, the unit in which Eugene Sledge served on Peleliu and Okinawa. Henry Sledge is Eugene’s son. David provided lots of interesting context for K/3/5’s experience of the war, including on campaigns like Guadalcanal and New Britain before Sledge joined the unit, and Henry Sledge gave a wonderful child’s perspective on his father’s later life, his writing of With the Old Breed (“I’d see him up late at night, writing on a yellow legal pad, and ask ‘What are you doing, Dad?’ ‘Nothing! Go to bed.’ He was nicer than that, but…”), and the special place that memoir has in the lives of veterans, veterans’ families, and the public’s understanding of what it was like to serve in World War II. Lots of insight and some profoundly moving stories.

Book recommendations: With the Old Breed and China Marine, by EB Sledge; Devil Dogs: King Company, Third Battalion, 5th Marines: From Guadalcanal to the Shores of Japan, by Saul David

Missed sessions:

• Women at War: Resistance, chaired by Steph Hinnershitz, panelists Elizabeth Hyman and Lynne Olson—Included discussion of women who participated in the Warsaw Uprising and the archaeologist Christiane Desroches-Noblecourt, the subject of Olson’s most recent book.

• “I Was There”: WWII Veteran Conversation, chaired by Michael Bell, guest Z Anthony Kruszewski, a veteran of the Polish resistance and the Warsaw Uprising.

The Museum has the entire day’s sessions in one video file on Vimeo here.

Saturday, November 19th

Final Resistance—July 20th and its Legacy in Germany, chaired by Alexandra Richie, panelist Levin von Trott zu Solz

This was the first of two outstanding sessions that I watched featuring speakers with direct personal connections to the war. Levin von Trott zu Solz is the nephew of Adam von Trott zu Solz, an ardent anti-Nazi who gained an important position in the Third Reich’s Foreign Ministry and who became a key associate of Colonel Claus von Stauffenberg in the Officers’ Plot. How closely did Trott zu Solz and Stauffenberg work on the plot? The night before the attempt on Hitler’s life, Stauffenberg’s driver recorded visits to two places: a church and Adam von Trott zu Solz’s house. And it was the driver’s logs of these visits that got Adam arrested.

Richie and Trott zu Solz talked through the course of Adam’s life and education (Rhodes Scholar, graduate of Balliol College, Oxford), his work in China, and finally his determination to carry on resistance to the Nazis from “inside,” at home, which he felt was an inescapable duty. His patriotic motivation was quite movingly explained, though I would like to have learned more, as in the panels on Austrian and Polish Catholic resistance, about Adam’s devout and outspoken Christianity (something Adam had in common with Stauffenberg). Trott zu Solz’s narrated his uncle’s arrest, trial, and execution straightforwardly and without embellishment, making it all the more powerful—especially as he explained how Adam and others of the conspirators attempted to outmaneuver the Gestapo and other authorities even in the midst of interrogation and torture.

An informative personal look at just what “resistance” really demands of people.

Masters of the Air, the Bloody 100th, and John “Lucky” Luckadoo, chaired by Donald Miller, panelist John Luckadoo

The second session I watched on Saturday, and the last overall I was able to catch, featured another person with a direct connection to the war—the 100-year old John Luckadoo, the last living original B-17 pilot from the 8th Air Force’s 100th Bomb Group. Luckadoo was astonishingly sharp and expressive, despite admitting that he had trouble hearing questions during the Q&A, and offered up lots of long-view perspective as well as specific details about what serving aboard a B-17 meant. It was so cold at bombing altitude over Germany, for instance, that when flying through flak or attacked by Luftwaffe fighters he would start sweating in fear and the sweat would freeze—which would then block oxygen flow to his mask. Miller also noted how young the pilots and crews were: Luckadoo was 22 years old when the war ended.

Luckadoo also described a briefing with General Curtis LeMay himself, a planned mission over Berlin that would have amounted to a suicide run but was only aborted after they had crossed the Channel into Occupied Europe, and the worst mission in his experience, a raid on Bremen. Throughout, Luckadoo was also self-effacing, pointing out that surviving all of his missions did not make him exceptionally skilled or special but simply lucky—“Damn lucky,” as in the title of Kevin Maurer’s recent book about him.

The Q&A was especially interesting, as many older members of the audience mentioned having fathers or other relatives who served as crewmen on B-17s. Others had good questions about things like the likelihood of survival when bailing out of a stricken bomber. The cockpit of the B-17 was so cramped, Luckadoo answered, that you had to put on your parachute and other equipment after you got aboard. But if you were hit, “You could go through a knothole and you wouldn’t touch either side.”

This was one of several sessions I wish could have gone on even longer.

Book recommendations: Damn Lucky: One Man’s Courage During the Bloodiest Military Campaign in Aviation History, by Kevin Maurer

Missed sessions:

• Saving Freud: The Rescuers Who Brought Him to Freedom—Rob Citino in conversation with Andrew Nagorski, author of the titular book, which covers the effort to help Sigmund Freud emigrate to England following the Anschluß.

• A French Teenager in the Resistance—Steph Hinnershitz in conversation with Nicole Spangenberg, who was 12 at the time of the German invasion of France.

• Half American: The Epic Story of African Americans Fighting World War II at Home and Abroad—Marcus Cox in conversation with author Matthew Delmont on his newly released book.

• Closing Banquet Presentation—Ben Macintyre, author of Operation Mincemeat, one of my favorite reads last year, presented on his most recent book, Prisoners of the Castle, a history of British POWs in Colditz.

The Museum has the entire day’s sessions in one video file on Vimeo here.

Conclusion

I was able to “attend” just under half of the Conference’s panels, interviews, and presentations, but what I saw was excellent. I learned a lot and was encouraged by the palpable enthusiasm for the topics. I was also glad to discover that the Museum has made available, at least for now, the recordings of each day’s sessions. I’ve linked all of them above. I plan to revisit several of these and catch up on the ones I missed. And I’m looking forward to next year’s conference.

I hope this has been a help, and that y’all will check some of these panels out, not to mention the many excellent books recommended over the course of the conference. Thanks for reading!

Two notes on craft from Poe

Or, perhaps, one note on convincing storytelling or believability from two different but overlapping angles.

Having read last year about Poe and science and a few weeks ago about Poe and American cities, right now I’m reading a pretty straightforward short biography called Edgar Allan Poe: The Fever Called Living, by Paul Collins. Despite its brisk pace and short length (107 pages), the book takes care to track Poe’s development as a craftsman—of poetry first, then fiction and journalism. Two early passages that caught my eye:

First, from a passage on Poe’s famously savage book reviews:

Poe could also lavish praise; indeed, his appreciations feature some of his most careful thinking about craft. In a generally positive review of Robert Bird’s satirical identity-shifting novel Sheppard Lee, Poe explained that a fantastical narrator must speak “as if the author were firmly impressed with the truth, yet astonished with the immensity of the wonders he relates, and for which, professedly, he neither claims nor anticipates credence.” The author must commit to his conceit, in other words—and yet must also perform a sleight of hand, and not overexplain or make the reader conscious of when the story has shifted into the improbable. Poe was, in fact, airing a central tenet of his own fiction: “The attention of the author, who does not depend upon explaining away his incredibilities, is directed to giving them the character and the luminousness of truth, and thus are brought about, unwittingly, some of the most vivid creations of human intellect. The reader, too, readily perceives and falls in with the writer’s humor, and suffers himself to be borne on thereby.”

Second, on one of the short stories that marks Poe’s maturity as a writer:

“Ligeia” returns to two of Poe’s signature themes—liminal states of life and death, and the fluidity of identity—and continues a brilliant use of gothic settings that were curiously old-fashioned even by 1838. Yet Poe does not jest with or even acknowledge these as fictional conventions . . . Instead, “Ligeia” was Poe’s first story to absolutely sustain the voice of the narrator and a belief in the conceit. He never breaks character—not to slip in an ostentatious scholarly joke, not for a sly nudge to the reader, not for grotesque description for its own sake. This disciplined internal logic would become a hallmark of Poe’s craft, and the defining characteristic of the stories that we still read today.

This latter is in contrast to some of Poe’s early stories, which were stylistically accomplished but inconsistent, narrated by nonentities or full of sly asides, wink-wink-nudge-nudge allusions, or showoffy jokes. They do not, in Collins’s words, commit fully to their conceits, and their narrators do not sustain the fevered, convincing voice Poe describes in the first passage because they step back from the dream they’ve created in the mind of the reader to gesture, comment on, or joke about it. The result is inconsistency and a lack of believability.

Consider the intensity of the Poe narrator par excellence, the anonymous narrator of “The Tell-Tale Heart,” or even a more sane, ordinary character like Arthur Gordon Pym. Both describe outlandish, shocking events and horrible violence with a matter-of-factness that makes them instantly convincing, and Poe, master of tone and pacing, does not pull away or relax his narrators’ hold on the reader. Now compare these to any of the recent Marvel movies—an extreme and probably unfair comparison, but I’m sticking with it. Jokey, unserious, pandering, self-aware and self-deprecating, their drama and emotion diluted by a steady drip of flippancy, their stories are weak as a result.

In sum: in writing a story, commit totally to selling what’s happening as true, and don’t blink or flinch—even once.

To paraphrase Chesterton, who was himself well familiar with Poe, fiction is a game of chicken which no man of honor should decline.

Looking for the big W

Jonathan Winters as Lennie Pike in It’s a Mad, Mad, Mad, Mad World (1963)

Over the weekend I finished watching It’s a Mad, Mad, Mad, Mad World with my kids. First time for them, zillionth time for me. The movie has grown up and aged with me the way a lot of other comedies haven’t, and part of the reason has to be the density of its jokes—slapstick, sight gags, visual puns (Jimmy Durante literally kicking the bucket), comedy of manners, observational humor, wordplay, banter, innuendo, shock, celebrity cameos, pop culture allusions, over-the-top situational comedy… every trick in the book. My kids were delighted by all the slapstick, especially Mickey Rooney and Buddy Hackett’s airplane antics and every time Ethel Merman got knocked upside down.

But the older I get the more I appreciate the film’s generous leavening of pure irony. The film is shot through with it from the start, the most fundamental irony being the situation itself—a small group of people witness an accident and, by doing the right thing and stopping to help, become privy to a secret (there’s $350,000 buried under “a big W” in Santa Rosita State Park) that sets them all at each other’s throats and precipitates the entire manic, frantic, madcap race to find stolen money. It’s as if the Good Samaritan stopped to help the victim of bandits and ended up taking off to Jericho to find Achan’s buried treasure.

This irony is neatly bookended by one character: Dorothy Provine’s Emmaline Finch. Emmaline firmly opposes going after from the beginning and spends most of the movie fed up with her feckless, incompetent husband (Milton Berle), her domineering mother (Ethel Merman), her idiot brother (Dick Shawn), and everyone else she meets and talks to along the way, including the most seemingly decent of the original group, trucker Lennie Pike (Jonathan Winters). She oozes disgust toward all of them and their low, vulgar, unethical, and illegal quest.

Until, that is the entire bunch arrives at Santa Rosita State Park. At first she refuses even to get out of the (stolen) truck they arrived in, but eventually leaves to find a water fountain to freshen up—and spots “the big W.”

Within minutes, she has told a complete stranger (Spencer Tracy’s Police Captain Culpeper, undercover) what is buried there and has hatched a plan to split the money with him and run away by herself. Emmaline’s standoffishness, it turns out, has always been more about maintaining a certain moral posture against everyone else than about actually doing the right thing. Everyone is a crook when the opportunity presents itself. There is none righteous.

Of course, Emmaline’s plotting is short-lived. Almost immediately, Pike finds one Otto Meyer (Phil Silvers), a schemer who had abandoned him in the desert to go after the money himself, and chases him, intending to settle the score. It’s in the middle of this sub-sub-sub-pursuit that Pike runs through the palm trees that form the big W, and he has his big epiphany.

That’s the irony that got me thinking about all of this: the two people who find the big W—Emmaline, stewing in her own self-righteousness, and Pike, furiously chasing his betrayer—are the ones who aren’t actively looking for it at the time. Sometimes, when you’re looking for something, you have to give up on it to find it.

Some kind of deep spiritual truth? I don’t know. It is first and foremost finely crafted irony. But like all good humor, it resonates with life and existence—that is, it rings true—as does the movie’s larger, climactic irony: all the men who wind up on a fire escape ten stories up, wrestling each other for the suitcase containing the stolen cash, lose what they’re striving so desperately to keep.

On the term "Anglo-Saxon"

Last week, when I took exception to the great Tom Shippey’s arguments for the continued use of the term “Dark Ages” to describe post-Roman or early medieval Europe, I had in mind a counterexample for a follow-up post: “Anglo-Saxon,” a term that tends not to suggest much to the ordinary person and to which very few preconceived notions are attached.

Unless you’re a particular kind of academic.

Briefly, in a technical sense the term Anglo-Saxon is most commonly used three ways:

• Describing a period, it applies to England from roughly the mid-5th century to the Norman Conquest in the late 11th century.

• Describing people, it applies to the Germanic peoples who invaded Britain during the “migration period” c. AD 450 and who originated in modern-day Germany, Denmark, and Frisia.

• As a noun, it is synonymous with Old English, the language spoken in many regional dialects by the people described above.

Other uses, such as for the material culture found at sites like Sutton Hoo or the literature produced by these people, are elaborations on these three basic uses. But Anglo-Saxon as a term for a period in a particular place and the people typical of that period and place has been in common usage for a very long time, right up until today. Just looking at the shelves I can see from my desk, I can see the great medieval historian Frank Stenton’s volume for the Oxford History of England, Anglo-Saxon England (1943), Hilda Ellis Davidson’s great study The Sword in Anglo-Saxon England (1962), Kevin Crossley-Holland’s literary anthology The Anglo-Saxon World (1982), John Blair’s Very Short Introductions volume The Anglo-Saxon Age (1984), and Marc Morris’s excellent The Anglo-Saxons (2021). Even the Nature study regarding Anglo-Saxon genetics that I linked to above uses the term to describe the migration, the period, and the cemeteries excavated as part of the study. This is a respectable term with a long history.

There has, recently,* however, been a move to stop using the term “Anglo-Saxon” within the study of the Middle Ages because of some of the ways the term has been used outside the field. I almost said “popularly used” but, again, I’ve found that very few people have any firm associations with the term. A vague, historical sense of Englishness attaches to it sometimes, and a very few might think of the term WASP, about which more below, but that’s about it. Nevertheless, because the term was sometimes used to designate certain subsets of “Nordic” or northern European racial types by 19th century scientific racists or casually used for people of a certain ethnic background (like the much, much, much vaguer and more insulting “white people” today), it is now “problematic.”

You can find all the kinds of arguments for this view that you’d expect in this piece from Smithsonian last year, which is where I first learned that there was any controversy about it. A few points raised in the essay:

• The Anglo-Saxons didn’t use the term Anglo-Saxon “much.” The authors try to have this both ways, pointing out that they did use it, but mostly in Latin documents like charters (or the Welsh chronicler Asser’s Life of King Alfred, which uses it in the very first sentence) and hoping you don’t realize that if someone uses a specific term of themselves in a second language they are still describing themselves using that term.

• The Anglo-Saxons more commonly called themselves Englisc or Angelcynn. True, but historians refer to historical peoples using terms they didn’t themselves use all the time. Witness the Egyptians or Greeks. There are even whole civilizations for whom we have had to make up names, like the Minoans. (It’s also worth noting that the cynn in Angelcynn is our word kin, as in kinship, raising the dread specter of blood-relationship that these authors clearly abhor. Naturally they don’t dwell on this.)

• The “Saxon” part of Anglo-Saxon is inaccurate because it “was not widely used and only for the Saxon groups,” not all the related Germanic peoples who invaded Britain in the 5th century. Flatly false, as any Welsh or Scottish person (or binge-viewer of “Outlander”) could tell you. The Welsh refer to their Angle enemies as “Saxons” in the 7th-century poem Y Gododdin and, to this day, the Welsh and Scots Gaelic words for “foreigner” or “English” are Saesneg and Sassenach. Who’s being ethnocentric now?

• The term obscures or erases ethnic minorities living in Britain at the time. There are whole libraries’ worth of controversy about the specific example the authors cite, of the presence of some sub-Saharan Africans in Britain during the period in question, but any argument along these lines is specious. Marginal cases cannot define the whole, and the presence of outsiders among a people group doesn’t make terms describing the predominant people or culture inaccurate. This is akin to some arguments I’ve seen that the term “Norse” is inaccurate because Scandinavians occasionally intermarried with the Sami.

• There are “more accurate” terms available. There are not. All the terms on offer in the essay are actually less precise and more awkward than Anglo-Saxon. And I’m astonished that one proposed alternative is “early medieval English,” since although “Anglo-Saxon” was never a problem when I was in grad school (see note below) I was specifically cautioned away from the term “English” for this period because of its anachronistic connotations.

• Racists used it. This is what the authors really want to argue—the kind of guilt-by-association cooties talk that somehow gets respect today—and most of their Smithsonian essay is taken up with examples of Bad People using the term. They even use the phrase “dog whistle,” and you know what I think of that. But the authors’ problem with many of the examples they offer is, tellingly, not really with the use of the term itself but with the motives of the people using it. The authors are practicing Bulverism.

Well, I didn’t intend to get into that much detail here, but that essay annoyed me so much when friends sent it my way last summer that it was hard not to.** I could go on, but I’ll conclude with its crowning stupidity, the opening sentence of what the authors clearly believe to be a trumpet blast of a final paragraph: “Historically speaking,” they write, “the name ‘Anglo-Saxon’ has more connection to white hoods than boar-crested helmets.”***

Let us now turn to intelligent people, and the reason I’m returning to contested terminology a week after I mulled over the Dark Ages.

This week on The Rest is History Tom Holland and Dominic Sandbrook presented a wonderful two-part series on Alfred the Great, and among the many topics they touched on was the term Anglo-Saxon. What began as an aside early in the episode, when Holland noted out that the term could not have been invented as a racist codeword because it was in use in Alfred’s lifetime, turns into a more pointed discussion later on (at approximately 39:45 if you listen here) regarding why there would be any controversy about the term in the first place:

Sandbrook: So, you mentioned earlier on—some people might have found that a bit weird if you don’t follow academic disputes on Twitter—which I advise you not to do—is you mentioned the phrase “Anglo-Saxon” which has now become… incendiary in America. In American academia. People don’t want to call them, they don’t even want to call them the Anglo-Saxons, do they?

Holland: Yeah, so, the word “Anglo-Saxon” has different significations in different countries. So, here it means the Anglo-Saxons. It’s the period—

Sandbrook: Yeah.

Holland: It’s shorthand for the period between the Roman withdrawal from Britain and 1066. It’s been that for a long time. And in France or Germany or the Continent Anglo-Saxon basically means the English-speaking world—

Sandbrook: Well in France it means Margaret Thatcher and McDonalds, doesn’t it? [laughs]

Holland: Exactly. Kind of liberal free-market economics. But there is the use of Anglo-Saxon as, you know, Britain, American, or Australia, New Zealand, and so on, Canada—“the Anglosphere” might be another way of putting it. In America, the word WASPs, White Anglo-Saxon Protestants, um, there’s a sense there that it is used to connote a kind of 19th-century, well, white, Anglo-Saxon, Protestant hegemony. And because that is now seen as something oppressive, therefore there’s a desire to get rid of the very word. It’s seen as providing succor to racists in America. But because America is an imperial country and preponderant, there is an absolute assumption among, I think, too many American academics that their use of a word should have global resonance, and they don’t acknowledge the fact that, firstly, in England “Anglo-Saxon” has the connotation that it does. It does not connote racist supremacy.

Sandbrook: No no no.

Holland: We have the English Defence League, we don’t have the Anglo-Saxon Defence League. And they want to call it “early English.” English is a much more problematic word in the context of Early Medieval History. But the other problem with banning the word Anglo-Saxon is that it ignores the fact that, as we said, that Alfred is using Anglo-Saxon in his charters, and its a word that underpins his entire sponsorship of the entire idea of the Angelcynn, the idea of Angles and Saxons being part of a unitary kingdom, a unity people, that in the long run will give birth to England. And this is looking forward to the future, but it’s also rooted in the past because it’s drawing on Bede’s great work, you know, and he’s writing in Northumbria, the Anglian kingdom of Northumbria, a long time before Alfred. So the word Anglo-Saxon seems to me to be by far the best description of this very complicated period and it seems insane to try to get rid of it. Anyway, that’s my rant.

Sandbrook: No, no, Tom, I couldn’t agree with you more. You’ve never had a better rant on this podcast in this series. As so often, why get rid of—it’s bonkers to get rid of the term that is natural to most people.

Holland: It think there’s a certain, a kind of cultural cringe on the part of too many academics in Britain to truckle to American hegemony. They are—in a way, they need to decolonize themselves, to coin a phrase. They need to stop behaving like colonial subjects, and assuming that what happens in America should automatically determine what happens here.

Sandbrook: I couldn’t agree with you more, Tom.

Me neither.

Anglo-Saxon poses a problem nearly the opposite of Dark Ages—it’s a term not commonly used by ordinary people, allowing it to retain most of its technical precision, but objected to by academics on grounds that only bother academics. These are not good reasons, and the continued American export of American neuroses to other countries and, worse, to the past should not extend to the Anglo-Saxons.

My favorite passage of Mark Twain comes from A Tramp Abroad and is a footnote to the phrase “pretty much”: “‘Pretty much’ may not be elegant English, but it is high time it was. There is no elegant word or phrase which means just what it means.” Anglo-Saxon may not be the preferred term of the elegant in American Humanities departments but it means something specific in a way no other term quite does, and most especially to people outside the university.

Let me conclude by heartily recommending any of the books I mentioned at the top of this post, and by commending to you Part I and Part II of The Rest is History’s Alfred the Great series. It’ll be well worth your time.

Footnotes:

*How recently, I wonder. While I’m sure you could trace objections to Anglo-Saxon further back than the last few years, when I wrote and defended my MA thesis in 2010 neither the two medievalists nor the military historian on my committee ever raised even a question about the term, which I not only used throughout but included in the subtitle to indicate the time, place, and culture I was researching.

**I’ve also been horribly sick all this week, so caveat lector throughout.

***Let me here urge the formulation of a corollary to Godwin’s Law for stupid invocations of the Klan.