Jay: THIS WAS THE EPISODE I WANTED SINCE SEASON ONE.
Let me explain. I always wanted a Sabine-centric episode like this. We got a few, but I wanted to learn about Sabine the same way we learned about Ezra. We got her story teased instead: Imperial Academy references early on, and we knew she was a Mandalorian, and something happened with her family. But that’s it. The episodes were as tight-lipped about Sabine’s background as Sabine herself was. And despite our impatience, it makes perfect sense: Sabine doesn’t just volunteer this information. It’s a slow burn, once she gets to trust you.
But here there was a payoff and boy was it a payoff. This episode was elegantly simple: the training was the entire plot, so it could focus on character work. It meant there was room for it to be an ensemble episode: Ezra, Kanan, and Hera all got great character moments in addition to Sabine. And we learned a ton about Sabine, featuring some of the finest character work yet seen in this show. For my money, this was the best episode in the series to date.
We saw the characters engaging with their histories and biases, engaging with each other — having flare ups and drama. And goodness, if there was any episode to get on the day of the Women’s March, this was it. In addition to Sabine’s history, I love that Hera both called Kanan on his crap and also helped Sabine out as well.
Goodness, what an episode. » Read more..
Baze was terrified. Chirrut was not. In the instant before he’d risen from the bunker, he’d questioned his own wisdom: How might be separate the will of the Force from his will, his ego, demanding action where action was unneeded? But there was no doubt in his heart now. The Force expressed itself through simplicity, and all it asked of him was to walk.
I am one with the Force and the Force is with me.
Is Chirrut Force-sensitive?
The more we learned about him prior to the release of Rogue One, the more people found themselves asking this question. Cassian Andor even comes close to asking the question himself within the movie, and the answer Baze Malbus gives him isn’t much more definitive than the one Rogue One offers viewers: he’s no Jedi.
That much is clear—Chirrut is not currently, nor was he ever, a Jedi Knight. He’s part of a new group called the Guardians of the Whills; devout followers of the Force, but not necessarily wielders of it. Baze certainly seems content with his giant-ass cannon. But that’s not usually what people mean when they ask, is he Force-sensitive? What they mean is, could he have been a Jedi? Is the Force warning him when a blaster bolt is about to come his way? With training, could he levitate things, perform mind tricks, and so on?
Personally, I doubt it. But to look at what Chirrut can do and ask “what if?” is to miss the point of Chirrut’s abilities entirely. » Read more..
Eeeeevery once in a while, Reddit produces something good. About a week ago, a user in the Star Wars subreddit posted a gif highlighting a particular background Mon Calamari actor in Return of the Jedi who was apparently given the direction “look confused“, and stuck with that strategy throughout the Battle of Endor. The gifs quickly jumped to Star Wars Twitter, and we all had a good laugh. Totally pointless little detail, but it brightened everybody’s day for a moment.
It called to mind an old memory of mine from way back when The Phantom Menace came out. As the first, and weirdest, Star Wars prequel, TPM was notable for just how little context we had for everything that was happening—far more so than for The Force Awakens, even. So it was that I (or maybe a friend I was with?) noticed the little PK droids in the background of the Trade Federation battleship and said “oh look, baby stormtroopers!” Obviously that wasn’t the case, but the notion that stormtroopers began life as these little dudes who did grunt work for the Trade Federation has stuck in my head all these years. To this day, I can’t help but notice them in the background and smile to myself, though no amount of explaining could ever really get across to somebody why I find them so amusing.
Star Wars is rife with little things like that; moments of whimsy, as George would say. And with all the weighty developments both in- and out-of-universe lately I thought it’d be fun to lighten up for a moment and ask the others: what’s the one little detail in the films that cracks you up every time? » Read more..
Mike: While last week’s two-parter obviously had a much more overt link to the larger narrative of the Rebellion in the form of Saw Gerrera, this episode struck me as having much more to say about the war itself, via the Empire’s differing approach to finding rebel bases here compared to the opening of The Empire Strikes Back. At first I wasn’t crazy about the idea of an Imperial probe droid stumbling upon Atollon so soon, and I’m still not a fan of the possibility that the Phoenix cell will eventually flee Atollon for Yavin (though that’s another topic entirely), but as the episode unfolded I caught lots of key details that changed how I saw what was happening.
First of all, of course, it’s not a probe droid—not technically. This thing is designated an “infiltrator” droid, and rather than immediately report its findings, it’s designed to blend in at any potential base for an indeterminate amount of time. While both it and the probe droid have self-destruct mechanisms, the infiltrator’s is substantially more powerful. I could be wrong, but this suggests to me that it may well have been designed to transmit its findings to the Empire and then go ahead and detonate itself anyway.
Why wouldn’t they want the standard probe droids to do that, too? Paradoxically, I think the more bad-ass infiltrator model implies that the Empire, even Thrawn, isn’t taking the rebels as seriously yet as they are in ESB. Where probe droids appear to be more basic models built to cover huge areas of space without actually engaging in hostilities, the infiltrator plays a more delicate game, and could have taken Chopper Base out all on its own—or at least, that’s what it’s designed for. » Read more..
About one and a half years ago, we got the first cast picture for Rogue One, and the general consensus (myself included) was celebration of the ethnic diversity, followed almost immediately by dismay at the heavily male cast. But after the first trailer surprised us all with the appearance of Mon Mothma I was hopeful for Rogue One and optimistic that there would be more women. Unfortunately, my fears were proven right when I finally sat down in the theater to watch the movie and it turned out to be a pretty big sausage fest. An ethnically diverse (and quite attractive) sausage fest, yes, but still a sausage fest.
It’s disappointing because I had high hopes for a movie whose cast represented a range of countries and ethnicities. I was hoping it would continue in the thread of The Force Awakens and make a concerted effort to show a wide range of women as well; I’ve written before on the lack of women of color in Star Wars and I was hoping Rogue One would prove me wrong. But it goes to show that allyship in one area doesn’t always translate to allyship in another. We should definitely celebrate when Star Wars does well. But we should also accept that it will make mistakes…and as fans we should hold it accountable when it does.
It’s hard to admit when things we love aren’t as perfect as we’d like them to be. I’ve found this to be especially with something like Star Wars, where people tend to structure their entire identity around the fandom. So I understand wanting to rationalize away the flaws rather than admit that our favored franchise didn’t put its best foot forward. And there’s been a rash of rationalizations as of late: Leia’s slave bikini is empowering because she uses it to kill Jabba. Padmé didn’t die of a broken heart, Palpatine actually drained her life essence to save Anakin. Rogue One doesn’t show a lot of women in the Rebellion because they were trying to be faithful to how it looked in A New Hope. » Read more..