Showing posts with label war movies. Show all posts
Showing posts with label war movies. Show all posts

May 24, 2021

12 STRONG (2018)

  

I don’t want to sound insensitive or dismissive, but can we please have a moratorium on 9/11? Can we all just agree that it happened, it was terrible, and our country’s been stuck in neutral ever since? As typical, following 9/11, Hollywood didn’t waste much time in finding ways to capitalize on the worst attack on our country in the history of ever, and soon a wide-ranging collection of genre-hopping films all came together and assembled the most depressing shared cinematic universe yet. Some of these actually managed to be pretty good, like Paul Greengrass’ harrowing United 93 and Kathryn Bigelow’s duo of The Hurt Locker and Zero Dark Thirty. And lest we not forget about Oliver Stone’s atypically maudlin and non-controversial World Trade Center, about which we actually all did forget. For every one title you remember, two or three are existing in the foggiest banks of your memory — probably where they belong. 9/11 has become so prominent in storytelling that it should have its own sub-genre label.

At the risk of again sounding insensitive, we’re coming dangerously close to 9/11 becoming a cliché. 12 Strong proves that — an absolutely lifeless, generic, bland, and unimpassioned telling of military forces engaging against the Taliban months following the attack. We’re back in the desert, kids, populated by American soldiers with nicknames who are tough and stoic and who have wives and who love their wives and America. They are led by Captain Mitch Nelson, with a performance by Chris Hemsworth that is absolutely out-of-the-box soldier as purchased via Amazon Third Party, slightly used but in otherwise good shape (contains none of the original packaging). And he’s as boring to watch as he’s ever been, which is impressive, considering how boring he generally is. You see, Mitch Nelson said to commanding officer, Lt. Colonel Bowers, an initially surprising appearance of Rob Riggle (until I tell you that the dude is a bonafide marine in real life), that 9/11 was an awful thing and he's the one who has to do something about it, namely lead his squad and make the Taliban pay. Then he decides to not die while in Afghanistan because he promised his wife he wouldn’t die. A flag waves. He means it. America/freedom.

Even if we want to scrape away the tragic and sad circumstances that surround 12 Strong and look at it either as a wartime drama or an action film, sorry — still boring. The sequences that find the soldiers directly engaging with the enemy lack suspense. Whether our soldiers die or not feels like no consequence, because beyond their mini opening prologues where each of them says goodbye to their wives, little is done to promote them as actual people. If you know half their names by film’s end, I’d be both impressed and convinced you were lying. (Why are you in this, Michael Shannon?)

Critiquing films based on true stories, especially when those stories involve such massive tragedies experienced by real people, is a slippery slope. To pass judgment on a dramatization of such tragedy and the actors who brought those characters to life feels as if judgment is being passed on the tragedy itself, as well as those real people. The soldiers as depicted in 12 Strong really did those things. They were real, and brave, and selfless. And they deserved a far better film about their actions.

Mar 31, 2021

DUNKIRK (2017)

Steven Spielberg, over the last 30 years, has adopted a practice that’s become known as “one for them, one for me,” which is how he chooses his projects. He makes one film “for them” — the audience who wants the big and fun tentpole — “and me” — the more personal and intimate story that he feels compelled to tell. Think Munich (“for me”) and Indiana Jones and the Kingdom Crystal Skull (“for them” — and thanks for nothing, by the way). Christopher Nolan, through his extremely successful (and profitable) tenure with Warner Bros., has been embarking on the same journey — and billions of Batman revenue has made the studio pretty amenable to keeping Nolan codified. But even then, his more personal films have still been bigger than life. His “one for me” films consist of The Prestige, Inception, and Interstellar, all of which have still managed to find a wide audience while satisfying his itch to tell those less broad kinds of stories. Like Spielberg, these kinds of non-mainstream tentpoles also found success at the box office.

So it’s kind of appropriate that Nolan’s latest finds him in World War II territory, which Spielberg previously explored with Saving Private Ryan (perhaps his best “one for me” film).

Dunkirk shows Nolan at his most experimental since Memento — not because of the story he’s telling, but in the way he chooses to tell it. This wartime experience is told by three separate groups of people, who for the most part never share screen time with each other (including fighter pilot Farrier, played by Tom Hardy, who conceals his face for most of his screen time with his jet’s face gear). It’s not quite real time, but it feels damn close, and there’s an intent on both Nolan’s part, as well as composer Hans Zimmer, to never let the tension cut. Whether it’s two soldiers trying to “buy” their way onto a rescue ship by carrying a wounded soldier on a stretcher, or a father and son civilian team steering their boat to the Dunkirk coast to transport soldiers home, or a trio of fighter pilots trying to quell the enemy in the air, Nolan never lets the looming threat settle, and Zimmer’s music slowly, slowly, slowly builds, rarely taking a break.

There was some minor guff online about Nolan’s audacity in making a PG-13 war film, because war in real life is brutal, and hence… But once you see that Nolan isn’t interested in shooting something as grisly as Saving Private Ryan’s Normandy Beach invasion, all of that falls by the wayside. There’s very little blood in Dunkirk and almost no violence, but it never feels “missing” so much as it becomes known early on that it’s simply not necessary.

Where Dunkirk falters is in its characterization, with its various characters being defined as: scared, patriotic, and brave. In the case of the former, this unfairly taints the audience’s view of the few soldiers on screen who have every right to have been psychologically ravaged by war, but who don’t have the audience’s sympathies, anyway. The film opens with young soldier Tommy (Fionn Whitehead) first running from enemy fire as his fellow soldiers are shot down, and then trying to take a shit on a beach, and then attempting to sneak on board a rescue ship, later defying orders from a superior officer to scram and hiding below the docks. This is our first impression of Tommy, who says more than once throughout that he “just wants to go home,” and he’s not someone the audience can become fully invested in. Between the treatment of this character, and things like Tom Hardy’s one-note performance, during which he makes the Tom Hardy face the whole time (and who I swear tries to sound a little like Bane in some scenes just to fuck with people), Dunkirk is better left to revel in its IMAX-shot war scenes than with the characters participating in them.

Dunkirk is a solid wartime film, and Nolan’s overall best since Inception, but its somewhat cold depiction of its characters muddy the waters of what the audience has come to expect by now of their on-screen war heroes. In this regard, it’s no Saving Private Ryan.