Some parts of this ship work better than others: A Star Wars Episode VIII review

*This review contains no spoilers.

“Star Wars: The Last Jedi” has most of the right ingredients and the right ideas to succeed, but doesn’t always dose these ingredients correctly. Ergo, while it’s not bad, it’s not the film it could have been.


The movie picks up where “The Force Awakens” left off, with the odds stacked massively against General Leia Organa’s (the late Carrie Fisher) Rebellion in its fight against the First Order a.k.a. the Empire 2.0, led mostly by Domnhall Gleeson’s General Hux. Poor Leia has her hands full not only with the First Order, but with keeping daredevil X-Wing extraordinaire pilot Poe Dameron (Oscaar Isaac) on a leash. Meanwhile, Jedi-in-training (well, not yet, but you know what I mean) Rey, still played by Daisy Ridley, has found Luke Skywalker (Mark Hamill) and plans to ask him for his help on behalf of the Resistance.

Of course, it’s not the only reason why Rey wants to see Luke. She can feel the force inside her, and it frightens her. In addition to her impression that her gift controls her much more than she controls it, there is the impending threat of Adam Driver’s Kylo Ren, backed by his master, the Supreme Leader Snoke (Andy Serkis). Then, there is the problem of Luke’s firm intent not to get involved, as he is clearly tortured over losing Kylo – or Ben Solo, as he was previously known – to the dark side.

In “The Force Awakens,” we met Jon Bonyega’s Finn, a storm trooper turned rebel soldier who became very (very) good friends with Rey. In “The Last Jedi,” because Rey is with Luke, Finn is relegated to a glorified subplot. The screenplay teams him up with a maintenance worker named Rose Tico (Kelly Marie Tran), as they are sent to retrieve a master code breaker who is needed for reasons that I don’t wish to spoil, but which feel remarkably minor in the movie’s grand scheme of things. (Although I’m always happy to see the actor who plays the code breaker in question.)

And that’s the setup for the movie, which runs into some problems. I love the idea of diversity in entertainment, but Bonyega isn’t exactly Denzel Washington in terms of his on-screen charisma. While he and Tran have a few fun moments, it’s hard to care about his character when Ridley isn’t there to generate emotional investment, and my indifference was only enhanced by the fact that his and Tran’s subplot is almost completely disposable. Tran’s Rose is a likable character who sometimes seems to belong in another movie.

Also, I’m still not sure about the casting of Adam Driver as Kylo Ren. I understand he’s supposed to be conflicted, and Driver can act, but I need a little more steel from a bad guy with the plans he has. Between him and Gleeson’s General Hux, the old Empire’s leaders scared me more.

Writer/director Rian Johnson clearly set out to make a Star Wars movie that doesn’t take itself too seriously. That’s a noble goal, but I suspect Star Wars afficionados will wish it took itself just a bit more seriously than it does. Indeed, off the top of my head, “The Last Jedi” strikes me as the most gag-loaded installment of the series by some distance, but the larger problem is that too few of them work; those that do are the subtler ones we’re accustomed to in Star Wars movies. However, the very first conversation in the film, between General Hux and Isaac’s Poe Dameron sounds directly out of a Seth MacFarlane screenplay, and we also have to suffer through a scene where Luke “milks” a cow-like creature for a bright turquoise substance. The shot of Luke staring at Rey with lots of the liquid stuck in his beard is not something anyone needs to see.

Several critics of “The Force Awakens” brought up the fact that it felt, at times, like a shameless remake of “A New Hope.” The Honest Trailers gang on Youtube couldn’t help but sarcastically quip, “gear up for a film so desperate to recapture the magic of the first Star Wars, it practically IS the first Star Wars.” Well, I can already hear these same people calling “The Last Jedi” a shameless remake of “Return of the Jedi.”  It’s not a baseless accusation, either. I mean, the scene with Rey, Kylo Ren and Supreme Leader Snoke is just so reminiscent of the final battle between Luke and Darth Vader that it even drew an ‘oh, come on!’ from me.

And I sure wish the movie hadn’t shortchanged the likable Poe Dameron character in the following two ways: 1) He doesn’t get enough screen time. I would have liked to see more of him and less of Finn and Rose, except for the part where… 2) For no discernible reason other than screenplay contrivance, his superiors keep him in the dark about a plan so sensible he clearly would have gone along with it had they kept him in the loop.

So, after all the things I criticized about the film, why am I still saying I liked it? Mostly because it has lots of things going for it. Between Mark Hamill’s proper return to the series and Carrie Fisher’s last hurrah as Leia, in addition to a handful of other details, the nostalgia factor remains through the roof. It has a glorious soundtrack by John Williams, which mixes in the cult Star Wars themes with some new ones to keep the listening experience pleasant. It has its shares of customarily easy-on-the-eye shots and action scenes (a fight scene taking place on a planet where the grounds yields red salt when it gets scratched is absolutely gorgeous).

And I can now say this because, two movies in, my mind is made up about this topic: I think Daisy Ridley is a star. I really do. She has some Lena Headey and some Keira Knightley in her, alongside that oh-so-critical “it” factor. Every time she’s on screen, I care about what’s going on. I’ll be back for Episode IX, of course, but I do hope it features more of her battle against Kylo Ren, and less of the other clutter we see in this one. It’s a shame, because somewhere in there was a better movie than the one we get in the end.


Blog at