Skip to main content

Star Trek Into Darkness

(First, a warning: There’s no way to really discuss this film without spoilers. I’ll start without them, but I’ll give a final warning. And now, off to the races we go...)

I’ve been a Trekkie since we snobbishly referred to ourselves as Trekkers. I actually watched the premier episode waaay back in 1966. I’m the father that J.J. Abrams, producer and director of the new films, refers to when he says, “This isn’t your father’s Star Trek.” Despite that, I was able to enjoy his 2009 reboot of Star Trek. It wasn’t Star Trek, mind you, but rather a clever rendition of Abrams’ preferred series, Star Wars. As a Star Wars film called Star Trek, it was all right; a standard, by-the-numbers space action film. Dumb as a bowl of mice, but at least the mice were entertaining.

Star Trek Into Darkness (STID) isn’t that good. The mice have left the bowl. It’s grossly unfair to call it a terrible film, but it’s definitely a bad film.

STID takes place roughly one year after the events of the last film. As the film starts, New Kirk & Co. are surveying a primitive culture on an alien planet, which affords Kirk the opportunity to do what he does best, i.e., completely ignore the Prime Directive (thou shalt not interfere with primitive cultures). Upon returning to Earth, he is shocked, shocked, I say, that Spock has filed a truthful report about this, nailing Kirk as a liar. Thus in his shocked state, Kirk is stripped of his command (which he never should have had, but I digress) and reassigned as first officer under the command of Rear Admiral Christopher Pike.

This demotion lasts for about five minutes.

A villainous villain named John Harrison, a member of Starfleet, has blown up what is reputedly a library in London. This prompts Starfleet to gather any and all senior fleet commanders into one big room with even bigger windows, which is what our villain wanted as he flies up outside and opens fire. He gets away, despite Kirk’s best efforts with a fire hose.

Kirk wants revenge, which is all Starfleet Admiral Alexander Marcus needs to hear to give the Enterprise back to Kirk. Kirk’s orders are pretty straight-forward: Go Kill Harrison. And so the meat of the movie begins.

The same actors are back in all the key roles, and again Simon Pegg (as Scotty) and Karl Urban (as McCoy) are stand-outs. Bruce Greenwood’s Admiral Pike simply owns the film when he’s on screen. Peter Weller, as Admiral Marcus, chews scenery. Alice Eve, as Carol Marcus, appears to have no purpose other than pose for a gratuitous shot of her in her underwear.

Zachary Quinto continues to be all right as Spock, only here he’s made stupid; not the actor’s fault, he’s written that way. Chris Pine remains a weak-sauce rendition of Kirk, and I was disappointed in Benedict Cumberbatch’s performance as Harrison. Most of the time he’s simply awesome, menacing in an almost quiet way, but at other times he’s teaching Weller how to chew scenery.

ILM’s visual effects are, not surprisingly, flawless. Michael Giacchino’s score feels repetitious of what he did the last time, but just when I think that he comes up with an awesome, new theme and reminds me why I always buy his soundtracks.

There is not an ounce of subtlety to the film’s analogies with the war on terror, right down to remote drone strikes, and that’s all right as far as it goes. Despite a bevy of stupid details, up until roughly the halfway point, STID at least lived up to the tradition of Trek dealing with modern issues in a science fiction universe. Up until that point, I had been won over and was actually enjoying the film.

Then the entire film lurches into the galaxy of stupid. Plot hole after plot hole opens up and stupid move after stupid move is made. By the end, I was just frustrated, more than a little angry, and I can’t say I ever want to see it again, let alone own it when it comes out on Blu-Ray.

To understand why, spoilers from here all the way down.

...

...

...

Final warning, spoilers inbound...

...

...

You have been warned.

Rather than bombard the area where Harrison is supposed to be hiding, Kirk opts to swoop in and arrest the dreaded bad guy. Kirk brings Harrison back to the Enterprise, where it is revealed that his real name is...dramatic pause... Khan. Yes, the Khan, The Wrath of Khan Khan, the villain we all expected to be in this film despite Abrams swearing on the soul of his mother that the film’s villain wasn’t Khan. Liar!

This move demonstrates in a loud and profound manner the writers’ complete lack of imagination. They already had the foundation of a new villain who might not actually be a villain. Issues regarding Admiral Marcus are brought up, there’s more than meets the eye, etc. The film goes back and forth as to who the real villain is, Harrison Khan or Marcus. Sure, it might have ended up as something along the lines of Space Bourne Identity Crisis, but it would have had the benefit of continuing the war on terror analogy. Better still, it would have been something (relatively) new. In short, there was absolutely no reason for Harrison to become Khan.

But that’s what happens and any hope for originality twists off into the stellar breeze. Plot holes begin yawning open, threatening the stability of the projection screen, if not the theater itself. Everyone’s IQ plunges, and they weren’t all that high to begin with. The moment Harrison says he’s Khan, you’d think Our Heroes would take a moment to learn more about him. After all, he's in the history books. Nope. Everyone just nods, goes, “Hmm,” and resumes business as usual.

And so it goes. The story ceases to move along as a story. Rather, it lurches from set piece to set piece. To facilitate the dual villains plotline, Khan goes from villain to hero to villain to hero to villain not because that’s his character but because the plot requires him to.

There’s a parade of fan service throughout the last third of the film, which just feels like pandering, especially when it takes over the plot. Especially when this film steals the iconic moment from The Wrath of Khan when Spock dies saving the Enterprise. Only this time it’s Kirk and we have Spock screaming, “Khhhaaannn!!!” In TWoK, Spock’s death brought the audience to tears because of fifteen years of history with these characters and because he was really, truly, completely dead (albeit, until the next film). Here, we are warned twice that there’s a magical way for Kirk to be brought back to life, so his death is beyond meaningless. It’s a cheap gimmick and nothing more.

But then, Abrams & Co. are masters of cheap gimmicks.

Star Trek was an adventure series that often tackled current events within its science fiction framework. The best Trek always did just that. This film teased that it might have gone that route, but in the end, Abrams reduces Trek to just another big, loud, brain-dead action film.

Star Wars fans, you have been warned.

Comments

Popular posts from this blog

Ant-Man and the Wasp: Quantumania

Wow, it’s been over a year. What a way to get back to this blog because… Are the films of the MCU getting worse? It’s a serious question because the latest that I’ve seen, Thor: Love and Thunder and Ant-Man and the Wasp: Quantumania , are strong arguments that the answer is “yes.” Summary: Ant-Man & Ant-Family get sucked into the quantum realm, where skullduggery is afoot. A load of crap ensues. I’m an Ant-Man fan. I loved the first film despite its flaws. It would have been wonderful to see what Edgar Wright may have wrought. It was clear, though, that replacement director Peyton Reed kept some of Wright’s ideas alive. The result was one of the MCU’s most intimate films, a straight-forward tale of a Scott Lang (Paul Rudd) desperate to remain in his daughter’s life while being “gifted” the life of a superhero. Ant-Man and the Wasp sorta stayed that course, but naturally, because this is the modern MCU, we had to have a female superhero take over, the titular Wasp (Hope van Dyne,

John Wick: Chapter 4

No sense in playing coy, this is a great film. I’ve seen it twice and while I don’t quite love it in the way I love the first, original John Wick , it’s my #2. It’s a little overlong, has some wasted space and time, has one absolutely pointless and useless character, and generally ignores the realities of firefights, falling, getting shot, hit, etc. All that notwithstanding, it’s a great action flick, has a genuine emotional core, and is well worth your time if you’re into that sort of thing. Like I am. Summary: John Wick (Keanu Reeves), last seen saying he was fed up with the High Table, goes to war to obtain his freedom. Some of the most incredible action scenes ever filmed ensue, culminating in a very satisfactory finale and a devastating post-credit scene. The first Wick film was a surprise hit. It was a simple, straight-forward tale of vengeance told in a simple, straight-forward manner. Where it stood out was its devotion to human stunt work, on exploiting long camera shots that

Rogan

The entire Joe Rogan controversy is an example of the kids being left in charge and the adults refusing to teach them any better. I’m not a regular consumer of podcasts. There are a couple I listen to from time to time, but nothing on a regular basis. While I’ve caught a few minutes of the Joe Rogan Experience on YouTube, I’ve never listened to his podcast. One of the primary reasons for that is that you have to subscribe to Spotify to do so, and I prefer Qobuz, Tidal, or even Amazon Music. Rogan is behind Spotify’s paywall and that’s that. But the nature of the fight is about more than who does or does not listen to Rogan. This fight goes to the very nature of the First Amendment and the fundamental concept of the United States. And yes, I understand that cuts both ways. What’s his name and Joni Mitchell are free to yank their creations from Spotify, no ifs, ands, or buts. I’m not denying their right, I’m questioning their reasons. Rogan talks to people. He does so largely unfiltered.