Blade_Runner_2049_logo
Poster for “Blade Runner 2049”. Image via Wikipedia.

*WARNING: SPOILERS!*

The movie’s title is misleading. The term “runner” is way too fast-paced for this 2.75 hour science fiction slog. It’s much more of a “Blade Walker” or even a “Blade Crawler”. Scenes drag on, and the camera lingers on things like trees, ruined cityscapes, and statues of naked women long after the viewer has gotten the idea.

The film follows officer K (Ryan Gosling), an LAPD officer in the year 2049. His job is to “retire” (that is, kill) obsolete replicants–synthetic humans created by the Wallace corporation. The older models, leftovers from the Tyrell corporation, which Niander Wallace purchased, have no built-in expiration date, unlike the newer versions–which is what K himself is.

In the opening sequence, K retires a rebellious replicant farmer, after getting into a ridiculous fistfight with him. The director and choreographer really should learn that people can’t get punched in the face repeatedly and then thrown through a wall and just walk it off. (There’s an even more egregious example later.) Also, the whole fight happened because K inexplicably set his gun aside. Very odd.

Anyway, after K kills the replicant, he finds a box buried in the yard outside his house, beside a lone dead tree. This allows for some nice shots of K standing around in his coat, looking contemplative and brooding. Get used to this.

K then goes home to his apartment, to install some upgrades on Joi (Ana de Armas), his holographic companion, who he apparently has set on “sexy over-solicitous housewife” mode. She makes him an artificial dinner, instantly switches her appearance from among a variety of revealing outfits, suggests various things they can do for fun, and in general behaves like a parody of what 13-year-old boys imagine a girlfriend is like. It’s cringe-worthy.

The new upgrade allows Joi to accompany him outside–so now, rather than just being his sexy overeager housewife, she can be his sexy, overeager constant companion. They are celebrating this by pretending to kiss while frolicking in the rain when they are interrupted by a call from K’s boss, Lt. Joshi. (Robin Wright)  She tells him to come to the police station, where they are examining the contents of the box he discovered–the skeleton of a female replicant that died in childbirth.

I was really annoyed by this scene. Basically, it was the standard police procedural trope of “the forensic lab”–except it was Officer K who spotted all the key clues! He kept telling the forensic analyst to zoom in on stuff, and figuring out what had happened to the remains himself. It seemed hard to believe that he, an average replicant rent-a-cop, would pick up on clues the forensics person missed.

At any rate, this is an alarming discovery, as replicants are not supposed to be able to reproduce, and they fear that the discovery of one who did will lead to a replicant rebellion. Joshi orders K to destroy all evidence of this replicant and her child.

This leads K to the Wallace Corporation headquarters–a strange, extremely orange building that reminded me of some of the sets from The Mummy, except with shimmering water shadows on the wall for some reason.

The corporation seems to consist of just two people: Niander Wallace (Jared Leto)–a strange, monk-like character who speaks in nonsensel sentences that are possibly supposed to make him sound smart, but in fact make him a comically obtuse guru–and his replicant secretary, Luv (Sylvia Hoeks), a femme fatale. It reminds me of a story I heard once about a company that employed only a lawyer and a secretary–their only job was to sue any companies who infringed on their corporation’s patents.

I frankly don’t know how the Wallace Corporation stays in business, with only two employees and a product line that exists solely to destroy other parts of the product line. Well, I guess there’s also a third product line designed to provide female companionship to the the main product line.

I’ve heard of niche markets, but this is ridiculous.

Anyway, Officer K finds out from Luv that the bones are the remains of a replicant named Rachael, and hears some recordings showing she was once involved with another LAPD cop, Rick Deckard, the protagonist of the original Blade Runner movie. (That last part wasn’t included in the script, though I half-expected it would be, since this movie insists on spelling things out for the audience.)

At some point around here, K leaves the Wallace Corp. headquarters and gets approached by a prostitute, who has been sent to spy on him by a mysterious woman. It doesn’t mean anything at the time, but it will be important later on, so file that away. Also ponder this: why are there always so many prostitutes in these sci-fi and fantasy worlds? Seriously, it feels like one-third of every fictional economy is hooker-based.

Luv is sent by Wallace to destroy the bones and to follow K as he searches for Rachael’s child. The former she does with incredible ease, considering it means murdering the forensics expert in the middle of the police station.

Meanwhile, K is telling a (somewhat tipsy) Lt. Joshi about his childhood memories. They aren’t, of course, real childhood memories–he’s a replicant, after all, but he has implanted memories. He tells Joshi about one of the most vivid–a story in which he is hiding a small wooden toy horse from some other children. We flashback to scenes of him being pursued through a dark industrial maze, and carefully securing the toy in some shelves.

This scene–not the flashback itself, but the scene where K recounts it to Joshi–was one of the best in the film. Wright was terrific as the foul-mouthed and heavy-drinking but warmhearted Lieutenant. In this scene, she’s almost flirtatious, and has far better chemistry with Gosling than his holographic love interest ever does. It’s a pity she doesn’t have a larger role.

K returns to the scene where he first found the box of remains, and finds a date carved on the dead tree beside the grave–6/10/21, which was also carved on the toy horse he remembers from his childhood. He begins to suspect (bolstered by Joi’s reassurances) that he is Rachael’s child. He checks the birth records and learns that two children were born on that date with identical DNA–a boy and a girl. The girl died, but the boy was sent to an orphanage.

This was another scene that annoyed me. As they are looking at the strings of DNA, the various combinations of “G” “T” “C” and “A” are displayed and Joi comments that these four elements make up human beings’ “code”, whereas she only has two elements to hers. I liked this line, but I didn’t like that she then had to spell it out: “1 and 0”, she says, for the benefit of everyone who doesn’t know what binary code is. I suppose there are such people, but I doubt any of them would go to see this movie.

K (along with Joi, for no reason I can discern) decides to go to the orphanage, which is located in some sort of massive junkyard, where K’s flying police car is shot down by some group of bandits–who these bandits are is never explained. K fights them off and finds his way into the orphanage–a neo-Dickensian sweatshop of sorts, where he forces the cruel overseer to show him to an abandoned area that matches his childhood memory. There, he discovers the horse in exactly the place he remembers hiding it.

 

Somehow–it was not clear how, since we last saw his flying car being shot down–he makes his way back to his apartment, and from there finds Dr. Ana Stelline, a woman with a condition that forces her to live inside a glass chamber so as to be protected from all contaminants. She designs false memories for the Wallace Corporation to implant in replicants. She is a talented designer of memories, and on inspecting his (how she did this, I have no idea) indicates that it is real.

K then becomes inexplicably angry and consequently fails the replicant behavior test that they apparently give him after every mission. He tells Joshi this is because he successfully found and killed Rachael’s child. Joshi gives him 48 hours to either flee or try to pass the test again. So he…

He, um…

Ok, this is really kind of bizarre…

He goes back to his apartment, where Joi has brought in the prostitute from earlier. She has done this because she knows that he’s been wanting to sleep with her (Joi, that is). But, since she’s a hologram and all, it doesn’t go very well. So she sort of superimposes herself over the prostitute.

Except the superimposition doesn’t totally work, so there’s this bizarre blurring effect., kind of like when you watch a 3-D movie without the glasses on.

It’s creepy and hilariously bad and stupid and probably one of the worst romantic scenes ever filmed. And it’s worse when you put it in context. I mean, I get annoyed enough when my computer installs updates without asking my permission. If it started letting prostitutes into my apartment while I was gone, I would be even more upset. And then when you add in that K has just been given 48 hours to run away from the authorities, it seems even more absurd that he would spend 8 of them making love to his virtual assistant.

Ok, looking at K, it was probably more like 10 minutes, but still.

Oh, and the morning after, as she’s leaving, the prostitute makes a catty remark to Joi. That was stupid too.

K has the toy horse analyzed by some random character who exists only to advance the plot but still manages to be vaguely offensive during his brief screen time. The levels of radiation found in the horse lead K (and Joi, natch) to the blindingly orange ruins of Las Vegas.

After finding an abandoned beekeeper’s station and some statues of naked women in high heels–just another day at the office!–K finds his way to an abandoned hotel and casino, where he meets Deckard (Harrison Ford)

Deckard enters with one of the best lines in the movie: “You mightn’t happen to have a piece of cheese about you, now?” This is a quote from Treasure Island, by Robert Louis Stevenson, as K helpfully informs us, thus weakening the line immensely.

Deckard and K then engage in another ridiculous comic-book fistfight that serves no purpose to the story, but takes place in a casino lounge with various holograms of famous performers flickering on and off. It’s kind of cool, but it was done better in Dead Money.

After this is over with, they talk, and Deckard explains he left the pregnant Rachael behind and scrambled police records so they could not track the child.

This scene was another one of the film’s high points, thanks entirely to Ford’s acting. The dialogue is still awkward, and Gosling is pretty wooden throughout, but the gruff tones of the veteran actor make it compelling. As he was when reprising another of his most famous roles, Ford is the one of the few bright spots.

Meanwhile, Luv–remember her?–has killed Joshi and tracked K to Las Vegas. She and her men attack, capturing Deckard and badly injuring K. She also destroys the small device in which the Joi program is stored, effectively “killing” her.

Luv takes Deckard to speak with Wallace. And by speak with him, I mean have Wallace recite bunch of gobbledygook at Deckard in a dull, awkward monotone before finally producing a replicant of Rachael. Deckard gruffly responds that “her eyes were green.” I would say it’s absurd that they could get such an obvious detail wrong, but given the Wallace Corporation’s general ineptitude, it seems almost plausible.

Meanwhile, K has been rescued by some pro-Replicant freedom fighters–one of whom is the prostitute from earlier. They want K to kill Deckard before he can lead the Wallace corporation to his daughter. From this, K realizes he is not the child after all, and that Deckard falsified the records.

After a brief interlude with a giant pink naked holographic girl–just don’t even ask, ok?–K intercepts Luv and her men as they are transporting Deckard to… someplace… and, in a rather anti-climactic battle, K kills Luv and rescues Deckard. This scene takes place at night and underwater, so it’s not really a fest for the eyes.

Finally, K takes Deckard back to meet his daughter–Ana Stelline. K has realized that the memory was actually hers–she designed it and the Wallace Corporation put it in his brain. Deckard greets his daughter in her isolation chamber while K collapses in the snow outside and the credits roll.

It’s not a bad little plot, and might have made quite a good 90 minute or two hour movie. But the pacing is absolutely bad; not merely because it is slow–although it is definitely that–but also just because even with all that build-up, the final battle still seems rushed, confusing and unsatisfying. And we never see what becomes of Wallace himself, who is the main villain of the piece.

“But it’s not about the story!” say the fans. “It’s about the atmosphere! The cinematography!”

Ok, sure; but the atmosphere isn’t that great. It’s nothing we haven’t seen a thousand times before in other films influenced by the original Blade Runner. I was struck, again and again, by how ordinary all of it felt.

As for the cinematography: it wasn’t bad, but it wasn’t as great as I expected from all the hype. That large parts of the film take place at night and in the rain doesn’t help–and frankly, as rainy noir-cinematography goes, there are much better examples.

The poster tells the story. Remember that article a few years ago about orange and blue in Hollywood movies? Well, those colors are out in force here–everything is bluish except Vegas, which is orange. (Compare the poster for 2049 above to the one for the original.)

And in the end, movies aren’t about cinematography. It’s just one tool that the filmmaker uses in service of the ultimate goal: telling a good story with good characters.

The story, as I have said, is not bad but it is also not remarkable, and certainly shouldn’t take this long to tell. And the characters? Well, there are a few good ones. Joshi and Deckard are standouts–I wish we could have had a film about the two of them working together instead.

K is probably the least interesting character in the whole thing, and that’s saying something. Joi–who is the de facto love interest–is also quite dull, since she exists entirely to serve K.

This brings me to another point: the film’s sexism. As I have said, there’s plenty of “male gaze”–besides the statues and holograms, there is a horrible scene where the camera focuses on a naked, newly-created female replicant who is immediately killed for no reason. (This should have been cut, not only because of the gratuitous nudity and violence, but also because it added nothing to the story and made the already overlong picture drag more.)

But even more significant than the sexist imagery is the fact that the women’s roles in the story are all secondary. Even Stelline, who is in a sense the central driving force of the whole plot, is shunted to the side to focus on the unremarkable officer K.

The irony is, it’s clearly a dystopian story, and the world they present could indeed be described as a dreadful dystopia for women in particular, where they are treated, with a few exceptions, as commodities. But the writers seem not to be aware of this. If they were, they could have explored that, rather than the story of officer K, the second-rate cop who wanted to bed his virtual assistant.

Blade Runner 2049 is the second cyberpunk film I’ve seen this year. The other was Ghost in the Shell. See that instead–it’s much better. You can even watch it twice in the time it takes to watch 2049.

For the last five years, I’ve been in a friendly fantasy football league. Fantasy football works like this: you have a team of a few players–my league’s format is 1 quarterback, 2 running backs, 3 wide receivers, 1  tight end, 1 kicker and 1 defense. Each week, players at those positions accrue points for what they do in the real-life NFL games.  My league is head-to-head, so my goal is for my players to score more combined points than the team I’m matched up against each week.

It’s a lot of fun.  It’s mostly luck, but there is a little skill involved–or at least, I’ll claim there is, because I won my league a few years ago, and it’s more fun to brag if I can say it was because I am a football expert.

So, I started thinking: for what other activities could you make up this sort of game? And I ultimately settled on movies.

Like many people, I like to imagine my “dream all-star cast” for movies. But anyone can do that. Fantasy film-making needs to have an element of strategy and resource management.  So, I came up with some rules.

The format of the Fantasy Movie Cast/Crew is as follows:

  • 1 Director
  • 1 Lead Actor
  • 1 Lead Actress
  • 1 Supporting Actor
  • 1 Supporting Actress
  • 1 Screenwriter
  • 1 Cinematographer
  • 1 Composer

Yes, I realize it takes a lot more people to make a movie, but as with Fantasy sports, there have to be some constraints.

Another constraint: you are only allowed to have two Academy Award-nominees per “team”.  That is what brings out the strategic element–it forces players to prioritize where they want the proven talent.  That’s not to say only Academy Award nominees are any good, but again, as with fantasy sports, you have to know how to find under-valued talent to succeed.

Also, you can’t cheat and use one nominee in multiple slots–no written by/directed by/starring the same person.

Finally, the selection is limited to living people–so no building All-Time teams with Stanley Kubrick directing Peter O’Toole or something.

So, here’s my team:

Director: Mike Leigh. Using one of my two Oscar slots right off the bat.  I figured having an established presence at the helm would be important. He also has experience directing in theater as well as film, and I think that versatility would be useful.

Others I considered: Sir Kenneth Branagh, Rian Johnson.

Lead Actor:  Roger Guenveur Smith. This is what I mean about under-valued talent.  I have seen Smith perform live in his one-man show Juan and John, and he is a marvelous actor. Why isn’t he more widely known?  Beats me.  He is excellent at cycling through a huge range of emotions, and can create all different kinds of characters–often in the space of a few minutes.  He also has a distinctive voice and memorable presence.

Others I considered: Ewan McGregor, Joel Edgerton, Ralph Fiennes

Lead Actress: Natalie Portman. Yeah, yeah; long-time readers probably knew I would pick her the minute they read the description of the game.  Well, she’s a great actress with a wide range, and a particular knack for dark or tragic roles.  Besides which, for a movie to succeed, it helps to have at least one big-name lead.

Others I considered: Rachel Weisz, Sigourney Weaver, Felicia Day

Supporting Actor: Stephen Colbert. People know him mainly as a talk-show host, but he does have a background in acting, which you could see sometimes on The Colbert Report when he would really dial up the crazy.  I read once that he said he always wanted to play Richard in Robert Bolt’s A Man For All Seasons. Just the fact that he said that earns him some acting credit, in my book.

Others I considered: Jeff Lewis, Hugh Laurie

Supporting Actress: Sara Kestelman. Like Smith, I first heard of Kestelman when she was voice acting in the game Knights of the Old Republic II. Since then, I’ve seen her perform in all sorts of things.  But it’s still her KotOR II role that best showcases what a terrific actress she is. While the writing is terrific, I think  Kestelman’s acting also made Kreia into one of the greatest characters in gaming history.

Others I considered: Rashida Jones, Tina Fey

Screenwriter: Anthony Tambakis. His work on Jane Got a Gun and his novel Swimming with Bridgeport Girls impressed me enough to take a chance on someone with a relatively small body of work.

Others I considered: None. There aren’t too many active screenwriters whose work I like.

Cinematographer: Steve Yedlin. I’ve only seen one movie on which he served as cinematographer: The Brothers Bloom. But it had something I really, really liked: color. Not just muted greens and greys and browns, but honest-to-goodness colors. This has fallen out of fashion for some reason, and it’s annoying. So, on the basis of his willingness to accommodate the full spectrum of colors, I choose him.

Others I considered: Dick Pope.

Composer: Lisa Gerrard. Another talent I first discovered in Jane Got a Gun. Since then, I’ve heard her work in the band Dead Can Dance, and I was hooked.

Others I considered: Clint Mansell

As for what the movie would be about–well, we can sort those details out later! That’s how the big studio producers do it, after all. As for scoring and head-to-head competitions, those also can be determined later.

How would you build your ideal movie cast and crew?

Possibly the worst movie poster in history.
Poster for “Waterloo”

In the days before CGI, epic war films were massive and costly undertakings. You wanted a shot of 10,000 guys marching across a field in full battle uniform? Well, you had to get them! You couldn’t just have Johnny the Computer Whiz draw them in after the fact.

As in actual warfare, there are innumerable logistical difficulties with re-creating these battles. You’ve got to have men in position, knowing how to use their equipment, and then film them as they maneuver in the field.

All that’s quite hard enough.  But when you are making a film for wide release, you have to have all that plus a story the audience can follow, structured so as to play out in a coherent and satisfying way over the course of two hours.

It’s this last bit that’s really tricky, because while history offers plenty of incredible and compelling stories, they rarely fit into neat three-act schemes that can be concisely portrayed in a couple of hours.

Waterloo starts out well, showing Napoleon’s abdication to Elba in 1814 and subsequent return in 1815.  Especially memorable is the moment when the Emperor walks alone to face his former soldiers, now under orders to kill him, and through sheer bravery and charisma wins them back over to his side. This is one part of the Napoleonic legend that seems made for the movies, and it certainly is a high point of the film.

After that, however, problems arise in this dramatization of the final chapter of Bonaparte’s career.  There are unnecessary voice-overs in which Napoleon (Rod Steiger) thinks in exposition for the benefit of the audience.  Many lines of dialogue uttered by officers on both sides seem like they were lifted from history books and changed to the present tense.

An inordinate amount of time is spent on Wellington’s staff at the Ball hosted by the Duchess of Richmond.   This scene also includes the introduction of a totally fictional and pointless love story that goes nowhere.  The only upside is the chemistry between Wellington (Christopher Plummer) and the Duchess (Virginia McKenna).

Wellington and the Duchess
“Old Boney’s advancing on Quatre-Bras… IF you know what I mean.”

The film dwells on things like this, Napoleon’s illness, and some peculiar episode involving a British soldier stealing a pig, and yet glosses over incidents like the Battles of Quatre-Bras and Ligny with a couple lines of dialogue.

It’s not that the film is inaccurate–indeed, they seem to have gone to some lengths to describe things in historically correct fashion. (Except for the romance and a reminiscence about Major-General Ponsonby’s father) The problem is that the film depicts these events in a strange and sometimes incoherent manner.

The biggest technical flaw is probably the mud.  The battle was famously delayed by wet ground after a rainy night, and indeed the film states this correctly. Where it falls down is the fact that the ground we see on screen is demonstrably dry, as evidenced by the huge clouds of dust kicked up by the columns of cavalry and infantry.

The end result is the comical visual of a frustrated Napoleon sinking in an obviously artificial mud puddle while all around him is a vast expanse of dry land. The fundamental historical fact is correctly depicted, but not in a dramatically effective way.

There are lots of issues like this.  After Marshal Ney’s ill-fated cavalry charge against the famous infantry squares, Napoleon rushes back to the field from his sickbed, crying, “What is he doing?  Everyone knows not to make a cavalry charge without infantry support!”

While completely factually accurate, this seems unlikely to be what Napoleon actually said at the time. It comes across as a line delivered for the benefit of audience members who aren’t familiar with the battle of Waterloo.

And this is the other difficult thing about making historical movies: balancing the history lesson aspect with the need to depict real characters, as opposed to instructional puppets designed to illustrate a historical lecture.

Chances are, if someone is watching the movie Waterloo, they are already a Napoleonic history fan. Sure, there might be the occasional viewer who is an ardent follower of Rod Steiger or Christopher Plummer, but if I were overseeing the production, I would make the executive decision that any viewer who doesn’t already know how the battle went is just going to have to piece it together as best they can–no reason the script should go out of its way to help them out.

Waterloo_1970_06Despite all of that, the movie isn’t horrible.  As an instructional device, it is not bad, and there is something inherently impressive about seeing huge lines of soldiers and horses advancing across a smoky field.  It gives you some vague hint of what it might have felt like to be in the battle.

It’s just that the film lacks a dramatic narrative.  Napoleon and Wellington don’t “come alive”; they just repeat their famous quotes and stoically watch the battle.  Because of this, it feels more like a recording of an elaborate re-enactment rather than a truly epic historical drama.

the_lego_batman_movie_promotionalposter
Poster for “The Lego Batman Movie” Image via Wikipedia

The central thematic conceit at the heart of The Lego Batman Movie is–

Oh, who am I kidding? It’s Lego Batman, for Pete’s sake. So I’ll spare you my usual line of in-depth socio-philosophical analysis. The only thing you need to know here is that it’s a really funny family-friendly movie, with tons of humorous references to various other incarnations of Batman–especially the late, great Adam West.

It’s true to the spirit of Lego, in that it is good-humored and full of crazy, giant battle scenes with characters from different franchises fighting each other all willy-nilly.  It’s exactly like the way I played with my Lego as a kid. And it’s a lot of fun.

The one way in which it can perhaps be analyzed as something other than an entertaining trifle is the part involving the new Gotham city police commissioner’s plan to make the police force less dependent on Batman. She even uses the phrase “It takes a village” to emphasize the collective effort.  Given when the movie was released (late January), I can’t help but wonder if they were expecting that line would have more political relevance.

But never mind that stuff!  It’s a nice, entertaining movie. Sometimes the action moves too fast for anyone but a hyperactive child to follow–but then, that is the target audience.  And there are plenty of jokes that will keep everyone entertained throughout, even when the battles become incoherent.

It_Comes_at_Night
Poster for “It Comes at Night” (Image via Wikipedia)

It Comes at Night is a highly misleading title for this film. Actually, everything about the marketing campaign is misleading. It’s not really a traditional horror film at all. Aside from a few disturbing images and jump scares, its primary focus is horror of the psychological and atmospheric sort, rather than any physical monsters.

Of course, this brand of horror is very much to my taste. The most frightening things, I’ve always believed, are not what we see, but rather what we imagine. Ultimately, the root of all horror is the unknown, because in it the human mind traces all the most terrible threats.

And from this, it should follow that It Comes at Night would be a truly terrifying film after all, because it certainly provides the audience with plenty of unknowns. But in spite of that, it’s not as scary as one might expect.

There’s a lot to unpack here, but I’ll begin by summarizing the plot–don’t read ahead if you don’t want to know the spoilers.

(more…)

wonder_woman_282017_film29
“Wonder Woman” poster. Image via Wikipedia, re-used under “Fair Use”.

Superhero movies are not my favorite genre. But I have long enjoyed watching re-runs of the old Wonder Woman TV series starring Lynda Carter, so I made a point of seeing this one.

Another thing that intrigued me is that the movie is set in World War I. (The character of Wonder Woman was originally created in the 1940s, and therefore was naturally depicted fighting in World War II against the Nazis.)

This was interesting to me for a couple of reasons: first, Hollywood normally can’t resist inserting Nazis into things on the flimsiest of pretexts; so to have no Nazis when the source material actually includes them is a pretty bold artistic choice.  Second, World War I is not nearly as well-known to modern audiences as World War II, so this setting seems like a bit of a risk from a marketing perspective. I like risk-taking.

I also like spoiling movies, so be warned–I’m now going to describe the plot, with spoilers!

The film begins in the present-day with Diana (Gal Gadot) receiving a photograph from the first World War, showing her in her full Wonder Woman garb, standing alongside a ragtag band of soldiers.

This segues into young Diana’s childhood on a hidden island of Amazon warriors. Diana wishes to train as a warrior under General Antiope (Robin Wright), but her mother forbids it, and tells her a cautionary tale about the horrors of war. She explains that Zeus created men to be peaceful, but they were corrupted by the God of War, Ares. Zeus then created the Amazons to protect mankind, and Ares was ultimately defeated. But Zeus also created “the God-Killer”–a weapon housed on the Amazons’ island, in case Ares should return.

Despite these warnings, Diana trains in secret anyway.  Her mother eventually finds out and initially disapproves, but ultimately is persuaded to let her continue.

One day, after a sparring session, an airplane crashes just off the shore.  Diana rescues the pilot, Captain Steve Trevor (Chris Pine), and the Amazons defeat the German forces pursuing him, but General Antiope is killed in the battle.

The Amazons question Capt. Trevor, who explains that he is fighting in the “War to end all Wars”. His plane was shot down as he was fleeing the Germans having stolen a notebook from a chemist nicknamed “Dr. Poison” and her commander, General Ludendorff, who are working to create a super-deadly poison gas.

Diana quickly realizes that the war Steve describes must be the work of Ares. She takes the God-Killer weapons and asks Steve to travel with her to the outside world and the center of the fighting, where she is sure they will find Ares.

Steve first takes her to London and delivers Dr. Poison’s notebook to his superiors. They can’t read what it says, but Diana can, and realizes it means the Germans are manufacturing and preparing to deploy the new, more lethal gas at the Front.

Sir Patrick Morgan, one of Steve’s superiors, is close to getting the Germans to agree to an armistice, but Diana believes Ludendorff is actually Ares, and will use the gas no matter what.

Diana, Steve, and a small group assembled with help from Sir Patrick go to the Front to destroy the supplies of poison gas.  Thanks to Diana’s heroics, they successfully liberate a small town and learn that Ludendorff is in the area, planning to attend a gala for the German officers at a castle nearby.

Sir Patrick orders them not to attack the gala, as he is close to finalizing the armistice. However, they go anyway. (Notice a pattern here?) The Germans fire the gas into the recently-liberated village, killing the inhabitants, much to Diana’s horror.

Diana tracks Ludendorff to an airfield where the Germans are about to deploy a massive long-range bomber loaded with the poison gas. Steve and his men attempt to take the bomber, while Diana kills Ludendorff with the God-Killer sword.

Diana is shocked that the fighting doesn’t stop on Ludendorff’s death. She starts to wonder if all mortals truly are inherently evil and prone to violence. At that moment, Sir Patrick appears, and reveals that he is in fact the God Ares, but that he does not cause wars–he merely exposes the true, dark nature of Zeus’s creation.

Meanwhile, Steve and his men fight their way to the bomber, and Steve is able to get aboard, knowing the only way to stop it from delivering its payload is for him to personally destroy it.

Diana and Ares fight a massive battle, and when Diana sees the bomber explode with Steve aboard, she rallies and defeats Ares, having been persuaded that humanity has the capacity for good as well as evil.

The closing scenes show Diana in London, somberly remembering Steve as cheering crowds celebrate the end of the war. The film ends with a return to the present-day Diana, looking at the old photograph of her and Steve, taken when they liberated the village.

As is typical of the genre, there are lots of drawn-out, special effects-heavy fighting scenes.  These are not bad for the most part–though definitely not to my taste. Each of them seemed to go on longer than necessary–thanks in part to an overuse of slow-motion effects. This was especially true of the final showdown between Diana and Ares. Since Diana’s victory was a foregone conclusion, it really did not need to drag on that long.

Much more interesting are the “character” scenes–yes, that’s right; the parts where people actually talk to one another. Gadot and Pine have excellent chemistry together, and their scenes were my favorite parts of the film.  Romantic sub-plots in action movies can very easily become pointless and tiresome, but the sparks between Diana and Steve seem genuine, and it gives the story some real heart.

One interesting aspect of their scenes is that they frequently talk simultaneously or interrupt one another.  This happened quite often–almost to the point of being overused–but it also made their conversations feel spontaneous, rather than just like two actors reciting lines at each other.

I wish the film had dwelt a bit more upon Diana’s relationship with Steve, and her impressions of the “outside world” in general–there was a little too much time in the second half devoted instead to Steve’s merry band of sidekicks.  They were mildly entertaining, but I think it would have been better to let them be nameless grunts rather than try to make them “colorful”. It’s Diana’s story, after all.

The script didn’t even try to use language that was appropriate for the time period–all the allied soldiers and officers spoke in modern lingo. Even more puzzling to me was that occasionally some characters would speak in a foreign language, with subtitles, but the Germans (and some of our heroes when posing as Germans) would speak in German-accented English.

I’d be interested to know the details of some of the weapons used in the film.  Some are obviously fanciful, others seem to have been trying to stay faithful to the period.  At one point, Steve still has a Colt 1911 despite being disguised as German colonel–that seemed weird to me. But after all, this is a comic-book superhero movie, so I tried to tune out the nit-picking historian voice in my head.

This brings me back around to the setting, which as I discussed at the outset was something that interested me in the film. I still think it was daring (by Hollywood franchise standards, that is) to change the setting to a less-familiar time period.

However, given what actually happens in the movie, it’s a bit puzzling. In fact, World War I actually did end with an armistice, and the real Ludendorff survived the war and went on to be influential in the early years of the Nazi Party.  So, given what happens in the film, is it supposed to be the beginning of an alternate history tale in which World War II did not happen? That would be quite interesting, but it’s left very vague and unexplored.  Fertile ground for a sequel, I suppose…

It’s not a bad film by any means, the plodding CGI boss fight at the end notwithstanding. The other fights are good enough, if you like that sort of thing, and Gal Gadot is a very likeable and charismatic lead.

As I said, I have seen few superhero films. The only recent ones I have watched are Marvel’s Thor and its sequel, The Dark World. The former is a delightful adventure that ranks among my favorite movies.  The latter, sadly, is more what I gather the typical superhero movie is like: a CGI-laden affair, with little time for character development or nuanced emotion of any kind.

This is noteworthy because Patty Jenkins, who directed Wonder Woman, was originally hired by Marvel to direct The Dark World, before leaving over the dreaded “creative differences”. It’s a pity; having seen Wonder Woman, I would have liked to have seen what she could have done with it.

Wonder Woman isn’t a great movie, but it’s certainly an entertaining summer flick, and it’s nice to see a film with a female lead and a female director drawing crowds to the theaters.  Hopefully, this will be the beginning of a trend in the entertainment industry.

WARNING! The following clip contains intense LEGO violence.  Parents, this is what happens when you give your nine-year-old sons red clay and LEGO skeletons! (Credits blurred as before, to avoid embarrassing family and friends.)

This movie is a little clearer than my previous ones, I think.  It was about an army of skeletons who invade a planet and massacre the inhabitants. I made the movie when I was nine, but the music came much later–when I was about 15, and I briefly got into composing scores for my old movies.

And now you know how far back my cosmic-horror fixation goes…

Wonder Woman, Jane Got a Gun, and Ghost in the Shell
From left: “Wonder Woman”, starring Gal Gadot, “Jane Got a Gun”, starring Natalie Portman, and “Ghost in the Shell”, starring Scarlett Johansson

Have you heard? Feminists and superhero fans have been getting anxious about the relative lack of promotion for the upcoming Wonder Woman film, starring Gal Gadot and directed by Patty Jenkins. They are concerned that it is going to suffer the same fate as recent DC Comics films have, and be cast as second-rate superheroes in comparison to Marvel’s string of successes.

I’ve been following the fortunes of the Wonder Woman film for a while now, and I also noticed this lack of publicity.  It registered with me because it fit into a pattern I’ve seen before.

My favorite movie of all time, Jane Got a Gun, was another film whose marketing campaign I watched closely. The Weinstein Co.’s promotional efforts for it were abysmal–I think I saw one trailer for it, and it made the movie look like an action/adventure flick when in fact it was a romantic drama. (Even the title is kind of misleading. They should have called it Jane Ballard.)

Jane Got a Gun had an infamously turmoil-filled production, and apparently the Weinstein Co. based its decision on the film’s history, rather than the finished product. (It’s usually a mistake to focus on process over results.) As such, they didn’t put much effort into promoting it, and didn’t hold advance screenings for critics.  As a result, few people heard of it, and it fared poorly at the box office.

This isn’t the only recent example of a film getting hamstrung by bad marketing.  Ghost in the Shell was a big-budget sci-fi picture with a strong story, and it flopped badly at the U.S. box office.

Unlike the case of Jane, the studio could never be accused of not spending resources promoting Ghost. Paramount even bought a Super Bowl ad for it.  But it was hit with an intense negative buzz, in which people accused it of “whitewashing” because of the decision to cast Scarlett Johansson as the lead character, Major Killian.

This accusation is obviously nonsense to anyone who bothers to watch the film. Major Killian is a cyborg–a human brain housed in a machine.  True, she was originally a Japanese woman, but the entire premise of the film is that her mind and consciousness are transferred to an artificial body.

And yet the accusation of whitewashing persisted, and undoubtedly contributed to negative press surrounding the film. Which is too bad, because while it was not a great film, it was certainly one of the better sci-fi movies I’ve seen in recent years. It was far better than the highly-successful blockbuster The Force Awakens, for example.

This is why what’s happening with Wonder Woman doesn’t surprise me too much.  I have, as they say, seen this movie before. But like Ian Fleming wrote, “Once is happenstance, twice is coincidence, the third time it’s enemy action.” At this point, I have to think this is part of some pattern.

So what’s the common thread?

While they are all very different films, Jane Got a Gun, Ghost in the Shell and Wonder Woman do have a few shared characteristics.  Most obviously, they all feature female protagonists.  They also are all categorized as action films. (Although Jane probably shouldn’t have been).

Is Hollywood deliberately sabotaging female-led action films? That seems crazy, since the easiest way for studios to prevent such films from succeeding would be to… not make them in the first place.

Let us, like Woodward and Bernstein before us, “follow the money”.

One thing to look at is the studios producing the movies: Warner Bros. is handling Wonder Woman, because they own DC Comics.  As I mentioned earlier, DC has been in competition with Marvel on superhero movies, and they have been losing.

Marvel is owned by Disney, which acquired it in 2009.

It so happens Disney also originally had a deal with Dreamworks to release Ghost in the Shell, but it was terminated in 2016, and the movie was released through Paramount instead.

Jane Got a Gun is the clear outlier here–the Weinstein Co. isn’t on anything like the same scale as Disney, Warner Bros. et al.  Also, Jane was rated “R” whereas the rest of these are “PG-13”.  So, presumably it had a much smaller marketing budget at the outset.

The key point is that all three of these movies are released by companies that aren’t Disney.

This is most significant for Wonder Woman, because of the ongoing DC/Marvel battle, which is really a proxy war between Warner Bros. and Disney.  And Disney has been winning it.

Part of the reason I brought up The Force Awakens to contrast with Ghost in the Shell  was because it got way more positive press despite being an inferior film.  But of course, Force Awakens was made by Lucasfilm, which since 2012 is owned by… Disney.

The upshot is that I think Disney is way better at promoting their movies than most of the other studios are.  Even when Disney has something sub-par, they can generate enough positive buzz about it to get people to buy tickets.

It’s important to understand what promotion really entails.  It’s more than just advertisements on television and the internet.  It’s more even than tie-ins, and red carpet events, and sending the cast and crew on talk shows.

It has to do with how PR firms work.  They feed stories to industry journalists to create a buzz around their clients’ products. (Read this marvelous essay by Paul Graham for an in-depth description of this process.)

My impression is that Disney–or perhaps the PR firm they hired–does a vastly better job of promotion compared to the other studios.  They have a much higher success at generating positive buzz for whatever they are releasing next.

Now, to some extent, there is bound to be a “crowding-out” effect. If Disney can internally do better PR, or if they can pay more to get it, it leaves less room for other non-Disney productions to get good PR.

And of course, none of this has anything to do with the actual quality of the movie in question.  (Indeed, I often wonder just how many movie reviews are influenced more by the PR campaign surrounding the film than by the film itself.)

In my review of The Force Awakens, I concluded by saying:

“[W]hy do so many people like The Force Awakens?  I don’t know–maybe it’s the same reason so many people like Donald Trump: both are loud, in-your-face, and have so much money backing them that they won’t go away.”

The comparison actually runs a bit deeper than that.  Trump, whatever else you want to say about him, is great at promotion.  He is like a one-man PR firm in terms of his ability to draw an audience for whatever he is peddling.

Disney, or whoever is handling PR and marketing for their movies, has a similar level of promotional skill.  And the other movie studios are unable to match it.

I think there is also something of an escalation going on, in that the more Disney hypes their releases, the more the other studios are then going to be expected to do to hype theirs. Expectations for marketing campaigns get higher and higher, and when studios fail to meet them, people don’t go to see their movies.

mv5bodyyodiwmwitnmi4oc00odfmlwjiymmtnmi4ogjimzjimtyyxkeyxkfqcgdeqxvynjczote0mzm-_v1_
She’s a robot.  You get that, right? (Image via IMDb)

So, Ghost in the Shell has been something of a disaster at the box office. Which is too bad, because as I said in my full review, it’s one of the better sci-fi movies I’ve seen in recent years.

A big problem has been heavy criticism of the decision to cast Scarlett Johansson as the main character.  The argument is that they should have gotten a Japanese actress to play the role, since the character is Japanese.

[Warning–I’m about to spoil a few plot points, so proceed with caution.]

But the thing is, the whole premise of the movie is that a sinister robotics corporation took the brain of a woman named Motoko Kusanagi and placed it inside an artificial body. (And re-named her “Mira Killian”.)  We only see Kusanagi’s human body in a brief flashback, and her features are difficult to discern in the scene.  Johansson just plays the artificial machine body in which Kusanagi’s brain is housed.

And this serves a dramatic purpose in the film: in the scene where Kusanagi in her mechanical body is reunited with her mother, the fact that they no longer have any resemblance makes the scene very poignant.  Even though she has her memories back, it underscores that something has been permanently taken away from them by the operation.

In addition, Johansson’s performance throughout the film was fine. So the whole controversy is really misguided–I suspect a lot of the people talking about it didn’t see the movie or even know the plot.