19 November 2015
WE SEEM TO BE MADE TO SUFFER. IT'S OUR LOT IN LIFE.
This review is based upon the "Despecialized Edition" prepared by fan editor Harmy, something akin to the original 1980 version. Or, an original version, anyway; this film appeared in multiple cuts even during its initial release.
Has any movie sequel ever had such widespread impossible expectations as The Empire Strikes Back? Has any movie sequel ever so thoroughly surpassed impossible expectations as The Empire Strikes Back? The very first follow-up to the almost unprecedented generational event that was 1977's Star Wars entered theaters in 1980 to some of the most ravenous crowds that had ever anticipated a new blockbuster. And while it was greeted with some small level of bafflement at the time, it has emerged in later years as one of the very small number of sequels to a widely-beloved original that conventional wisdom agrees is probably maybe even better than the first one.
If you want to see that conventional wisdom flouted, you're going to walk away from this review disappointed. Though it's probably the case that in some ineffable way, The Empire Strikes Back is a distinctly less "special" movie than Star Wars. It is not as singular, let us say. If Star Wars is the blueprint for all future Hollywood blockbusters (and in a great many ways, it obviously is), it's still plainly part of the '70s sci-fi boom and the American cinematic landscape of the 1970s generally; the sets and cinematography are the most obvious aspects of that which are true, but they are not alone. In retrospect, we might call it a transitional film, though of course at the time there was nothing to transition to: it was simply a weird attempt at branching the essentials of '70s Hollywood aesthetics into a heretofore unseen direction, and it was fascinating. The Empire Strikes Back, meanwhile, is tangibly a post-Star Wars popcorn film, a genre inaugurated by Superman in 1978 and Star Trek: The Motion Picture in 1979, but not, I think, perfected until right here.
By "perfected" I don't mean that The Empire Strikes Back is the best post-Star Wars film, though it well might be (Raiders of the Lost Ark is the only title I can think of offhand that would challenge it). I mean that, whereas Star Wars, Superman, and Star Trek: The Motion Picture all feel like they were definitely made sometime in the late '70s (or in Star Trek's case, like a hungover version of the 1960s that spent ten straight years locked in the bathroom and then forced to play catch-up), The Empire Strikes Back, like Raiders of the Lost Ark (or Star Trek II: The Wrath of Khan, or Back to the Future, and we can take this through dozens of films all the way up to Jurassic World if we want to), feels detached from time; outside of the ever-evolving technology used to make film and certain narrative tropes more prominent at one time or another, most of the E-ticket blockbusters in the decades since 1980 have felt distinctly same-ish in their attitudes, stylistic choices, and narrative structure - that last one's the fault of Star Wars itself and its hard-on for Joseph Campbell, of course. Most, not all, and "same-ish" can mean a lot of things, if it means anything in the first place. I really only mean this: watch Star Wars, especially denuded of the special edition crap from 1997 and onwards, and you see a film that has the year of its creation etched onto every frame, or at least every frame that doesn't have spaceships in it. That's simply not true of The Empire Strikes Back, a film that could have been made exactly the same way at any point between 1978 and 1991.
While it's not such a strange and unique marvel as Star Wars, though, The Empire Strikes Back makes up for it by being better, or at least deprived of its predecessor's most obvious flaws. For one thing, uniquely among the first six theatrically-released films in the Star Wars franchise, The Empire Strikes Back is almost entirely free of actively shitty dialogue. There are only two points I can point to where Lawrence Kasdan's screenplay reaches the depths of Tosche Station or lakes on Naboo, and both pivot on the tentative romantic bickering between Leia (Carrie Fisher) and Han Solo (Harrison Ford) - a relationship that, persistently, requires the actors to do a great deal of the heavy lifting that the writing can't ever handle - firstly the strained and painful matter of Han's attempt to force Leia to admit that she loves him when he's leaving the station on the frozen planet Hoth, a scene that feels like a screenwriting exercise that never saw a second draft; secondly, the clunky, too desperately "sci-fi" insult "Why you stuck-up, half-witted, scruffy-looking... nerf herder!" and the borscht belt rejoinder "Who's scruffy-lookin'?"
It's probably not an accident that this also the Star Wars film among the first six that has the least tinkering by George Lucas himself. It's the only film for which he didn't materially contribute to the final script. As I understand the way things went, he developed a story with Leigh Brackett, who wrote the first draft of the screenplay; after her untimely death from cancer, Lucas went back to re-write it himself, scrapping most of her specific narrative ideas but maintaining most of her broad concepts. And then Kasdan came down to rewrite the thing top-to-bottom based on this new story.
The real important thing is that this is the only Star Wars film that Lucas had no active hand in directing - he's of course the credited director on four of the six, and it's generally understood that Richard Marquand was his cat's paw in the making of Return of the Jedi. For The Empire Strikes Back, Lucas and producer Gary Kurtz tapped a much stronger directorial presence in the form of Irvin Kershner, a name you almost certainly don't recognise. And it's a damned pity that these days, Kershner's best-known films after this one are probably the bootleg James Bond picture Never Say Never Again and mediocre sequel RoboCop 2, his next and final theatrical features, which provides ample cover to presume that he's a miserable hack. But if we stand in 1980 looking backwards rather than forewards, we see that his two prior features were 1978's giallo-flecked Eyes of Laura Mars and the charming 1976 Barbra Streisand comedy Up the Sandbox. And these are the work of, not an auteur, but a damned competent filmmaker - Eyes of Laura Mars in particular showcases some really excellent thriller directing (it's a better-directed film than Empire Strikes Back, though it is not better overall).
This means lots of things for The Empire Strikes Back, but easily the most important one is that it's so infinitely better as a character story and showcase for acting than Star Wars that it's kind of hard to square the two as containing the same cast. The leads are vastly better: Ford (by far the best of the three last time, but still rocky in places) plays Han's cocky hotshot arrogance with more brittleness now, leaving it much clearer how much of a romantic and patriot he is at heart; Fisher junks her over-enunciated line deliveries and has much clearer intentions for how Leia evolves across the movie, rather than simply what she's thinking in any given instant. Mark Hamill is on some other plane entirely: the callow California boy mien of his Luke Skywalker in Star Wars has evaporated, replaced with a young man who's only slightly more mature but incomparably more thoughtful and aware of his own wants and needs. And not wishing to diminish the trauma of Hamill's January, 1977 car crash that left him with a badly shattered face; but he's much more interesting to look at as a result of it, giving Luke an automatic sense of troubled inner struggle just because of how his eyes and cheekbones work now.
So the characters have more complex arcs this time, thanks in part to the actors finding their roles and Kershner's assistance in making that happen - it's worth noting, the best character beat in the film and maybe the entire franchise, Han's very steady and focused "I know" in response to Leia's "I love you" was an on-set improvisation Ford cooked up with Kershner's encouragement - and also, let's be fair, the film's willingness to go dark. We all know this is the Star Wars that ends unhappily, but frankly, it's also the Star Wars that's ribboned with suffering throughout. Really, there's nothing that goes right for the heroes: the first plot point involves Luke getting lost, attacked by a snow beast, and nearly freezing to death (the film is somewhat bookended by scenes of a mutilated Luke being pieced together in sickbay), and the opening act is dominated an effects-heavy action sequence whose stakes are "run the clock until we can safely run away". Once the film splits into two plots, both of them hinge on failure: one of the two subplots has as its entire narrative spine, "the Millennium Falcon keeps breaking in one different way after another", the other finds Luke having a terrifyingly expressive puppet throwing him one dismissive and disappointed look after another before ending with the sentiment, "well, if he fucks up, at least we have a back-up plan" (does it need saying that Yoda, voiced by Frank Oz and performed by him and fellow Muppet A-lister Kathryn Mullen - let us note that Yoda was made by ILM, not the Henson creature shop - is one of the great pieces of puppet acting in all of cinema? Because Christ Jesus, is he ever convincing and emotive). Star Wars is structured on a chain of increasingly high-stakes triumphs: escape Mos Eisley, rescue Leia and escape the Death Star, blow up the Death Star against all odds. The Empire Strikes Back is structured on a chain of increasingly small-scale losses: flee from the rebel base, break the space ship, lose a one-on-one lightsaber duel.
This isn't some "the film is better because it's grim" thing; this structure gives more room for the characters to have more complicated responses and enjoy their occasional hard-fought small triumphs more, while also making The Empire Strikes Back incredibly interesting. How many giant-scale blockbusters are predicated on the heroes losing at every turn? And yet the magical thing - the magic of Star Wars, or whatever - is that this never turns into any sort of bleak slog. Nothing here is remotely as exciting as the Death Star attack that ends the first film, and the closest equivalent, the battle against the elephantine AT-AT walkers on Hoth, is distinctly lumpy and feels like it was stuck in more to give the film a big setpiece early on. Still, this is a space opera and a fantasy movie before it is anything else, and it acquits itself beautifully. It is not such a swashbuckler, but the film still crackles by at an unflagging pace, slowing only twice: when cross-cutting between Luke's philosophical training and the Cloud City tour where the film happily stops to be charmed right off its feet by Billy Dee Williams's Lando Calrissian, and then at the very, very end, where everybody has failed and is taking time to prepare themselves to move on and keep fighting. Incidentally, I've thought for years that The Empire Strikes Back got to cheat into some of its success, by not having to resolve its plot threads; this is entirely wrong. While it leaves two very obvious sequel hooks open for Return of the Jedi - Luke must deal with the knowledge of his father's identity; the team has to rescue Han - it doesn't feel emotionally incomplete in and of itself. In fact, the unresolved ending is exactly part of why it feels complete: after all of the battering they've taken, the characters regroup, and prepare to fight on. It is an optimistic ending: "we can still fight". The internal emotional arc of the film is strengthened by giving it an unresolved future to look forward to. Heck, that's undoubtedly part of the reason why it's still so much fun despite being nothing but a laundry list of setbacks: it promises that our heroes are unbowed and strong.
Of course, it's also fun because it's a big ol' spectacle. Lucas and Kurtz, having assembled a dream team for Star Wars, surprisingly turned out to be unable or disinterested in retaining it: the only crew heads to return were sound designer Ben Burtt and costume designer John Mollo, while miniature effects director Dennis Muren was promoted (though Star Wars production designer John Barry did come back as second unit director; and if "concept artist" can plausibly be called a crew head position, the invaluable Ralph McQuarrie came back too). But their new artistic team more than met the needs of the film; production designer Norman Reynolds conceived of a more varied, wide-ranging world, to take advantage of the vastly wider scope of the script, and cinematographer Peter Suschtzky brought a terrific command of color that offsets the fact that this film's compositions are generally a bit more two-dimensional and straightforward than the last film. Just think of the exquisite scene in which Luke and Darth Vader (still David Prowse's body with James Earl Jones's voice - and it seems that Jones is way the hell nastier with his line readings this time, don't you think?) square off in a room of plunging blues, almost down to navy, and harsh neon orange, with their lightsabers setting off their dark silhouettes! It is the prettiest scene in a Star Wars film, and splendidly dramatic, and its ascetic, limited palette draws attention wonderfully to the action of the fight.
There really is something to be said for that fight scene all in all: it's a much lower-key lightsaber duel than anything the franchise would see again, but it's absolutely incredible nonetheless. It's the best example in all the franchise of swordfighting-as-storytelling: the way Vader idly thwacks at Luke without being very flashy reveals itself to be a test. We're watching a cat playing with a mouse, almost, except in this case the cat is very curious about the mouse's capabilities and not looking for a meal. That undercurrent sets up this whole climactic sequence to take place on psychological grounds, which pays off wonderfully at the famous "No, I am your father" reveal - I suppose it's shocking in and of itself (though less so if you were born later than 1975), but it also makes sense: all of Vader's behavior in the movie and especially the last sequence is perfectly tuned to push this reveal.
Anyway, there's one other thing that makes the film exciting and fun and tense and all of that, and for the second time in a row (a record that would just keep on going, too), John Williams is pretty much the reason that the film is as great as it is. The score for The Empire Strikes Back doesn't exactly drive the narrative, emotions, and rhythm of the film so bluntly as in Star Wars, and this is another way - maybe the key way - that The Empire Strikes Back feels conventional in a way that Star Wars does not. It is, however, better music - if I were to pop on a Star Wars soundtrack to listen to purely for listening pleasure, it would be the second film rather than the first. In addition to the one-off "The Asteriod Field", a bright, even playful piece of music that ratchets up the tension and speed of its accompanying scene far more than the impressively busy visuals do, Williams adds three incredibly useful motifs to his collection from the last time around. One of these is "Han Solo and the Princess", an evolution of "Princess Leia's Theme" from Star Wars that's slightly lower and dark, heavier in the string section, and doesn't resolve itself as cleanly - it's a breathtakingly beautiful, yearning romantic theme. Another is "Yoda's Theme", a subdued, warm theme that adds a softer but still aching counterpart to the intense, mournful "Force Theme" from Star Wars.
And there's the big guy, the best-known piece of Star Wars music after the brassy, adventurous "Luke's Theme" that accompanies all of the opening crawls: "The Imperial March", a dominant minor-key rumble of evil. It might be the best march Williams ever composed, and they're possibly the thing he does best: the "Raiders March" the Superman "Main Theme", and the easily-overlooked "March from 1941" are all masterworks of film composition, and "The Imperial March" tops all of them (maybe not Superman. That's a hell of a theme. But still). Coupled with the shiny blackness of Vader himself, the image and sound form some of the most iconic moments in all of popcorn cinema.
There are, to be sure, enough flaws in The Empire Strikes Back that it's hard even with this best of all Star Wars pictures to give credence to the fannish insistence that it is one of the great achievements in cinema - not even little flaws, some of them are gaping. This film being rather more serious and adult-facing than Star Wars, the pieces stuck in there kids are glaring: I have no particular problem with the neurotic robot C-3PO and Anthony Daniels's fluttery performance of him in Star Wars nor in Return of the Jedi, but his comic relief is galling here, particularly when he interrupts one of the most insinuating statements of the romantic them in the film. And the film feels a bit stiff the entire time it's on Hoth, unsure of how to reintroduce characters (Leia gets a splendid wordless reaction shot, but then a clumsy dialogue dump), choppy in the way it advances plot, and for all its creativity and top-notch effects work, the battle sequence squelches the narrative momentum in a way that I refused to notice when I was 10.
What The Empire Strikes Back has the great fortune to do is to get increasingly better as it moves along, even as it narrows its focus; the smaller the scale, the more profound the feelings attached, and the more heaving and dramatic the visuals, and the more aching Williams's score. It ends with one of its very best sequences, sad and hopeful, soaring on the score, grandiose in the visuals - and there's no popcorn movie better than a popcorn movie that saves the best for last.
9/10
Reviews in this series
Star Wars (Lucas, 1977)
The Empire Strikes Back (Kershner, 1980)
Return of the Jedi (Marquand, 1983)
Star Wars: Episode I - The Phantom Menace (Lucas, 1999)
Star Wars: Episode II - Attack of the Clones (Lucas, 2002)
Star Wars: Episode III - Revenge of the Sith (Lucas, 2005)
Star Wars: The Force Awakens (Abrams, 2015)
Has any movie sequel ever had such widespread impossible expectations as The Empire Strikes Back? Has any movie sequel ever so thoroughly surpassed impossible expectations as The Empire Strikes Back? The very first follow-up to the almost unprecedented generational event that was 1977's Star Wars entered theaters in 1980 to some of the most ravenous crowds that had ever anticipated a new blockbuster. And while it was greeted with some small level of bafflement at the time, it has emerged in later years as one of the very small number of sequels to a widely-beloved original that conventional wisdom agrees is probably maybe even better than the first one.
If you want to see that conventional wisdom flouted, you're going to walk away from this review disappointed. Though it's probably the case that in some ineffable way, The Empire Strikes Back is a distinctly less "special" movie than Star Wars. It is not as singular, let us say. If Star Wars is the blueprint for all future Hollywood blockbusters (and in a great many ways, it obviously is), it's still plainly part of the '70s sci-fi boom and the American cinematic landscape of the 1970s generally; the sets and cinematography are the most obvious aspects of that which are true, but they are not alone. In retrospect, we might call it a transitional film, though of course at the time there was nothing to transition to: it was simply a weird attempt at branching the essentials of '70s Hollywood aesthetics into a heretofore unseen direction, and it was fascinating. The Empire Strikes Back, meanwhile, is tangibly a post-Star Wars popcorn film, a genre inaugurated by Superman in 1978 and Star Trek: The Motion Picture in 1979, but not, I think, perfected until right here.
By "perfected" I don't mean that The Empire Strikes Back is the best post-Star Wars film, though it well might be (Raiders of the Lost Ark is the only title I can think of offhand that would challenge it). I mean that, whereas Star Wars, Superman, and Star Trek: The Motion Picture all feel like they were definitely made sometime in the late '70s (or in Star Trek's case, like a hungover version of the 1960s that spent ten straight years locked in the bathroom and then forced to play catch-up), The Empire Strikes Back, like Raiders of the Lost Ark (or Star Trek II: The Wrath of Khan, or Back to the Future, and we can take this through dozens of films all the way up to Jurassic World if we want to), feels detached from time; outside of the ever-evolving technology used to make film and certain narrative tropes more prominent at one time or another, most of the E-ticket blockbusters in the decades since 1980 have felt distinctly same-ish in their attitudes, stylistic choices, and narrative structure - that last one's the fault of Star Wars itself and its hard-on for Joseph Campbell, of course. Most, not all, and "same-ish" can mean a lot of things, if it means anything in the first place. I really only mean this: watch Star Wars, especially denuded of the special edition crap from 1997 and onwards, and you see a film that has the year of its creation etched onto every frame, or at least every frame that doesn't have spaceships in it. That's simply not true of The Empire Strikes Back, a film that could have been made exactly the same way at any point between 1978 and 1991.
While it's not such a strange and unique marvel as Star Wars, though, The Empire Strikes Back makes up for it by being better, or at least deprived of its predecessor's most obvious flaws. For one thing, uniquely among the first six theatrically-released films in the Star Wars franchise, The Empire Strikes Back is almost entirely free of actively shitty dialogue. There are only two points I can point to where Lawrence Kasdan's screenplay reaches the depths of Tosche Station or lakes on Naboo, and both pivot on the tentative romantic bickering between Leia (Carrie Fisher) and Han Solo (Harrison Ford) - a relationship that, persistently, requires the actors to do a great deal of the heavy lifting that the writing can't ever handle - firstly the strained and painful matter of Han's attempt to force Leia to admit that she loves him when he's leaving the station on the frozen planet Hoth, a scene that feels like a screenwriting exercise that never saw a second draft; secondly, the clunky, too desperately "sci-fi" insult "Why you stuck-up, half-witted, scruffy-looking... nerf herder!" and the borscht belt rejoinder "Who's scruffy-lookin'?"
It's probably not an accident that this also the Star Wars film among the first six that has the least tinkering by George Lucas himself. It's the only film for which he didn't materially contribute to the final script. As I understand the way things went, he developed a story with Leigh Brackett, who wrote the first draft of the screenplay; after her untimely death from cancer, Lucas went back to re-write it himself, scrapping most of her specific narrative ideas but maintaining most of her broad concepts. And then Kasdan came down to rewrite the thing top-to-bottom based on this new story.
The real important thing is that this is the only Star Wars film that Lucas had no active hand in directing - he's of course the credited director on four of the six, and it's generally understood that Richard Marquand was his cat's paw in the making of Return of the Jedi. For The Empire Strikes Back, Lucas and producer Gary Kurtz tapped a much stronger directorial presence in the form of Irvin Kershner, a name you almost certainly don't recognise. And it's a damned pity that these days, Kershner's best-known films after this one are probably the bootleg James Bond picture Never Say Never Again and mediocre sequel RoboCop 2, his next and final theatrical features, which provides ample cover to presume that he's a miserable hack. But if we stand in 1980 looking backwards rather than forewards, we see that his two prior features were 1978's giallo-flecked Eyes of Laura Mars and the charming 1976 Barbra Streisand comedy Up the Sandbox. And these are the work of, not an auteur, but a damned competent filmmaker - Eyes of Laura Mars in particular showcases some really excellent thriller directing (it's a better-directed film than Empire Strikes Back, though it is not better overall).
This means lots of things for The Empire Strikes Back, but easily the most important one is that it's so infinitely better as a character story and showcase for acting than Star Wars that it's kind of hard to square the two as containing the same cast. The leads are vastly better: Ford (by far the best of the three last time, but still rocky in places) plays Han's cocky hotshot arrogance with more brittleness now, leaving it much clearer how much of a romantic and patriot he is at heart; Fisher junks her over-enunciated line deliveries and has much clearer intentions for how Leia evolves across the movie, rather than simply what she's thinking in any given instant. Mark Hamill is on some other plane entirely: the callow California boy mien of his Luke Skywalker in Star Wars has evaporated, replaced with a young man who's only slightly more mature but incomparably more thoughtful and aware of his own wants and needs. And not wishing to diminish the trauma of Hamill's January, 1977 car crash that left him with a badly shattered face; but he's much more interesting to look at as a result of it, giving Luke an automatic sense of troubled inner struggle just because of how his eyes and cheekbones work now.
So the characters have more complex arcs this time, thanks in part to the actors finding their roles and Kershner's assistance in making that happen - it's worth noting, the best character beat in the film and maybe the entire franchise, Han's very steady and focused "I know" in response to Leia's "I love you" was an on-set improvisation Ford cooked up with Kershner's encouragement - and also, let's be fair, the film's willingness to go dark. We all know this is the Star Wars that ends unhappily, but frankly, it's also the Star Wars that's ribboned with suffering throughout. Really, there's nothing that goes right for the heroes: the first plot point involves Luke getting lost, attacked by a snow beast, and nearly freezing to death (the film is somewhat bookended by scenes of a mutilated Luke being pieced together in sickbay), and the opening act is dominated an effects-heavy action sequence whose stakes are "run the clock until we can safely run away". Once the film splits into two plots, both of them hinge on failure: one of the two subplots has as its entire narrative spine, "the Millennium Falcon keeps breaking in one different way after another", the other finds Luke having a terrifyingly expressive puppet throwing him one dismissive and disappointed look after another before ending with the sentiment, "well, if he fucks up, at least we have a back-up plan" (does it need saying that Yoda, voiced by Frank Oz and performed by him and fellow Muppet A-lister Kathryn Mullen - let us note that Yoda was made by ILM, not the Henson creature shop - is one of the great pieces of puppet acting in all of cinema? Because Christ Jesus, is he ever convincing and emotive). Star Wars is structured on a chain of increasingly high-stakes triumphs: escape Mos Eisley, rescue Leia and escape the Death Star, blow up the Death Star against all odds. The Empire Strikes Back is structured on a chain of increasingly small-scale losses: flee from the rebel base, break the space ship, lose a one-on-one lightsaber duel.
This isn't some "the film is better because it's grim" thing; this structure gives more room for the characters to have more complicated responses and enjoy their occasional hard-fought small triumphs more, while also making The Empire Strikes Back incredibly interesting. How many giant-scale blockbusters are predicated on the heroes losing at every turn? And yet the magical thing - the magic of Star Wars, or whatever - is that this never turns into any sort of bleak slog. Nothing here is remotely as exciting as the Death Star attack that ends the first film, and the closest equivalent, the battle against the elephantine AT-AT walkers on Hoth, is distinctly lumpy and feels like it was stuck in more to give the film a big setpiece early on. Still, this is a space opera and a fantasy movie before it is anything else, and it acquits itself beautifully. It is not such a swashbuckler, but the film still crackles by at an unflagging pace, slowing only twice: when cross-cutting between Luke's philosophical training and the Cloud City tour where the film happily stops to be charmed right off its feet by Billy Dee Williams's Lando Calrissian, and then at the very, very end, where everybody has failed and is taking time to prepare themselves to move on and keep fighting. Incidentally, I've thought for years that The Empire Strikes Back got to cheat into some of its success, by not having to resolve its plot threads; this is entirely wrong. While it leaves two very obvious sequel hooks open for Return of the Jedi - Luke must deal with the knowledge of his father's identity; the team has to rescue Han - it doesn't feel emotionally incomplete in and of itself. In fact, the unresolved ending is exactly part of why it feels complete: after all of the battering they've taken, the characters regroup, and prepare to fight on. It is an optimistic ending: "we can still fight". The internal emotional arc of the film is strengthened by giving it an unresolved future to look forward to. Heck, that's undoubtedly part of the reason why it's still so much fun despite being nothing but a laundry list of setbacks: it promises that our heroes are unbowed and strong.
Of course, it's also fun because it's a big ol' spectacle. Lucas and Kurtz, having assembled a dream team for Star Wars, surprisingly turned out to be unable or disinterested in retaining it: the only crew heads to return were sound designer Ben Burtt and costume designer John Mollo, while miniature effects director Dennis Muren was promoted (though Star Wars production designer John Barry did come back as second unit director; and if "concept artist" can plausibly be called a crew head position, the invaluable Ralph McQuarrie came back too). But their new artistic team more than met the needs of the film; production designer Norman Reynolds conceived of a more varied, wide-ranging world, to take advantage of the vastly wider scope of the script, and cinematographer Peter Suschtzky brought a terrific command of color that offsets the fact that this film's compositions are generally a bit more two-dimensional and straightforward than the last film. Just think of the exquisite scene in which Luke and Darth Vader (still David Prowse's body with James Earl Jones's voice - and it seems that Jones is way the hell nastier with his line readings this time, don't you think?) square off in a room of plunging blues, almost down to navy, and harsh neon orange, with their lightsabers setting off their dark silhouettes! It is the prettiest scene in a Star Wars film, and splendidly dramatic, and its ascetic, limited palette draws attention wonderfully to the action of the fight.
There really is something to be said for that fight scene all in all: it's a much lower-key lightsaber duel than anything the franchise would see again, but it's absolutely incredible nonetheless. It's the best example in all the franchise of swordfighting-as-storytelling: the way Vader idly thwacks at Luke without being very flashy reveals itself to be a test. We're watching a cat playing with a mouse, almost, except in this case the cat is very curious about the mouse's capabilities and not looking for a meal. That undercurrent sets up this whole climactic sequence to take place on psychological grounds, which pays off wonderfully at the famous "No, I am your father" reveal - I suppose it's shocking in and of itself (though less so if you were born later than 1975), but it also makes sense: all of Vader's behavior in the movie and especially the last sequence is perfectly tuned to push this reveal.
Anyway, there's one other thing that makes the film exciting and fun and tense and all of that, and for the second time in a row (a record that would just keep on going, too), John Williams is pretty much the reason that the film is as great as it is. The score for The Empire Strikes Back doesn't exactly drive the narrative, emotions, and rhythm of the film so bluntly as in Star Wars, and this is another way - maybe the key way - that The Empire Strikes Back feels conventional in a way that Star Wars does not. It is, however, better music - if I were to pop on a Star Wars soundtrack to listen to purely for listening pleasure, it would be the second film rather than the first. In addition to the one-off "The Asteriod Field", a bright, even playful piece of music that ratchets up the tension and speed of its accompanying scene far more than the impressively busy visuals do, Williams adds three incredibly useful motifs to his collection from the last time around. One of these is "Han Solo and the Princess", an evolution of "Princess Leia's Theme" from Star Wars that's slightly lower and dark, heavier in the string section, and doesn't resolve itself as cleanly - it's a breathtakingly beautiful, yearning romantic theme. Another is "Yoda's Theme", a subdued, warm theme that adds a softer but still aching counterpart to the intense, mournful "Force Theme" from Star Wars.
And there's the big guy, the best-known piece of Star Wars music after the brassy, adventurous "Luke's Theme" that accompanies all of the opening crawls: "The Imperial March", a dominant minor-key rumble of evil. It might be the best march Williams ever composed, and they're possibly the thing he does best: the "Raiders March" the Superman "Main Theme", and the easily-overlooked "March from 1941" are all masterworks of film composition, and "The Imperial March" tops all of them (maybe not Superman. That's a hell of a theme. But still). Coupled with the shiny blackness of Vader himself, the image and sound form some of the most iconic moments in all of popcorn cinema.
There are, to be sure, enough flaws in The Empire Strikes Back that it's hard even with this best of all Star Wars pictures to give credence to the fannish insistence that it is one of the great achievements in cinema - not even little flaws, some of them are gaping. This film being rather more serious and adult-facing than Star Wars, the pieces stuck in there kids are glaring: I have no particular problem with the neurotic robot C-3PO and Anthony Daniels's fluttery performance of him in Star Wars nor in Return of the Jedi, but his comic relief is galling here, particularly when he interrupts one of the most insinuating statements of the romantic them in the film. And the film feels a bit stiff the entire time it's on Hoth, unsure of how to reintroduce characters (Leia gets a splendid wordless reaction shot, but then a clumsy dialogue dump), choppy in the way it advances plot, and for all its creativity and top-notch effects work, the battle sequence squelches the narrative momentum in a way that I refused to notice when I was 10.
What The Empire Strikes Back has the great fortune to do is to get increasingly better as it moves along, even as it narrows its focus; the smaller the scale, the more profound the feelings attached, and the more heaving and dramatic the visuals, and the more aching Williams's score. It ends with one of its very best sequences, sad and hopeful, soaring on the score, grandiose in the visuals - and there's no popcorn movie better than a popcorn movie that saves the best for last.
9/10
Reviews in this series
Star Wars (Lucas, 1977)
The Empire Strikes Back (Kershner, 1980)
Return of the Jedi (Marquand, 1983)
Star Wars: Episode I - The Phantom Menace (Lucas, 1999)
Star Wars: Episode II - Attack of the Clones (Lucas, 2002)
Star Wars: Episode III - Revenge of the Sith (Lucas, 2005)
Star Wars: The Force Awakens (Abrams, 2015)
29 comments:
Just a few rules so that everybody can have fun: ad hominem attacks on the blogger are fair; ad hominem attacks on other commenters will be deleted. And I will absolutely not stand for anything that is, in my judgment, demeaning, insulting or hateful to any gender, ethnicity, sexual orientation, or religion. And though I won't insist on keeping politics out, let's think long and hard before we say anything particularly inflammatory.
Also, sorry about the whole "must be a registered user" thing, but I do deeply hate to get spam, and I refuse to take on the totalitarian mantle of moderating comments, and I am much too lazy to try to migrate over to a better comments system than the one that comes pre-loaded with Blogger.
Tim, you better damn well do the Star Wars Holiday Special by this Christmas. It has been too long since we saw a 0/10 review.
ReplyDelete@Moviemotorbreath: In preparation for the new movie, my friend is marathoning Star Wars trilogies on consecutive weekends. Having gone through the good trilogy and the mediocre trilogy, he's now planning to screen the bad trilogy.
ReplyDeleteI know that it doesn't _really_ deserve it Tim, but can you at least consider giving Attack of the Clones a 0/10?
ReplyDeleteNot Fenimore, please tell me your buddy is doing a write-up of this adventure somewhere...
ReplyDelete@moviemotorbreath: Tim's already given us three this year. I fear we are too close to breaking him already.
ReplyDeleteAfter revisiting these first three films recently, I was surprised to find the asteroid field scene to be the second most exciting Star Wars action set piece (after the Death Star raid from the original, of course). Holy crap--that score. And those Tie Fighters bouncing off the rocks. Perfection.
ReplyDeleteI second @moviemotorbreath's motion.
ReplyDeleteWhat kind of person do you all take me for? Of course I'm going to be reviewing the Holiday Special. Not the Ewok pictures - yet - and I second Trish's question: Not Fenimore, is your friend writing about his awful, wonderful experience?
ReplyDeleteNot that I know of, but I can ask. ;)
ReplyDeleteI think this movie wrecked us all for Star Wars as a whole. If it hadn't been so freaking unbelievably amazing we might have remembered the series as a really good, kind of dumb movie that was a lot of fun, and its disappointing sequels. Instead, Empire raised the bar for what a Star Wars movie should be, and there's no going back. I don't think that the prequels would ever have been considered "good" by any stretch, but there wouldn't be such a level of vitriol hurled at it. Nobody ever sent death threats over the Matrix Reloaded and nobody gave up acting because of a role in a Police Academy sequel, but with Star Wars everything is measured by the original trilogy, and the original trilogy is basically a two very similar movies propped up by one incredible middle film that, I think, did more than Star Wars itself to define Star Wars.
ReplyDeleteI feel like after the first movie Luke, Vader and the Death Star had become iconic, but it took this movie to really cement the iconography of the rest of the saga. I didn't discover the trilogy until 1989 and I was still in diapers when Return of the Jedi came out, so I'm throwing out a theory based on guesswork. But what do we picture when we think Star Wars? Han and Leia's romance, Darth Vader's enormous villainy, Han Solo's total badassery, the Millennium Falcon as a great ship that's always breaking down. Some of that's teased in the first one, and none of it shows up at all in the second, really. For all of his stomping around and chewing scenery, Vader spent the first movie as another villain's lackey, and the third hamstrung by a deep and necessary case of conflicted emotions. But in Empire, he commands an entire fleet, viciously murders his underlings that displease him, tortures Han for no reason and then has him essentially entombed alive as an afterthought. The Millennium Falcon is bragged about in Star Wars but never actually does anything but jump to hyperspace at the right time. This time we get to see just what it's capable of. The ship is a character in its own right, and the film-long attempt to repair it turns it into not just a friend, but a friend in desperate need. And there's nothing between Han and Leia in Return of the Jedi that sizzles anywhere close to the Scoundrel scene, or the "I love you" "I know" moment in Empire.
And a single tossed off line at the very beginning, "That bounty hunter we ran into on Ord Mantell" immediately suggests a whole slew of adventures these characters have had in the interim, had without us, that makes us realize how much more we want to see their continued adventures. And thats' the reason we have a (now defunct) Extended Universe that tended to copy Empire more than the other two movies.
One thing that I don't think gets talked about enough with this film is just how clean it is from a thematic perspective, something alltogether impressive given how piecemeal the script allegedly was in development. The main drive of the film is obviously Luke's internal struggle, one that I think is fairly clearly centered around his own search for identity--of discovering who he is and what he might become. This is pretty textual in the cave scene, which in hindsight is a nice bit of foreshadowing of the ending, but when encountered in context can only be read as Luke fearing that he might succumb to the dark side and become like Vader.
ReplyDeleteThis struggle dovetails into the big thematic goal of the film, which is to take the necessarily black-and-white morality of the original film and start casting it in shades of grey. This is where your points about the more complex arcs and the increasing sense of failure really set in, because virtually every point in the movie is creating in some small way a wider sense of morality and consequences--we start to see a darkness in Luke and a romanticism in Han, and Leia is put in a position between them that she struggles with (though this gets shot in the foot with the retcon in the next film--watching it without that knowledge and the film is pretty clearly setting up Leia to make a choice between two sides of her life). The good guys don't always win, the mentors aren't completely pure in intention, and not all the bad guys are evil incarnate.
Which leads us to Lando and Vader, who are the most obvious declarations of the shaded morality in the film, with Lando being a fundamentally good person that betrays his friends for what he believes to be good purposes, and Vader suddenly gaining some human sympathy with the revelation that, even as much as he's being manipulative and treacherous, he is actually trying to save his son in the only way he thinks he can. And with Luke having struggled with his internal identity the whole film, what better way to confront that than with the revelation that the man that believes to be the most evil person in the universe is actually his father?
This is I think the main emotional drive of the film, and one of the reasons why it does feel so emotionally conclusive at the end. Plot points are left hanging, but the main internal conflict--Luke's struggle for identity--is resolved rather gracefully in the "Father?" scene onboard the Millennium Falcon. Luke isn't completely healed, and the struggle isn't completely over, but he at least comes to terms with the truth, and is visibly a more mature and prepared individual by the end of the film. It's a remarkably clean and layered film thematically, which is so unusual and rewarding to see in such an overtly popcorn film as this.
Some friends and I did our own retrospective on Star Wars in podcast form over the course of this year (to pimp myself out a little, our episode on Empire can be heard here: http://twofriendswatch.libsyn.com/star-wars-the-empire-stikes-back). Tl;dr: we concur with the consensus and this review, that Empire is by far the best Star Wars feature, and the only one I'm willing to offer entirely unqualified praise. In addition to the across the board technical and aesthetic excellence, the trim, character driven narrative, the thematic weight and symmetry and the supremely well-judged management of tone (with the exception of some of C-3PO's unwelcome intrusions) make it close to my ideal popcorn movie.
ReplyDeleteI think Empire is astonishingly well made, but watching it often leaves me with a sense of frustration. At times, it feels like the story is not unfolding naturally, but is more concerned with producing an emotional response in the audience. Darth Vader could have grabbed Han and Leia the moment that they set foot in Cloud City. Instead, he hangs back for a while. I don’t see any reason for Vader to do this except to create suspense, and to allow the audience to gain an impression of Lando. It’s like Vader knows that he’s the villain in a movie.
ReplyDeleteTo take another example, at the beginning of the movie Luke is attacked by a large animal. This happens *just after* he announces that he’s been scanning the area for life forms and hasn’t detected any. I suppose it’s possible that the Rebel scanners weren’t designed to detect Wampas, but it feels like a cheap gotcha moment. There’s a similar scene in the first movie where Luke is ambushed by sandpeople. But before it happens, the movie makes it clear that the sandpeople are there and that Luke is behaving foolishly. The movie plays fair and I jumped anyway. Empire affects me more than Star Wars, but it also makes me feel more manipulated.
I do like the way that Empire expresses dark emotions. The lightsaber duel isn’t just one sided, it’s filmed in a way to suggest that’s a form of child abuse. It nicely sets up the Oedipal revelation. It also taps into certain emotions that I wouldn’t necessarily expect to find in space adventure movie.
It's perhaps a little immersion-breaking how Frank Oz used his Grover voice for Yoda, but it still would've fit my image of him, and it's nowhere near immersion-breaking as how much Endor is obviously the California redwoods.
ReplyDeleteAnd now you're imagining, say, Big Bird as Luke, Ernie as Han, and Miss Piggy (or Bert) as Leia. You're welcome.
PS: Empire did make the cover of Time magazine this time around; possibly even bumping back the story of Mt. St. Helens (erupted four days before Empire's release) by a week.
http://time.com/vault/year/1980/
@Tim, @Trish: I got myself an invite, I'm writing it up!
ReplyDeletePrayers for the safety of my immortal soul are appreciated. :P
A series of excellent points, laid out in a calm, rational manner, detailing all of the things Empire does right to create a more subtly shaded and emotionally rich experience than its predecessor.
ReplyDeleteAnd yet, I still prefer Star Wars. Go figure.
Aaron - I always saw Vader's decision to wait as a bit of sadistic gamesmanship. They can't go anywhere and he's got tone to kill before Luke, the one he's really after, shows up, so he's going to let them start to feel safe and let their guard down. They're less likely to try to run then (and probably escape yet again), and being captured and tortured just when everything was supposed to be better for everyone just makes it hurt more. Also the Wampa was really just there to smash Luke's face in before anybody got a good look at him, to give an in-movie explanation for the reconstructive surgery Hamill needed after his accident. If I felt like being nitpicky about an element of the movie, is probably go with the way the cross-cutting between Luke and the Falcon's storylines means either Luke trained on Dagoba for a couple of hours or the Falcon spent weeks being chased through an asteroid field.
ReplyDeleteAs I understand the way things went, he developed a story with Leigh Brackett, who wrote the first draft of the screenplay; after her untimely death from cancer, Lucas went back to re-write it himself, scrapping most of her specific narrative ideas but maintaining most of her broad concepts.
ReplyDeleteYes and no, maybe? According to your friend and mine, Lawrence Kasdan:
George had hired Leight the way anyone would - because, oh my God, she's Leigh Brackett, and because he wanted a Hawksian, goading humor between Han Solo and Princess Leia. But Leigh couldn't serve George the way he wanted to be served. Out of all our respect for her, she was always going to get a credit for the movie, but if you get your hands on her draft you won't find one item that's in the finished film.
And more:
Look, there's no question that Leigh Brackett was one of the great screenwriters of all time. But it was an odd job for her, and there's nothing of that draft left in Empire. Not to say it's all me. The truth is these movies are all George. I wouldn't say that of Raiders, but I would say that of the Star Wars movies.
Brian- "If I felt like being nitpicky about an element of the movie, is probably go with the way the cross-cutting between Luke and the Falcon's storylines means either Luke trained on Dagoba for a couple of hours or the Falcon spent weeks being chased through an asteroid field."
ReplyDeleteThat's what I always thought too, but I was really looking for it this time, and it's not as clusterfucky as we might think. The asteroid chase takes us up to the scene where Yoda raises the X-Wing out of the swamp - which is still a hell of a lot of training for one day, and still a hell of a long time in the asteroid field, given that we know Luke spends a full night on Dagobah (it's when the Falcon is inside the space worm).
Han announces that he's going to head to Lando and Cloud City at sublight speeds, and then the action cuts to Luke's day of training that involves levitating R2-D2 and fighting Illusion Vader, so we can assume that weeks have passed.
That still leaves Luke's first day of training feeling pretty crowded, but it's not like Beauty and the Beast-style discontinuity.
Ryan- Interesting. I've never read the draft, so I won't hardly contradict Kasdan. My understanding was that a cloud city (but not Cloud City), a small Jedi master (but not at all Yoda), a planet named Hoth (but not an ice planet and the Rebels weren't based there), and the intimation of another Force adept in the galaxy (but not presented in remotely the same manner as "There is another...") were all present in Brackett's draft, among other similarly multiple-generations-removed echoes.
I suppose they could have spent a day or two in the space worm trying to fix the ship, before realizing it was a space worm, but that makes it the most lackadaisical interstellar predator ever.
ReplyDeleteEverybody likes to point out how few of the characters in Star Wars are female (sausage fest to say the least), but I think that argument is most relevant in this installment. Imagine if Lando Calrissian was in fact a woman, a femme fatale-like character. She could be a former love interest for Han Solo that would provide a perfect foil towards Han and Leia's sexual tension throughout this movie. I feel like it's a missed opportunity in my opinion.
ReplyDeleteYeah, as good as Empire is, it's by far the *worst* of the films in terms of female representation and agency--Leia is literally the only woman in the entire film, and she's saddled with the rather ickily-executed romance plot. I think Return does worse things to her character, but on the whole Empire fares the worst for feminist readings.
ReplyDelete@Brian Malbon: A day inside the space slug? 0_o Its metabolism must be slower than that of the Sarlacc.
ReplyDeleteHaven't really thought much about the passage of time in SW until reading these comments. I guess I always assumed that Luke's training and the Falcon's flight aren't shown simultaneously and we only see the highlights. Heh, maybe Dagobah has a very fast rotation so days are much shorter. And Tatooine might also have days well shorter than 24 hours, so Luke would be used to it. More realistically, how much time do you think Han and co. spent on Cloud City before being captured?
"aren't shown simultaneously"
ReplyDeleteMeant to say the events themselves aren't perfectly simultaneous.
Andrew - is not the sort of thong you think about during the movie,mostly because they do such an excellent job of keeping you from asking silly questions. Unfortunately if you devoured all the novels and devoted a great deal of your adolescence that you could have spent chasing girls to memorizing all aspects of a continuity that no longer officially exists, these little nitpicks tend to rear their heads a lot more.
ReplyDeleteBrian – I agree that the wampa attack (or the equivalent) was necessary in light of Hamill’s injuries. However, I think that the script did a poor job of setting it up. If Luke had been doing *anything* other than scanning the area for animals, it would be easier to believe that he could be ambushed by an animal.
ReplyDeleteRegarding Vader’s decision to hang back in Cloud City, as I understand it his plan was to cause Han and Leia to suffer so that Luke would sense it and try to rescue them. I suppose Vader’s line of thinking was, “I intend to harm Luke’s friends at some point in the future. Therefore, Luke will have a vision of the future in which they are being harmed.” Of course, this plan assumes that Vader knows what visions Luke will have and when he will have them. From Vader’s perspective, it seems like the safest choice would be to harm Han as soon as possible. Or better yet, don't rely on Luke having visions at all. Instead, set up a straightforward prisoner exchange.
I think that Empire is a great work of cinema. But I when I watch a movie, I often find myself wondering what it would be like to be part of the story. In the case of Empire, I can’t imagine being in the story because the story doesn’t seem to hang together. Some issues are minor, like C-3PO’s obsession with probabilities, even though originally it was R2-D2 that gave probabilities. Other issues are more serious. The snowspeeder pilots choose to fly head on against walkers, even though the walkers can only shoot targets that are in front of them. The Empire places a blockade around Hoth, except that when the first rebel transport tries to escape, it only encounters a single Star Destroyer that is easily dealt with. When Luke tries to leave Hoth, he meets no resistance whatsoever. At the same time, many ships are pursuing the Falcon.
By the time we get to Cloud City, is Vader even fighting the rebels anymore? He had two high ranking members of the rebellion (or three counting Chewie), but he didn’t ask them to divulge the location of the rebel rendezvous point. They might not have talked, but he didn't even try. Maybe by then, Vader really was ready to join Luke and part ways with the Empire?
Empire works well on an emotional level, but I think the plot is pretty patchy. I have the impression that the screenwriters (whoever they were) knew exactly where they wanted to go with the story, but they didn’t care too much about how they got there. I agree that they did a great job keeping us from thinking about these things.
As long as we're nitpicking details, how the hell did the Millennium Falcon escape Hoth with Vader just standing there watching? If the Force enabled Yoda to pull an x-wing out of the swamp, why couldn't Vader grab the Falcon and pull it back? For that matter, why couldn't Vader crash the troop carriers that most of the rebel army was in and win the war right there?
ReplyDeleteI have to disagree with T. Hartwell's analysis of the ending, however. The point of the big reveal is not that Vader isn't so bad after all. The point is that Luke's father is pure evil. The whole film has been Luke's effort to follow in the footsteps of his father, whom he's been led to believe was a hero. This film's powerful ending is Luke's loss of innocence, his discovery that the focal point of his life was a lie, that his hero is actually a villain, and that the footsteps in which he is walking lead to the worst place.
Add to your short list of returning personnel Stuart Freeborn, makeup artist and creature designer. But the addition to the crew I always found odd was Brian Johnson as visual effects supervisor. He had previously supervised the space scenes in Space 1999 and Alien. I've always wondered exactly what he brought to the production that ILM's staff couldn't have.
ReplyDeletePoor Hayden Christensen. He was great in SHATTERED GLASS, playing a role that didn't suck, but he'll be remembered forever as Anakin. Not every actor can overcome George Lucas's dialogue.
ReplyDelete