“Across the Sea”
May 11th, 2010
[For more discussion of the episode, check out my breakdown and analysis of critical responses to “Across the Sea.” Also, for a review of the series’ penultimate episode, What They Died For, click here]
Do metaphors count as answers?
It’s the question I found myself returning to throughout “Across the Sea,” a story which feels so designed to discover answers that it never quite achieves a narrative in its own right, although I don’t necessarily mean that as a slight to its effectiveness. However, while you could argue we get some facts and details that help us piece together previous events, there is very little of what one would call “clear” answers in the hour. What we get are extended metaphors meant to give meaning, rather than clarity, to that which has happened before and that which will happen in the future.
Considering the breadth of questions we as an audience have at this stage in the show’s run, there is no chance that the show will ever be able to make everything perfectly clear, and when tonight’s episode actually tried to provide “answers” it often felt unnatural, inorganic. Where the episode worked best is in using metaphors and abstract ideas to solidify human emotions and character motivations: this is the story of Jacob and his nameless twin brother (who we’ll call Esau for the sake of the Biblical connection, even if their mother’s name makes it less than perfect), but it both implicitly and explicitly gestures to what we’ve seen unfold on the island for six seasons, and in doing so gives greater meaning to that journey even if the “why” question remains unanswered.
I don’t think “Across the Sea” is by any means perfect, but I think it did a most admirable job at crafting a story which crystallizes the show’s journey thus far, worrying less about the big picture and more about establishing where the individual portraits the show has created fit into the mysteries of the island (which may remain unsolved).
May 13th, 2009
“It only ends once. Anything that happens before that…it’s just progress.”
After last week’s penultimate episode, there were two paths moving forward: one was John Locke leading a group of Others and Benjamin Linus to kill the man known as Jacob, and the other was Jack Sheppard heading out to drop a hydrogen bomb into the Swan Station and rest the entire show as we know it.
What was so fascinating about these two paths is that you are convinced, at about the halway point of “The Incident,” that neither will truly happen. The latter is far too big of a series reboot for them to risk this late in the series’ lifetime, and the former seems premature considering that we haven’t even met this mysterious Jacob who runs this island and now we’re just going to kill him, just like that? But the episode just kept going: the closer you got to its conclusion, the more you realized that there really wasn’t anything standing in the way of these events at all except for our own expectations.
What Carlton Cuse and Damon Lindelof did with this episode was toy with the viewers in a way that they only can, and in one of the only ways I’ll admit I downright love. In an episode where the first scene was the most important, and where the inevitable became questionable and the predicted was thrown entirely on its head, they managed to take a scenario that sounded too simple and complicate it beyond any reasonable expectation. In one fell swoop, they rewrote the events of the entire season, opening up a metric ton of new questions just as the final shot in many ways made everything fair game for the show’s final season, all the while situating the show’s characters in the right place for the action to come.
There are some key reasons why this isn’t quite Lost’s best finale, but in terms of its technique I’d say that Lindelof and Cuse have certainly tapped into something that will yield some fantastic results in the show’s sixth and final season.