Star Wars: The Last Jedi

Warning: total spoilers for The Last Jedi.

After weeks of frantically speed-scrolling through my various social media feeds when anything that looked like a Star Wars spoiler appeared, I’ve finally managed to get out and see The Last Jedi. Despite my diligence, I didn’t go in completely unspoiled: I knew the general shape of the fan discourse surrounding the characterisation, which means I had some context cues and a smatter of details to work with, but not the major plot points. Now that I’ve seen the movie, however, I’m electing to write my own review before catching up on other people’s opinions, so if I touch on something that’s already been dissected at length without referencing said discussion, that’s why.

In broad-brush strokes, I enjoyed The Last Jedi. Assessing it purely on its own merits, there was a lot it did right: the cinematography, special effects and original creature creation were wonderful, I loved Rose Tico, and there was a pleasing balance of drama, emotion and humour, the requisite scenery-chewing deftly subverted by moments of self-aware comedy, especially in the opening exchange between Hux and Poe Dameron. Mostly, it was solid.

Mostly.

But.

The thing is, no Star Wars film is an island. The Last Jedi is the second film in a trilogy of trilogies, one whose core trio were clearly and intentionally mapped to the heroes of the (original by creation-date, second by internal chronology) series in The Force Awakens: Finn to Han, Rey to Luke and Poe to Leia. This being so, it was easy to mark the other narrative similarities between The Force Awakens and A New Hope – most notably, the parallels between the Death Star and Starkiller Base, both of which were destroyed in the respective finales, but not before their destructive power was unleashed. Which makes comparing The Last Jedi to The Empire Strikes Back not only reasonable, but – I would argue – necessary, if only to determine whether the decision to parallel the new with the old has continued beyond the first film.

The short answer to that is: yes, The Last Jedi is structurally akin to Empire, but not always to useful effect. The long answer, however, is rather more complex.

As a writer, there’s nothing that makes me crave a metaphorical red pen quite like a story where, for whatever reason, I can see the authorial handwave of Because Reasons gumming up the mechanics. If The Last Jedi was an original film, detached from the Star Wars universe, I’d be able to tell you that the problem stems from the poorly-forced sexist clash between Poe and Holdo, and that would be that. But because The Last Jedi has borrowed certain key narrative structures from Empire, there’s a clear template against which to measure its narrative choices, which makes it easier to infer the hows and whys of various changers.

A quick refresher in Star Wars, for those who haven’t watched the original trilogy lately. The Empire Strikes back begins with the Rebel forces being ousted from Hoth in a massive battle. After fleeing the planet, Luke goes to Degobah to train with Master Yoda, while Han and Leia spend some time dealing with a broken Millennium Falcon and the pursuit of Boba Fett, kissing and bickering and generally cementing their chemistry before finally going to track down Han’s old buddy, Lando Calrissian, in Cloud City. Frustrated with Yoda, Luke has a premonition of danger and goes to rescue his friends, as Lando, who’s been strong-armed by Darth Vader, hands Han and Leia over to the Empire. Han is frozen in carbonite after Leia declares her love for him, Luke loses a hand and learns Vader is his father, and the film ends with the pair them, plus Lando, escaping as they resolve to rescue Han.

By comparison, The Last Jedi follows a fairly similar arc. The film opens with the Rebellion being ousted from its base and pursued in a space battle. Rey attempts to persuade Luke to help her, while Poe and Finn are left dealing with a fleet that’s low on fuel as they try to outrun Hux and the First Order. As Leia lies injured, Poe clashes with Holdo over command, which results in him sending Finn and Rose on a secret mission to find a codebreaker who can help sabotage the First Order’s ship. Unable to the codebreaker, Rose and Finn return instead with DJ, a stranger who claims he can help them, but who ends up betraying them to the First Order. Unaware of this, Poe mounts a short-lived mutiny against Holdo. Meanwhile, frustrated with Luke and experiencing an odd connection to Kylo Ren, Rey goes to try and turn him to back to the light, only to find that Snoke was the source of their connection. Kylo kills Snoke and his guards with Rey’s help, reveals the truth about her lost parents, then betrays her in turn. In the final battle, Rose is injured and declares her feelings for Finn, and the film ends with the rebellion united but still fleeing.

Based on this, it seems clear that The Last Jedi is intended to parallel The Empire Strikes Back, both structurally and thematically. All the same elements are in play, albeit recontextualised by their place in a new story; but where Empire is a tight, sleek film, The Last Jedi is middle-heavy. The major difference between the two is Poe’s tension-and-mutiny arc, which doesn’t map to anything in Empire.

And this is the part where things get prickly. As stated, I really love Rose Tico, not only because she’s a brilliant, engaging character superbly acted by Kelly Marie Tran, but because she represents another crucial foray into diverse representation, both in Star Wars and on the big screen generally. There’s a lot to recommend Vice-Admiral Holdo, too, especially her touching final scene with Leia: I still want to know more about their relationship. I am not for a moment saying that either character – that either woman – doesn’t belong in the film, or in Star Wars, or that their roles were miscast or badly acted or anything like that. But there is, I suspect, a truly maddening reason why they were paired onscreen with Finn and Poe, and that this logic in turn adversely affected both the deeper plot implications and the film’s overall structure.

Given how closely The Last Jedi parallels the main arc of Empire, it’s narratively incongruous that, rather than Finn and Poe heading out to find the codebreaker together, the pair of them are instead split up, decreasing their screen-time while extending the length of the film. But as was firmly established in The Force Awakens, Finn and Poe map to Han and Leia – which is to say, to a canonical straight couple. Even without the phenomenal on-screen chemistry between John Boyega and Oscar Isaac, that parallel is clear in the writing; and in Empire, Han and Leia’s time alone is what catalyses their on-screen romance.

That being so, I find it impossible to believe that Finn and Poe were split up and paired with new female characters for anything other than a clumsy, godawful attempt to No Homo the narrative. Rose and Finn’s scenes are delightful, and their actors, too, have chemistry, but every time we cut back to Poe and Holdo, the story flounders. Everything that happens during Finn’s absence is demonstrably redundant: not only does it fail to move the plot forward, but in trying to justify the time-split, writer/director Rian Johnson has foisted a truly terrible mini-arc on Poe Dameron.

Specifically: after Leia is incapacitated, Holdo is given command of the rebellion. Seeing Holdo for the first time, Poe looks startled and states that she’s not what he was expecting. When Poe, recently demoted by Leia for ignoring orders, asks Holdo what her plan is, Holdo dismisses him as a hot-headed “flyboy” who isn’t what they need right now. Not only doesn’t she tell him where they’re headed, she apparently doesn’t tell anyone else, either. This failure to communicate her plan to her people is, firstly, why Finn feels he has to light out on his own, which is how he meets Rose, and is secondly why, once Finn and Rose come up with a plan to infiltrate the First Order, Poe decides that they can’t risk involving Holdo.

As we eventually learn, Holdo does have a plan – and a good one. There is literally no reason why, given the steadily escalating fear and anxiety of her crew, who are watching their companion ships get picked off one by one, she doesn’t share the full details with the rebellion. Instead, she leaves it to Poe to figure out that she’s refuelling the transport ships to evacuate – and when he panics, pointing out (correctly) that the transports are neither shielded nor armed, she likewise doesn’t elaborate on the fact that they’ll have a cloaking device to shield them and a destination close by, one where they can land and take shelter while the main ship acts as a decoy.

Because of Holdo’s decision to withhold this information, Poe thinks that she’s given up and is leading them blithely to their deaths, and so stages a mutiny – one in which he’s supported by a number of other, equally worried crewmembers. Happily, Leia recovers from her injuries in time to reclaim control, and only then does she let Poe in on Holdo’s plan. Poe suffers no further consequences for his actions, and even when they talk privately, both Holdo and Leia seem more amused by his mutiny than angry at what he’s done, rendering the whole arc moot. Except, of course, for the fact that Finn and Rose, on their mission from Poe, bring DJ into the mix – and DJ, who knows about the cloaking device, betrays this secret to the First Order, who promptly open fire on the transport ships.

Hundreds of rebellion soldiers die because Poe and Holdo so disliked each other on sight that neither one trusted the other with vital information – and for the rest of the film, this is never addressed. But of course, Johnson can’t address it, not even to hang a fucking lampshade on it, because the entire scenario is manufactured as a way to justify Poe’s protagonist-level screentime while Finn is away – which is also why, contextually, their antagonism doesn’t even make sense. The film begins with the premise that the entire rebellion, who’ve just been flushed out of their single remaining base, is on the run together – so why the fuck haven’t Poe and Holdo met before now? Especially as both are shown to have a close, personal relationship with Leia, it rings utterly false that they’d not only be in the dark about one another, but start out instantly on the wrong foot.

As such, the coding around Poe’s surprise at Holdo – that she’s not what he expected – is a lazy misstep. Traditionally, when hotshot male characters say this about a new female commander, it’s a sexist dogwhistle: oh, I didn’t know we’d be getting a woman. But why would Poe Dameron, son of Shara Bey and devotee of General Leia Organa, be surprised by Holdo’s gender? He wouldn’t, is the answer. Flatly, canonically, he wouldn’t. But if there’s some other aspect of Holdo that’s meant to ping as unusual besides her being female, it’s not obvious. It would’ve made far more sense to write the two as having a pre-existing antagonistic relationship for whatever reason: instead, we get Poe cast as an impatient, know-it-all James Bond to Holdo as Judi Dench’s M, who doesn’t have time for his nonsense when they first meet, but who ends up forgiving it anyway.

It’s like Rian Johnson looked at the Poe Dameron of The Force Awakens – a character universally beloved for being vulnerable, funny, charming, honest, loyal and openly affectionate – and decided, Hey, that guy’s an awesome pilot, which means he’s a COOL GUY, and COOL GUYS don’t play by the RULES, man, especially if it means listening to WOMEN – they just A-Team that shit in secret and to HELL with the bodycount! And anyway he’s HOT, so he’s ALWAYS forgiven.

Dear Rian Johnson, if you’re reading this: I like a lot of what you did with this film, but FUCK YOU FOREVER for making Poe Dameron the kind of guy who gets a bunch of his friends killed, then has a mutiny, then indirectly gets even MORE people killed, and never shows any grief about or cognisance of his actions, all because you wanted to avoid fuelling a homoerotic parallel that you openly queerbaited in promo but never intended to fulfil anyway. GIVE US OUR GODDAMN GAYS IN SPACE, YOU COWARD.

Anyway. 

The point being, the entire plot of The Last Jedi suffers because of a single, seemingly homophobic decision – unnecessarily splitting up Poe and Finn to avoid further Han/Leia comparisons – and the knock-on consequences thereof. Which is where I bring out my metaphorical Red Pen of Plot-Fixing and say, here is what should’ve happened. Namely: Poe and Holdo should’ve had a pre-existing antagonistic relationship, but one that didn’t prevent them from sharing information like grown-ups. Rather than Rose being part of the rebellion, she should’ve been the codebreaker they were sent to retrieve on Holdo’s orders (because two plans are better than one, and why not try both gambits?). This voids the need for DJ, who barely appears before disappearing again, so that Rose-as-codebreaker retains her status as an important, well-fleshed character who interacts with both Finn and Poe, and whose introduction works to map her onto Lando Calrissian. If you really must keep DJ because Benicio del Toro and thematic betrayal parallels (more of which shortly), he can be the dubious guy with First Order secrets that Rose has been trying to recruit for the rebellion, which explains why she’s with him on the casino planet in the first place, and how he’s so easily able to cut a deal with Phasma. BOOM! You’ve just saved a solid 20 minutes of redundant screen-time without degrading Poe’s character or undermining Holdo’s for no good reason and without dumb sexism creeping in. You’re welcome. 

(Also. ALSO. Not to take away from how lovely that Finn/Rose kiss was, but let’s just take a moment to peek into the other timeline, the one where Stormpilot gets to go canon the same way Han and Leia did in Empire. Let’s imagine Finn and Poe bickering in the casino, getting all rumpled during the escape while Rose and BB8 exchange Meaningful Looks and scathing droid-beeps about the two of them. Let’s imagine, during that final battle on Krait, that it’s Poe, not Rose, who stays behind to forcibly knock Finn out of that self-sacrificing dive towards the enemy gun; Poe who grabs Finn and kisses him because they should fight for what they love, not against what they hate, before passing out injured, thus completing the parallel of Han going into carbonite after kissing Leia. Let us gaze upon that world, that glorious thematic act of completion, subversion and queer recontextualisation, and then quietly wish a pox on everything in our cruddy Darkest Timeline that conspired to make it unhappen.)

And now, with all that out of the way, let’s address the Rey/Kylo issue.

As I said at the outset of this piece, I tried my best to avoid spoilers before watching the film, but no matter how quickly I scrolled through feeds or closed my tabs, I still knew that a lot of people had come away rejoicing in the idea that Rey and Kylo were being set up romantically, while an equal number had not.

And I just. Look. While I’m not going to stand here and tell people what to ship or on what basis, both generally and at this historical moment in particular, I find myself with an intense personal dislike of narratives, canonical or otherwise, which take it upon themselves to woobify Nazis, neo-Nazis, or the clearly signposted fictional counterparts thereof, into which category Kylo Ren and the whole First Order falls squarely. I don’t care about how sad he feels that he killed his dad: he still fucking killed his dad, and that’s before you account for the fact that he demonstrably doesn’t give a shit about committing genocide. In the immortal words of Brooklyn Nine Nine’s Jake Peralta: cool motive, still murder. Except for how the motive isn’t actually cool at all, because, you know, actual literal genocide.

From my viewing of the film, I honestly can’t tell if Rian Johnson wants us to think of Kylo as a genuinely sympathetic, redeemable figure, or if he’s just trying to improve on the jarring, horrible botch the prequels made of Anakin’s trip to the Dark Side by showing us his complexity without negating his monstrousness. Or, well: let me rephrase that. In terms of the actual script and what takes place, I’d argue that, even if Kylo is given a final shot at redemption in Episode IX, he’s still not being primed as Rey’s love interest. It’s just that the question of how much Johnson wants us to care about Kylo as a person, regardless of anything that happens with Rey, is a different question, for all that the two are easily conflated.

Yes, Rey and Kylo touched hands. They did! And Kylo killed Snoke instead of Rey! This is what we might call a low fucking bar for romantic compatibility, but hey: it’s not like white dudes in cinema are ever really called upon to jump anything higher. More salient in terms of the Star Wars universe is the fact that, after they defeat Snoke’s guards, Kylo’s appeal to Rey to join him and rule the galaxy together is an almost word-for-word callback to the offer Anakin makes Padme in Revenge of the Sith, right before he force-chokes her into unconsciousness, leaves her pregnant ass for dead and turns into Darth Vader. The fact that Anakin and Padme are also sold as a tragic romance prior to this moment is not, I would contend, the salient hook on which to hang the hopes of canon Reylo. Aside from anything else, Rey is mapped to Luke and Kylo, very clearly, to Darth Vader: with clear precedent, Rey’s desire to turn Kylo back from the Dark Side can be heartfelt without being romantic.

(Also, I mean. The connection that Rey and Kylo had was deliberately forged by Snoke to exploit their weaknesses, which is why they each had a vision of converting the other. Though we’re given a hint that the link remains in the final scenes, it ends with Rey shutting the door – both literally and figuratively – in Kylo’s face. I’m hard-pressed to view that as destiny.)

As for Kylo himself, his characterisation reads to me as deliberate, selfish nihilism. Kylo is conflicted over his murder of Han Solo because it impacts him, but at no point does he hesitate to reign down destruction and death on strangers. His desire to turn Rey to the Dark Side is likewise covetous, possessive: she is powerful, and he wants a powerful companion in the Force, but one who, by virtue of being his apprentice, will be subordinate to him – not a judgemental superior, as Snoke was. This is reflected in the way DJ’s betrayal of Rose and Finn is paralleled with Kylo’s decision to first help Rey when it benefits him, and then to turn on her afterwards. Like DJ, Kylo is mercenary in his allegiances, helping whoever helps him in the moment, then discarding them when the relationship is no longer useful.

The death of Snoke itself, however, is rather anticlimactic. He was a looming, distant figure in The Force Awakens, and while there’s an established tradition of Star Wars villains showing up and looking cool without their origins ever being satisfactorily explained at the time, this is vastly more annoying in Snoke’s case. Unlike General Greivous, Darth Maul or Boba Fett, Snoke isn’t just the random antagonist of a single film, plucked from obscurity to thwart the heroes: he’s the reason Ben Solo turned to the Dark Side and become Kylo Ren. Presumably, the hows and whys of Snoke manipulating the young Ben could still come out in Episode IX, but if it never gets addressed onscreen, I’m going to be deeply irritated.

On a more positive note, I enjoyed what the film did with Luke’s arc, for all that it’s not what I’d expected. To me, one of the most fascinating arguments in Star Wars discourse is the question of the Jedi, their morality, and how it all set Anakin up for failure. The Jedi ideology put forth in the prequels is the kind of thing that sounds superficially deep and meaningful, but which looks increasingly toxic the more closely it’s examined. The ban on children, marriage and close relationships outside the Order; the extreme youth of those taken for training combined with a forcible, protracted separation from their families; the idea that fear necessarily leads to anger, and so on. Luke describing the Force to Rey as something that existed beyond the Jedi, an innate aspect of the world, felt both refreshing and intuitively right, even given the necessity of respecting the balance between light and dark. The appearance of force-ghost Yoda felt a little pat, as did his ability to call lightning, but he still had one of my favourite lines in the whole film, delivered in support of Luke’s choice to step away from the Jedi teachings: as masters, we become the thing they surpass.

There were other, smaller niggles throughout than my issues with Poe and the no-homo restructuring of the plot: the handwaving of distances between Luke’s world and the main fight in a story that hinged on fuel supply; the sudden appearance of trenches and tunnels into the caves on Krait when everyone was meant to be trapped inside; the random appearance of an Evil Ball Droid to play momentary nemesis to BB8; the on-the-nose decision to show a random white slave boy, holding a broom he Force-summoned like a lightsaber, at the very end of the film. And as wonderful as it was to see Billie Lourd on screen, the knowledge that Carrie Fisher will be absent from Episode IX – the film that was meant to have been her movie, just as Harrison Ford had the The Force Awakens and Mark Hamill had The Last Jedi – rendered both her presence and her mother’s all the more bittersweet.

 

Ultimately, The Last Jedi is a successful-but-frustrating mess, which is kind of how you know it’s a Star Wars movie. I’ll be forever angry at the carelessness with which Rian Johnson treated Poe Dameron and Vice-Admiral Holdo, but even if I could’ve wished for a different plot structure, I’m always going to stan hard for Rose Tico, who was warm and kind and intelligent and who stole every scene she was in. LESS REN, MORE ROSE – that’s my new motto.

Here’s hoping that Episode IX delivers.