Showing posts with label the Empire Strikes Back. Show all posts
Showing posts with label the Empire Strikes Back. Show all posts

Monday, July 10, 2017

Sci-Fi Cast Away: Star Wars #33

The following is my review of Star Wars #33, which was posted on PopMatters.com.


In terms of a modern mythos, complete with philosophical, psychological, and cos-playing implications, Star Wars is the standard by which all others are measured. Few other sagas, from Marvel's ever-evolving continuity of reboots and retcons to multiple eras of Star Trek, even come close. It manages to be both incredibly expansive, yet remarkably concise. It's themes, emotions, and drama create a perfect blend that gives it a special place in popular culture.

Given the sheer breadth and scope of Star Wars, it's easy to forget that there are various parts that remain unexplored. Ever since Disney and Marvel began expanding some of those unexplored areas, new elements of that mythos are emerging. Given the iconic status that Star Wars has for generations of fans, it's a careful balancing act. There are only so many ways that Star Wars can be expanded without undermining the larger narrative. Even an iconic mythos cannot withstand the force of too many Jar Jars.

Jason Aaron manages that balancing act better than most, taking full advantage of the gap between A New Hope and The Empire Strikes Back to flesh out elements of Star Wars that never get a chance on a movie screen. One element that never gets much development is the relationship between Luke and Leia. Even without knowing their secret sibling connection, so much of the drama is centered around Leia's constant clashes with Han. It's easy to forget that her story is closely tied to Luke. Aaron, with the artistic talents of Salvador Larroca, use Star Wars #33 as an opportunity to explore that story.

The setup is simple, if not unremarkable by Star Wars standards. Luke and Leia get stranded on a planet that's mostly water and dotted with a few small islands. The circumstances are fairly generic in that it's not part of some larger story arc. It's just another case of a routine mission going horribly wrong, which seems to happen at least once a week for the Rebellion. There's nothing about it that rattles the continuity of the original trilogy. It's basically the sci-fi equivalent of Cast Away, but with more sea monsters and fewer volley balls.

This bland, but simple setup does serve an important purpose though. It puts Luke and Leia in a position where they have to work together and rely on each other to survive. They know they can survive an onslaught of storm troopers and escaping the Death Star. They've even shown they can survive working with Han Solo for more than two weeks and survive. However, their strength is often defined by their ability to be part of a team. They're rarely in a situation where they can only rely on each other.

It makes for some compelling moments, exploring some of the inner struggles within both characters. It's easy to forget between blowing up the Death Star and falling in love with a smuggler that Luke and Leia are still processing some major upheavals. A part of Luke still sees himself as a farm boy and a part of Leia still sees herself as a princess, complete with all the ceremonial formalities. What stands out in Star Wars #33 is just how uneasy they both feel with their previous roles.

There's a distinct sense that being a farm boy never sat well with Luke. Leia shows a similar sentiment. She reveals that at one point, she ran away to escape some of the formalities that come with being a princess. While this puts her at odds with most traditional Disney princesses, it reveals an important element to both characters.

On some levels, they sense that their situations in life aren't right. They sense that they're meant for something else. Aaron gives the impression that the Force is somehow letting them know that their story is tied with that of Darth Vader and the legacy of Anikan Skywalker. They don't know this, given the story's place in the existing Star Wars timeline. However, they do feel it. If it is a manifestation of the Force, then Yoda himself would be proud.

Beyond the personal exploration, there's also some reflection on recent events, relative to the outcome of A New Hope. Leia is still mourning the destruction of Alderan. The emotions don't get too heavy, though. Leia comes off as more hardened than most princesses. She's no Cinderella, but she's no Elsa either. If she ever broke into song, it wouldn't be very uplifting.

These moments of personal insight and inner character struggles are the highlight of Star Wars #33. While they succeed at providing greater insight into Luke and Leia, as characters, the rest of the narrative falls somewhat flat. Their struggles for survival on the island never create much strain. At most, they only ever seem inconvenienced by their situation. There's never any despair, anguish, or strain. Despite one of them being a princess and the other being a farm boy, their outlook on the situation is remarkably dispassionate.

There are some elements that keep the story from becoming too much like Cast Away. They eventually find out that the planet isn't as desolate as they think. That helps put them in a position to escape and even make a few new allies. However, that story is lacking in terms of detail and insight. It comes off as just a simple, convenient way to get Luke and Leia off the planet before readers can start making incest jokes.

There's nothing about the story in Star Wars #33 that feels out of place, out of character, or inconsistent with the larger mythos. Even if parts of the story lack details, it never comes off as flawed or incomplete. The primary strength of the narrative is the deeper exploration of Luke and Leia, as characters.

When all is said and done, they both come off as more complex characters, which can only give greater weight to the iconic narrative that is Star Wars. While that won't stop some fans from cracking incest jokes about Luke and Leia, Star Wars #33 will give them a greater appreciation for who they are as characters. Anyone hoping for more than that, though, is asking too much of the Force.

Final Score: 6 out of 10

Monday, October 26, 2015

Covert Subversion: Darth Vader #11

The following is my review of Darth Vader #11, which was posted on PopMatters.com.


Most people learn about dramatic irony in high school English classes, albeit only by reading novels and plays that no teenager has willingly read since the 1830s. It's an important storytelling tool. It puts the reader in a position to understand the context of a story in a way that isn't possible for any of the characters, unless one of those characters happens to be Deadpool. By knowing what the characters can't know or having already seen the sequel, the story takes on a new meaning. It can either enhance the subsequent stories or make them more needlessly complicated than the plot of the last Matrix movie.

Kieron Gillen has been attempting to accomplish the former and avoid the latter in Marvel's Darth Vader series. And by nearly every measure, he has succeeded. In fact, he's succeeded in measures nobody has expected.

He doesn't expect the readers to rely the events of the Empire Strikes Back and Return of the Jedi, two movies that have been effectively spoiled since 1983. He actually attempts to build a comprehensive story about Darth Vader in wake of the Death Star's destruction. And he does it in a way that somehow makes Vader even more menacing. Even James Earl Jones' voice might not do justice to the persona he's crafted.

More than anything else, Kieron Gillen's work on Darth Vader has crafted a story that laid the seeds for the events in Return of the Jedi. He succeeds where Revenge of the Sith failed so spectacularly in that he's made Darth Vader more than the emperor's puppet. He's shown that unlike the character Hayden Christiansen played in the movies, Darth Vader is capable of following his own agenda. And he's been doing so with help from a cast of surprisingly compelling characters in Aphra, BT, and Triple-0. But in Darth Vader #11, this agenda begins to clash with that of the emperor. Something has to give and it can't give until Luke loses a hand and Han takes a carbonite bath.

This means the story has to unfold in a careful, tactful way. That's not easy to do in a story that involves Darth Vader, an army of Stormtroopers, and a less-than-ethical archaeologist like Aphra. But somehow, Gillen manages to navigate this fragile narrative with the skill of a brain surgeon. He's very careful to mix in details that will later show up in the Empire Strikes Back, but not to the point that it would trigger another Han/Greedo situation.

This kind of attention to detail is refreshing in an era where continuity gaffs and retcons happen every other Thursday. Gillen channels his inner Stanley Kubrick, making sure every major and minor detail is addressed. And he does this without creepy twins or Jack Nicholson. Even with all these details, he still finds a way to include battles involving Stormtroopers, blasters, and light sabres. With no gungans or pod racers in sight, classic Star Wars fans will find plenty to enjoy.


But it's the use of dramatic irony that makes this story more satisfying than just seeing Stormtroopers get shot. This is where Thanoth, Darth Vader's new nemesis/ally, shows more competence than the average Imperial officer. Throughout this series, Vader has been subverting the Emperor, pursuing his own private agenda with Aphra. Being Darth Vader, he's made it look as easy as outsmarting Homer Simpson at times. That's no longer the case with Thanoth.

He's not Boba Fett. He's not Jar Jar Binks either. Thanoth is a Star Wars anomaly of sorts in that he's actually a competent bureaucrat. He's not content to just check out at five o'clock and count down the days until he can collect a pension. He sensed there was something not right about Darth Vader's latest covert mission and he's been investigating it, much to Vader's chagrin. It creates one of those situations where you know both of them can succeed without one of them being screwed over.

This marks the first time in this series where Darth Vader has to covertly help Aphra. He's only partially successful. This makes for some powerful moments where Vader is genuinely torn between his private agenda and his loyalty to the Emperor. Were he not Darth Vader, he might get nervous like Lance Armstrong during a drug test.


But the fact remains he is Darth Vader. He is the menacing Sith Lord that's destined to chop off Luke's hand and kill the Emperor. And his ability to pull this off under the watchful eye of someone like Thanoth is most impressive, even by Darth Vader's standards. He's very careful and covert in his ability to manipulate the battle. So he's not just a menacing Sith Lord with a light sabre. He's a menacing Sith Lord that knows how to use deception and tact.

These aren't just traits that neither Hayden Christiansen nor James Earl Jones can hope to capture. These are traits that add a complexity to Darth Vader that really didn't show until Return of the Jedi. The fact that Darth Vader is willing to go to such lengths to deceive the Emperor makes it more believable that he will eventually turn on him. Sure, it still takes the near-murder of his son, but it helps it feel less forced.

Darth Vader #11 acts as a culmination of sorts where Darth Vader's agenda finally clashes with that of the Emperor. It's a clash that's not quite on the level as the Battle of Hoth or the Battle of Endor. No planets blow up and nobody gets a hand chopped off. But it has all the necessary details. It conveys a refined, concise narrative that fits perfectly into the existing Star Wars mythos. And most importantly, it does this without gungans or Trade Federations.

Final Score: 9 out of 10