My biggest issues with the Hunger Games trilogy were both things that have gone unchanged in the film adaptations. The structural sameness of the three books may have had a purpose, but it particularly affected my enjoyment of the second book, Catching Fire, where it felt lazy and formulaic rather than meaningful. The same can be said for the books’ close first-person perspective, which I found particularly limiting in the glimpses of a bigger conflict in Catching Fire that the perspective gave the books no chance to explore.
What I found most interesting about my response to The Hunger Games: Catching Fire, Francis Lawrence’s adaptation of what I identified as the least successful of the novels back in 2011, is that I liked it much more than its predecessor despite the fact it doubles down on these elements. Some of this has to do with how “first-person perspectives” function differently in literature vs. film, certainly, but I think it’s also a case in which one of the film’s most potentially frustrating choices successfully neutralizes one of the book’s biggest problems.
[Spoilers for the film, and then separately marked spoilers for the series, follow]
October 20th, 2013
Last year, The New Yorker’s Emily Nussbaum had a theory about Homeland. She argued that Sgt. Nicholas Brody’s panicked communications with Abu Nazir as Carrie Mathison was held hostage were all an act, and that he was in on the plan from the beginning.
It was an interesting theory, one she gave me credit for partially debunking by noting that Abu Nazir and Brody continue speaking in the same manner once Carrie is no longer listening to their conversation. For me, that was the sign that the theory couldn’t work: while an interesting idea, I did not believe Homeland was a series that would so actively mislead the viewer with information that—in hindsight—would contradict the intended truth of the situation.
If you saw last night’s episode of Homeland, and have been following some of the subsequent conversation, the above may sound familiar. Indeed, this season’s central storyline almost feels inspired by Nussbaum’s theory, as though the writers took it as a challenge as to whether the series could sustain a twist that in retrospect contradicts many of the storylines and character actions displayed in earlier episodes and maintain its reputation.
The response to “Game On” suggests that they can’t, but that doesn’t necessarily mean I’m no longer on board.
“Tower of David”
October 13th, 2013
It’s been a few months since I watched the first two episodes of Homeland‘s third season. They were made available to press ahead of the show’s panel at the Television Critics Association press tour, which was logical—in that it allowed those in attendance to ask informed questions rather than random guesswork—but also daring. It was daring because in the two episodes screened for critics, Nicholas Brody did not appear for even a brief sequence, and yet Damian Lewis was seated on the panel at the Beverly Hilton.
I tweeted in advance of that panel that I was interested to see how the room responded to this (among other facts about Homeland‘s third season, specifically the increased focus on Morgan Saylor’s Dana), but Showtime was quick to offer clarification: a trailer revealed early footage of Brody’s first appearance in “Tower of David,” and the panel confirmed he would return in the very next episode beyond the ones we had seen. Part of me had expected them to treat Brody’s return as a surprise, leaving his fate open-ended, but from the beginning Brody was something the series was very open about, creating a certain suspense to see how the show planned on reintegrating the character into the narrative.
“Tower of David” works as a structural exercise in character development, drawing a parallel between Brody and Carrie’s respective prisons. However, it fails to acknowledge and mitigate the issues that plagued the two characters’ development last season, leaving an episode that works up until the point you look into the past rather than the present/future.
September 29th, 2013
A series finale is different from any other episode of a television show; the biggest test for a series finale is whether or not it feels different from any other episode of that television show.
Breaking Bad has been an often messy show, driven by complex moral agency and characters who seem simultaneously the architect and the victim of chaos. It was a series that continued to grow in scale but largely followed the same principles of tight characterization and almost claustrophobic connections with those characters. In the show’s third season, it delineated between “half measures” and “full measures,” and the series was ultimately a narrative driven by the former: while some were explosive and others were tragic, there was never a moment when one could say that Breaking Bad had solved or even dramatically mitigated its central conflict.
It was this quality that gave the series its momentum, and enabled it to grow an audience of devotees from a series that many people—myself included—had not given much of a chance in its early seasons. It was also this quality that by the very nature of a series finale was forced to change in “Felina,” a clean end to a messy show that very purposefully limits its capacity to embody the series it brings to a conclusion.
June 9th, 2013
“Here only the family name matters.”
As Varys explains this fact to Shae, he’s being pragmatic: he’s trying to help someone whose very existence at King’s Landing threatens her own life and the life of the man she loves. Varys acknowledges that she has made Tyrion better. Varys acknowledges that hers is a true love. And yet Varys also gives her a collection of diamonds, telling her to sail to Pentos and start a new life for herself so that her love can do something good for Westeros without the threat of a single-named woman hanging over him.
It’s dark advice, advice that Shae refuses to take. Despite the fact that we just saw both Robb Stark and Talisa die for following true love over pragmatism, and despite the fact that Jon Snow just took three arrows from the woman he loves, Shae proves what many other characters have learned as well: there is still power in love even when all signs would suggest that trusting in such power will be your undoing.
“Mhysa” is about this love, which may seem strange in light of the fact that last week ended on such a foreboding sendoff for Robb and Catelyn Stark. And yet Game of Thrones needed a new motivation beyond ascending to the throne, a sense of purpose that could evolve beyond the War of the Five Kings and the deaths of Robert Baratheon and Ned Stark which set it off. What “Mhysa” seeks to accomplish is reframe the actions of its characters not as part of a larger power struggle, but rather as actions designed to protect their families or to protect the realm. This is not to say that we are to support the Lannisters’ cruelty or to endorse Melisandre’s sorcery, but rather that we can shift our understanding of their actions away from a part in a larger plot and instead toward what motivated them to take those steps in the first place.
It’s an enriching move that works to build a strong foundation for future seasons, although one that has some issues retroactively making some of the season’s storylines resonate in the way intended. “Mhysa” concludes a third season that was only retroactively revealed—for non-readers, at least—to be the season where Game of Thrones could no longer be simplified to a battle between the Starks of Winterfell and the Lannisters of Casterly Rock, one that did its job without necessarily connecting in the process.
“The Rains of Castamere”
June 2nd, 2013
“The closer you get, the worse the fear gets.”
Every season of Game of Thrones has built to a big event in the season’s ninth episode. As a result, the end of each season has continually created a conflict between those who have read the books and those who haven’t: the pattern means that both parties know the season is building to something major, but only those who have read the books know what that is. This wouldn’t be as much of a problem if those people didn’t really, really want to talk about it.
In the first season, I would say fans mostly tried to keep quiet about Ned Stark’s death. The first season hinged on Ned’s story, and the initial shock of his beheading gave the show its big hook that could make casual viewers into fans and help sustain the show moving forward. In the second season, the Battle of Blackwater Bay was a fairly spoiler-free form of anticipation, as there’s nothing to really spoil: no one major dies, Stannis’ attack on King’s Landing is never kept a secret, and the episode was more about execution than surprise (and well-executed it was).
The third season was always going to be the problem. The “Red Wedding” has been on the tips of readers’ tongues since they read the books, considered by most to be the definitive moment in the series. It’s the moment that makes Ned’s death look like just a drop in the bucket, and the clearest evidence of George R.R. Martin’s wanton disregard for his own characters and their happiness. From the time the show first sprung into existence, this has been the moment that book readers were waiting for, and by the time it arrived in the third season there was no longer any concern about letting viewers engage with the series on their own terms out of fear for its future. This season has all been a buildup to this moment, to the point where the phrase “Red Wedding” was something that even those who tried to avoid spoilers were probably familiar with because readers could not contain themselves.
“The Rains of Castamere” arrives with intense expectation, and like many other book readers I sat through the episode with a slightly higher heart rate. As much as I think the fans went too far in proliferating the use of “Red Wedding” and hyping this particular episode as noteworthy, thus providing non-readers enough information to potentially spoil the episode’s conclusion, I can understand why they were excited, and felt that excitement in the moments leading up to the episode and throughout. This is as intense an hour of television that Game of Thrones will produce over the course of its run, and I’d argue it’s a particularly well-executed adaptation that makes some smart choices to salt the wounds left behind by this most storied of literary–and now televisual—weddings.
“Endless Forms Most Beautiful”
June 1st, 2013
When I attended the Television Critics’ Association Winter Press Tour in January, BBC America presented a panel for Orphan Black, a new drama series originating from Canada (where it airs on Space). It was an interesting panel to attend, because none of the critics in the room had no opportunity to watch it: while we were shown a quick trailer to help give us context, most of the questions were actually asking for more information as opposed to specific responses to the series. What we saw looked interesting, and the panel was enjoyable, but it was an exploratory exercise in a space where greater context is necessary to achieve any real insight.
Reading back over the transcript of that panel, and revisiting this fun interview Will Harris did with the three stars in attendance, I couldn’t help but smile. In retrospect, there are plenty of hints there about the show Orphan Black would become: a fearless, balls to the wall science fiction pleasure that’s smart as hell. Co-creator Graeme Manson was asked about the possibility of flashbacks, to which he responded “Yeah, actually, none at all. We really, really like a story that’s like a runaway train that keeps you on the edge of your seat and has you not sure whether the story is going to take a hard left or a hard right.” Tatiana Maslany was asked about the challenge of playing multiple roles, and explained “Yeah, it’s a challenge, the different arcs. You know, there’s so many arcs to it. So it’s a bit of a mind — I keep wanting to say the wrong word.”
The wrong word is the right word in this case: Orphan Black is a mindfuck, and ends its first season with another segment in the runaway train first season, one that becomes four climaxes in one by the time it reaches its conclusion.
May 19th, 2013
“I always have a choice.”
“Second Sons” opens with a choice. Arya wakes up to discover that her captor has fallen asleep, and picks up a rock with which she intends to kill Sandor Clegane, a man she believes to be taking her back to King’s Landing. However, as she grows closer, it turns out the Hound isn’t sleeping at all, and he gives her a choice: she can put the rock down, or she can take one shot at killing him with it. The catch is that, should she choose the second option and the Hound remains alive, he’ll break both of her hands.
It’s not really a choice when you think about it, as Arya’s trust in her own strength isn’t quite enough to make her hands worth the risk. It’s also not much of a choice given that she’s his captive, even if he intends to take her to Robb and Catelyn on the Twins as opposed to taking her to King’s Landing and the Lannisters. As much as Arya struggles against the place in life that was determined for her, and as much as she tried last week to go back to the independence she craves, she still finds herself in a position where choices are not available to her.
It’s far from a complicated theme, but what I like about “Second Sons” is the resignation of it all. Arya sitting on the Hound’s lap as he rides toward the Twins is an evocative image, both because of the beautiful countryside mirroring Arya’s hope at seeing her family and because she’s not bound or tortured or anything of the kind. Rather, she’s accepted her fate as the fate put before her, and will comply if only because it’s the most effective way to survive until the day where you have choices you did not have before.
It’s a position that comes to bear on many episodes as the season goes on, as characters struggle with the lack of agency that comes naturally with being born—or being treated—as a second son.
May 5th, 2013
“If you think this has a happy ending, you haven’t been paying attention.”
“The Climb” begins with three groups of characters who share a common goal: reaching The Wall. While Jon and Ygritte are with the wildlings as they prepare to scale it, Bran and Sam are moving toward the Wall from opposite directions.
For viewers, The Wall has been a prominent object for the series, one of the first images we saw to introduce a sense of the scale of Westeros. It’s a prominent part of the credits, sure, but it was also key to the series’ prologue. When Jon Snow saw the Wall for the first time, it was a formative moment for the character, just as it’s foretold as a prominent moment for Gilly, who can’t even imagine the stories Sam tells her about the structure. It’s something so large that it persists even for those who have never laid eyes on it, something that holds power even when the vast majority of its expanse lies unguarded. The Night’s Watch may be in charge of protecting the Wall, but the Wall does most of the protecting itself, a single crack in the ice capable of nearly killing the entirety of the Wildling party.
The “Game of Thrones” would be difficult enough if its only threat were static obstacles like The Wall (or the threat of the White Walkers beyond it, which is ostensibly still the most prominent threat to the entirety of Westeros). But “The Climb” isn’t a solitary activity, something that you can survive on your own: there’s always someone there to cut your rope, or stand in your way, or give your life new—often less—meaning at the drop of a hat. With its central metaphor, “The Climb” reminds us that no climb is without the threat of not simply missing a foothold but someone doing everything in their power to make sure that no foothold even exists, a dark and often foreboding episode that despite closing on a hopeful moment offers little evidence of hopefulness overall.