Posts Tagged ‘Steven Spielberg’
I don’t have the numbers to back this up, but I have a hunch that most professional writers rarely go back to reread their own work. In an interview with The Paris Review, the novelist François Mauriac puts his finger on why revisiting a published story can be such an unpleasant experience:
I only reread my books when I have to in correcting proofs. The publication of my complete works condemned me to this; it is as painful as rereading old letters. It is thus that death emerges from abstraction, thus we touch it like a thing: a handful of ashes, of dust.
The more you unpack this statement, the more insightful it becomes. Reading one of your published stories is like reading an old letter in several ways: it confronts you with the image of yourself when you were younger, it makes your mistakes more visible in hindsight, and it shows you how insidiously the present has turned into the dead past. It’s the fossilized remnant of a process that used to be alive, and as soon as a work of art is locked into its final form, you see all kinds of problems with it. This isn’t necessarily because you could do any better now, but because a story on the page always seems less interesting than it did in your head. When you’re experiencing the work of other writers, you rarely dwell on how else it might have been done, but when you’re reading your own stuff, it’s hard to think about anything else.
This kind of estrangement from a work to which you devoted so much time and energy is unbearably sad—or it would be, if the writer didn’t immediately move on to the next thing. And it explains why the rare story that you can enjoy for its own sake becomes so precious. Usually, it’s something that came fairly easily, as if you were simply transcribing a moment of inspiration that descended from somewhere higher up, or rose from the depths of the subconscious. Isaac Asimov called it “writing over my head,” saying: “I occasionally write better than I ordinarily do…When I reread one of these stories or passages, I find it hard to believe that I wrote it, and I wish ardently that I could write like that all the time.” (Asimov said that he cried whenever he reread the ending of his own story “The Ugly Little Boy.”) Alternatively, you can feel safely detached from one of your own works if you were operating as an artist for hire, without much of a personal stake in the result, but did your job at a high level of technical proficiency. Steven Spielberg has said that the only one of his movies that he can watch with his kids as if he hadn’t directed it, rather than remembering what it was like on the set each day, is Raiders of the Lost Ark. You can see why: it was George Lucas’s baby, and what Spielberg brought to the project was a matchless eye and a useful degree of distance from the material. And I’m not surprised that the result delights him as much as it does me.
When it comes to my own work, there’s almost nothing that I can read now for my own pleasure. Occasionally, like Mauriac, I’ll need to correct page proofs, and I always have to gather my courage a bit: you’re strictly limited in the number of changes you can make, and you can’t imperceptibly massage the text in the way you can when you’re fiddling with a draft in Word. Reviewing proofs shortly after you’ve finished a story is even wore than reading an old letter—it’s like encountering an ex-boyfriend or girlfriend soon after a breakup, when you realize that you’ll never be able to take back what happened. (Not every writer feels this way, and some, like James Joyce, notoriously rewrote entire sections of the manuscript in galley form. But I’ve always assumed that making extensive changes at this stage will only introduce unforeseen complications, so I try to restrict myself to altering a word or a punctuation mark here and there.) Even after my feelings have cooled and a story sits on the shelf like a dead thing, it’s hard for me to look at it again: it’s like being confronted with your irrevocable life choices all at once. And if I had to make a list of the bits and pieces of my fiction that I wouldn’t mind reading again, it represents a tiny slice of the whole: maybe “The Boneless One,” most of “Kawataro” and “The Whale God,” the second half of “Ernesto,” the closing summation in The Icon Thief, and the plane crash and tunnel chase in City of Exiles. That’s about it.
In most of these cases, I was writing over my head, either because I was following up on a good idea that seemed to come out of nowhere, or because I was able to subordinate myself to the mechanics of a plot that I’d already set in motion. And of all the pages I’ve published, Chapter 58 of Eternal Empire might be my favorite—which is to say, if you forced me to pick something to read again, it’s the one I’d probably chose. It isn’t the most complex or difficult thing I’ve written: once I knew that Wolfe and Ilya would team up to take down a dacha full of gangsters and save Maddy, it was mostly just a matter of not screwing it up. But I had a great time writing it, and I still have a good time reading the result. The confluence of names I mentioned above is part of the reason why: it’s one of the few occasions when I felt that I was writing fanfic for my own creations, not because I was indulging myself, but because it combined characters for a payoff that I never would have imagined when I wrote the first book in the series. It’s obviously indebted to scenes like the shootout at the Victory Motel in both the novel and the film versions of L.A. Confidential, and if Wolfe at the climax of City of Exiles slipped into the Clarice Starling of The Silence of the Lambs, she’s closer here to the Starling of Hannibal. It’s the finest moment for my favorite character in the trilogy, which is reason enough for me to like it. Throughout this entire author’s commentary, I’d been looking forward to writing about it, but now that I’m here, I find that I don’t have much to say except that I think it’s pretty damned good. And I’m going back to read it again now…
A few weeks ago, I picked up a used copy of the original hardcover edition of Peter Benchley’s Jaws. It caught my eye in part because of the iconic cover art, designed by the legendary Paul Bacon, who passed away earlier this summer. Although the painting was redrawn for the paperback, which later became the basis for one of the great movie posters, it’s still a work of graphic genius, second only to Chip Kidd’s dust jacket design for Jurassic Park in the unexpected way it came to define an entire franchise. And upon leafing through the novel itself—I’m still only halfway through—I was struck by how much it differs, not just from its film adaptation, but from what we’ve come to expect from a modern thriller. There’s a lot of background material on the town of Amity, some engaging, some not, including an entire subplot about the mayor’s mob connections. Most stupefying of all is the huge amount of space devoted to a plot thread, which the movie omits entirely, about an affair between Chief Brody’s wife and Hooper, the oceanographer played in the film by Richard Dreyfuss. It takes up something like sixty uninterrupted pages right in the middle of the novel, and frankly, it’s terrible, complete with passages of awful, clinical, mid-seventies lovemaking as bad as anything from Irving Wallace, who wrote about sex, as one critic put it, as if he’d never had it himself. (A tip to writers: any passage that unblushingly includes the phrase “her genitals” probably doesn’t need to exist.)
Reading the section again today, it’s hard to shake a sense that it must have struck many readers at the time as about as pointless as it seems now. Benchley can be a fine writer elsewhere, but I’d like to think that a modern editor would have taken him firmly by the hand and advised him to cut the whole thing. In fact, the man who edited Jaws was Thomas Congdon, an editor at Doubleday whose clients would later include David Halberstam and Russell Baker, and his collaboration with Benchley has been documented in exceptional detail, thanks to a fascinating story that the journalist Ted Morgan wrote for The New York Times Magazine around the time of the book’s publication. Congdon commissioned the novel from Benchley before a single word of it had been written, and he worked closely with the author, starting at the outline phase, which is unusual in itself. And Congdon, unbelievably, is the one we have to thank for what I have no choice but to call, ahem, the Dreyfuss affair. As Morgan writes:
When Benchley wrote a sex scene between the police chief and his wife, Congdon’s sense of propriety was offended: “I don’t think there’s any place for wholesome married sex in this kind of book,” he wrote. Benchley obediently turned the wife into an adulteress, who has an affair with a young marine scientist. [Italics mine.]
Still, for all I know, Congdon may have been right. It certainly didn’t hurt the novel: half of Morgan’s article is devoted to cataloging its massive sales figures and proceeds from subsidiary rights, and this is all before the movie came out. (The name “Steven Spielberg” never appears, and the only person mentioned from the film side is producer Richard Zanuck.) And while Jaws might seem like a genre unto itself, it has to be read in the context of seventies bestsellerdom, which was dominated by the likes of Wallace, Jacqueline Susann, and Harold Robbins, who spiced up every story with generous helpings of smut. You might even say that the movie version of Jaws, which spawned the modern blockbuster, marks a transitional moment in more ways than one: the only remotely erotic moment in the film is Susan Backlinie’s nude swim at the very beginning, followed by the unavoidable sexual overtones of the ensuing shark attack. Mass culture was moving into an era in which the adult obsessions of the seventies would give way to a fascination with hardware and special effects, calculated to appeal to a teenage male audience that would have found Ellen Brody’s midlife sexual awakening even less interesting than I did. The real love affair in the movie is between the audience and the shark, or, more precisely, between Spielberg’s camera and the shark’s elusive silhouette. Anything else would be superfluous.
As it happens, Jaws wasn’t the first major motion picture of that decade to shy away from sexual elements in the source material. Mario Puzo’s original novel of The Godfather goes on for page after page about Lucy Mancini, Sonny’s girlfriend, and in particular about an odd feature of her anatomy and its subsequent surgical correction. Francis Coppola found it about as weird as many readers undoubtedly did:
I started to read the book. I got only fifty pages into it. I thought, it’s a popular, sensational novel, pretty cheap stuff. I got to the part about the singer supposedly modeled on Frank Sinatra and the girl Sonny Corleone liked so much because her vagina was enormous—remember that stuff in the book? It never showed up in the movie. Anyway, I said, “My God, what is this—The Carpetbaggers? So I stopped reading and said, “Forget it.”
Not every movie from that era shied away from the sexual elements—The Exorcist sure as hell didn’t—but it’s hard not to see the pattern here. As audiences changed, books that were written in part with an eye to the movie rights began to tone down the sex, then cut it altogether, knowing that it was unlikely to survive the adaptation anyway. Readers didn’t seem to miss it, either. And while I’d say that it was no great loss, I also wish that we had books and movies large enough to accommodate good sex in fiction, when necessary, along with more innocent thrills. Pop culture is a ship in which we’re all traveling together, and to get the range of stories we deserve, we’re going to need a bigger boat.
Almost exactly twenty years ago, on April 12, 1995, Tony Kushner, author of Angels in America, was honored at an event at Northwestern University. While taking questions from the audience, he was asked whether he thought there was such a thing as nonpolitical theater. His response:
Well, I don’t think there’s anything that’s not political. As they say, the absence of an ideology is an ideology. It’s a conservative ideology. And a politics that seeks to efface its presence is part of the great mythmaking project of bourgeois, capital society…
I feel uncomfortable talking about theater artists. I will say that, for instance, Steven Spielberg is apparently a Democrat. He just gave a big party for Bill Clinton. I guess that means he’s probably idiotic. I feel I can trash people in the film industry and, of course, they read about these terrible things that I say about them and then I’m having a smaller and smaller market in Hollywood as a result. [Laughter.] Forrest Gump is bad reactionary art and Jurassic Park is sublimely good, hideously reactionary art. E.T. and Close Encounters of the Third Kind are the flagship aesthetic statements of Reaganism. They’re fascinating for that reason, because Spielberg is somebody who has just an astonishing ear for the rumblings of reaction, and he just goes right for it and he knows exactly what to do with it.
This wasn’t the first time that Kushner had expressed this opinion: the previous year, in an interview with the Iowa Journal of Cultural Studies, he described Spielberg as a “front-runner for the Reagan counterrevolution.” What’s astonishing, of course, is that many years later, Kushner went on to become one of Spielberg’s most productive collaborators, writing the screenplays for Munich and Lincoln, with another historical drama in the works as we speak. As far as I know, Kushner—who is more likely to describe Spielberg these days as “one of the great filmmakers of all time”—has never directly addressed the sea change in his feelings, which leaves us free to speculate. It’s possible that Kushner simply mellowed a little with age; or that he was moved, like so many other moviegoers, by the transition in Spielberg’s career after Schindler’s List; or that he realized that working with the most successful director in history would allow him to write scripts that had a decent change of being made, which is something that even a Pulitzer winner can’t take for granted. Really, though, it’s likely that it was some combination of all the above, as well as a recognition that political art is much more effective when executed with peerless technical proficiency. Spielberg is simply the best there is; Kushner, when given the chance to work with him, seemed more than happy to acknowledge this.
Which gets at a tricky point about political art in general. Writers are often warned against trying to inject particular ideological or social concerns into their stories; we’re told that our themes should arise organically from an extended engagement with plot and character, rather than being imposed from above, and that audiences are haunted the most by works of art in which the conclusions seem to emerge almost against the author’s will. What deserves to be emphasized, though, is that political content in itself isn’t a kind of poison pill that makes for bad art; it simply allows bad art, the kind that ought to be revised into something better, to be tolerated and widely seen in what amounts to draft form. A mediocre play of no particular merit might lie in a drawer forever, but if it embraces a viewpoint that happens to resonate with how its audience already feels about a certain subject, it’s more likely to get a sympathetic reception. When the audience, to use David Mamet’s image, leaves the theater humming its own sense of virtue, it’s likely to forgive a lot of other things. Which means that it’s easier for political art to get away with things like flat characters, muddled storytelling, and stretches of outright boredom—which are the source of its bad reputation.
This doesn’t mean that artists have to avoid politics, but it does mean that they need to try just as hard to live up to their own standards of good storytelling as they would if they were writing a straight comedy or drama. (Even the most talented writers suffer from a streak of laziness, and political art’s one great liability is that it allows us to indulge in it. Politics is a little like pornography; it can be shoddy on every level but still find an audience.) And I suspect that’s why Kushner was ultimately drawn to Spielberg. He understood the difference between art that we politely applaud and the kind that grabs us and doesn’t let go, and he evidently came to see that Spielberg’s relentless focus on craft, which once struck him as reactionary, was a weapon in its own right. What makes a film like Munich so extraordinary—and I think it’s one of the great movies of the last decade—is that it uses all the conventions of the thriller, and every trick Spielberg has acquired in a lifetime of popular moviemaking, to tell a story that implicates all of us in frightening, complicated ways. And Kushner’s unstated acceptance of this is more revealing than any number of his more explicit pronouncements on the subject. There’s a place for politics in art, just as there’s a place for everything else, but only if it refuses to settle for anything less than a Spielberg.
On Saturday, my wife and I spent seven hours at the River East theater in Chicago, watching a marathon of the Indiana Jones movies, which I still insist on calling a trilogy, in advance of their release tomorrow on Blu-ray. It wasn’t the first time I’d seen all three films on the big screen—I spent a wonderful day watching them all at the sadly departed UC Theater in Berkeley over a decade ago—but it had been a long time since I’d seen them from start to finish. The experience, I’m happy to say, was close to perfect: the digital prints were gorgeous, the crowd was large and enthusiastic, and the movies were as satisfying as ever. And the fact that we left before Kingdom of the Crystal Skull doesn’t diminish my appreciation for what the original trilogy achieved. Like everyone else, I’m critical of George Lucas: he remains, as David Thomson notes, the saddest of moguls, and his career over the last twenty years has consisted of one long retreat. And yet with these three films, he shaped and enriched my inner life more than any other filmmaker, and for that, I’m forever grateful.
Of the three, Raiders is by far the most cinematically exciting: it was made when Steven Spielberg was still only thirty-four, with the greatest natural eye in movie history, and the result is dazzlingly assembled—it may be his most technically thrilling film of any kind. A great deal of this can be credited to the screenplay by Lawrence Kasdan, which pulls off the difficult job of moving between set pieces conceived by the director and producer while lavishing every scene with ingenious and delightful beats. (Even so modest a sequence as the “bad dates” scene is a small masterpiece of acting, writing, editing, and direction.) The script for Temple of Doom, by Willard Huyck and Gloria Katz, is far more problematic, and the connective material is considerably less graceful, but the big set pieces—the opening sequence in Shanghai, the spike room, the mine car chase—reach dizzying heights. By comparison, the action in Last Crusade is competent, inventive, but less divinely inspired, and there isn’t an action sequence here that really holds up with the best of the first two movies.
Yet Last Crusade has always been my favorite of the three, and one of my favorite movies of any kind, which gets at a very important point: these films aren’t about action or special effects, as fine as they may be, but about a certain spirit, a promise about the kinds of experiences and adventures that the movies can offer us, and Last Crusade captures that spirit perfectly. It’s both endearingly innocent and highly sophisticated, and it expresses, as Truffaut would have said, both an idea of life and an idea of cinema—and the fact that the ideas are straight out of a boy’s book of adventures doesn’t make them any less moving or less true. Looking back, I’ve begun to realize that it’s as responsible as any movie for the direction my own life has taken: I saw it when I was about ten years old, and it was arguably the first in a sequence of books, movies, and television shows that convinced me that I wanted to tell stories for a living. Other movies have since become more important to me, and I fully see its limitations, but few works of art have ever seized my imagination in quite the same way.
And its spirit is one that I’ve been trying to recapture in my own work ever since. One night after college, I was watching Temple of Doom with my family when I dozed off near the end and awoke as the closing credits began to roll. Somehow, in that moment between sleep and waking, I heard something in the score by John Williams—it’s the unbearably beautiful theme that appears in “Slave Children’s Crusade”—that I’d never heard before: it seemed to crystallize, in a few bars of music, everything that I hoped to accomplish as a storyteller. My first novel, a long adventure story set in India, may have been my subconscious effort to work out that one moment of dreamlike inspiration. And while that novel remains unpublished, one of the great challenges I now face as a writer is gradually nudging my work back to that theme, which has been reduced to a subtle, almost imperceptible note in my published novels and stories. I’m still trying to figure out what shape it will take. But it’s there. And I have a hunch that Indy will be the one to show me the way.
People have forgotten how to tell a story. Stories don’t have a middle or an end any more. They usually have a beginning that never stops beginning.
It’s Oscar week, and in anticipation of writing up my list of the ten best movies of the year, which I’m hoping to post in two parts tomorrow and Friday, I’ve been catching up on some of the notable movies I’ve missed, although not all of them. In fact, this will be the first year in a while in which I won’t see all of the Best Picture nominees, not so much out of a lack of time than because there are two I have no interest in watching—and you’re free to guess which ones. But of the remaining films, War Horse is one that I really wanted to see: as a director, Steven Spielberg, who for all his shortcomings remains the major Hollywood filmmaker of the past forty years, has been rather less prolific over the past decade, as his attention has shifted increasingly to producing, so his latest movie is always something of an event. And War Horse is undoubtedly worth seeing, as much for its final limitations as for its considerable strengths.
First, the good news. Spielberg’s eye, which I’ve written about at length before, is on full display, and it does marvelous things: the cinematography is gorgeous but only occasionally showy, and Spielberg’s longtime collaborator Janusz Kaminski offers up small wonders of subtle reveals in the visual play between foreground and background. A cavalry charge through a wheatfield is one of the most beautiful things Spielberg has ever done, and throughout the movie, we’re treated to the work of a director equally at home with intimate detail and epic scope. The occasional nods to David Lean and John Ford aren’t merely homage, but a nod from one legendary filmmaker to his peers. And for most of its first hour, aided by fluent editing from the great Michael Kahn, the film convinces us that we’re about to see something truly special.
Around the halfway point, however, doubts start to creep in, and by the end, although War Horse is never anything less than watchable, it starts to seem sentimental, contrived, and—most unforgivably—confused about its own intentions. Is this movie about a brave, beautiful horse, or is the horse simply a narrative device to introduce us to a series of human vignettes? If it’s the former, it just doesn’t work: the horse never emerges as a real personality, and it even disappears from the action for long stretches at a time. The clincher is the movie’s decision to have all characters, regardless of nationality, speak in accented English: I can understand the reasoning—otherwise, nearly half of the movie would be in subtitles—but it still strikes me as misguided. If the movie is really about this horse, it doesn’t matter if we can understand what the humans are saying, and perhaps even better if we can’t.
Instead, we’re implicitly told that our attention belongs on the human characters, even though none of them ever really repays our interest: for the most part, they’re symbolic figures, although a few—notably a French farmer played by Niels Arestrup—are given sporadic life by the actors involved. Spielberg remains our great visual storyteller, but here, as elsewhere, he displays an odd streak of timidity when it comes to constructing focused narratives. On his greatest achievement, the Indiana Jones trilogy, he evidently deferred to George Lucas, and many of his recent films, even ones I admire—Saving Private Ryan, A.I., Minority Report, War of the Worlds, Munich—suffer from a kind of ambivalence in the second half, as if he can’t decide what they’re about, even as individual scenes remain ravishing. Spielberg’s future depends, more than ever, on his choice of material and the quality of his scripts. And War Horse, for all its flaws, is only a reminder of how much is at stake.
For the second time this week, I find myself reviewing a movie based on a beloved work of art about which I know practically nothing. Yesterday, it was the novels of John le Carré; today, it’s The Adventures of Tintin: The Secret of the Unicorn. And while I’ve always found le Carré dauntingly formidable, if anything, Hergé has the opposite problem—there’s almost too much good stuff here, and it’s all very enticing. (The A.V. Club has a nice Gateways to Geekery on the subject that seems like a good place to start.) Steven Spielberg’s earnest adaptation, while far from perfect, is enough to make me want to take the leap into the comics at last: as a character, Tintin is paper-thin, but winning, and I probably would have been obsessed by the movie that surrounds him if I’d seen it at the age of eight. As it stands, for all its energy, wit, and visual invention, it never takes hold in the way it constantly seems on the point of doing, and the problem, I think, lies in the secret of the Unicorn itself. In short, it lies in the MacGuffin.
A MacGuffin, of course, is the object or plot element that drives a work of fiction. The term was coined by Hitchcock, but Spielberg knows it as well as anyone, having structured the Indiana Jones series around three unforgettable objects: the Ark of the Covenant, the Sankara stones, and the Holy Grail. (We’ll just pretend that the crystal skull never happened, as Spielberg himself seems increasingly inclined to do.) Tintin takes its cues from Indy in more ways than one—although this may simply be a case of inspiration returning at last to its original source—so obviously the story is structured around a similar quest: three parchments, hidden within three model ships, leading to a legendary treasure. And what is the treasure, you ask? Well, it’s…treasure. Four hundredweight of pirate gold, as we’re repeatedly reminded, sunk at the bottom of the sea. That’s a lot of gold. Yet even as the movie worked its sometimes exhausting magic, I felt a bit of a sinking feeling myself, once I realized that the object of Tintin’s quest was going to be nothing but a convenient haul of pirate booty.
Conventional wisdom holds that the MacGuffin itself doesn’t matter; the important thing, we’re told, is the desire and conflict it arouses in the characters. Every few years, then, someone has the fashionable idea to construct a MacGuffin around nothing at all: the “government secrets” of North by Northwest, the mysterious briefcases of Ronin and Pulp Fiction, the Rabbit’s Foot of Mission: Impossible III. To a point, the conventional wisdom is right: we aren’t going to care about any object, no matter how shrouded in importance, if we don’t care about the characters, too. Yet part of me insists that a storyteller should at least pretend to find the MacGuffin interesting, and worth taking seriously, especially if the characters will be wholly defined by their quest. It would be one thing if Tintin had an emotional stake in the chase, or even, like Indy, an inner life, but he’s characterized solely by his pluck in pursuit of that pirate treasure. And I’m past the point where I’m intrigued by pirate treasure for its own sake.
And that’s the real problem. An interesting MacGuffin doesn’t guarantee interesting characters, but a boring one will make the characters boring, too, if the MacGuffin is all they want. A director with great stars and superb confidence in his craft, like Hitchcock or the John Huston of The Maltese Falcon, can get away with a MacGuffin spun out of thin air, but for most works of art, it’s probably safer to go with something less arbitrary. This lesson is lost, unfortunately, on writers and directors who have been told that MacGuffins don’t matter, but still haven’t figured out why. Tintin is the third movie in less than two months built around a MacGuffin that the movie barely bothers to develop, after the nuclear codes of Mission: Impossible—Ghost Protocol and the unspoken secrets of Tinker, Tailor, Soldier, Spy. Both films get away with it because of the level of skill involved, as does Tintin, to a point. But then I think of Indy at the Well of Souls, and I’m reminded that a MacGuffin can be far more. It can be something that gets in your dreams.