Saturday, June 22, 2013

The Belated "Man of Steel" Review

It's been a while since the last time we had a Superman movie, namely 2006's underwhelming "Superman Returns". In that movie, we got a Superman take that did little more than jerk off the legacy of Richard Donner's classic film of the 70s as well as present to us a Superman that was more of a wanky emo brooder turned Super-stalker. Needless to say, not many liked it, and Warner Bros. and DC decided that rebooting it was the best course of action.

Fast forward to 2013, and here we are with "Man of Steel": a more modern take on the classic superhero as envisioned by director Zack Snyder ("300", "Watchmen") and producer Christopher Nolan. Now without further adieu, here comes my belated review of "Man of Steel", so strap yourselves in assholes.

Be warned, spoilers aplenty are ahead:

"Man of Steel" presents a much harder look at the Superman mythos than has ever been presented in film form before. It also packs some of the most unbelievable wanton acts of destruction to probably ever be seen in a summer blockbuster or "disaster porn" film. Seriously. Metropolis gets obliterated so much that it's amazing there's anything left of it. In those regards, the action sequences are brilliant and the wanton acts of destruction are set pieces that I personally have always wanted to see in a Superman film.

The casting and characterizations are mostly well done as well. While main star Henry Cavill didn't leave the lasting impression on me that someone that plays Superman rightfully should be able to do, the rest of the principal cast was mostly great, in particular Russell Crowe as Jor-El. Even Kevin Costner as Supes' earthbound Papa Kent does great in limited screen time, but it's Michael Shannon that really stole the show for me as General Zod. He isn't Terrance Stamp, and who could be, but he leaves a lasting impression. I also enjoyed Amy Adams as Lois Lane and Laurence Fishburne as Perry White (irony!).

Now, here's what so many fans have been having a shit-fit about: the ending. Yes, Superman kills Zod in the film's conclusion. He breaks his neck like a twig to stop Zod from killing more innocent civilians and screams in sorrow at what he's been forced to do. Now I know what you're thinking because I thought the same exact fucking thing when I saw it happen on the big screen: since when the fuck does Superman kill? In retrospect, the idea itself is infuriating, because if it's one thing that Superman stories have been telling us SINCE THE FUCKING 1930s is that Superman always finds another way to save the day. Superman is supposed to represent the best in humanity and put himself over the law...or something. Well, here he broke Zod's neck.

Now, looking back on it, while seeing that bothered the shit out of me, I think I understand why Snyder, Nolan, and screenwriter David Goyer went down this route. Maybe since this was an origin story, they're going to use Superman killing Zod as a benchmark for future events, as to something that Superman can never, ever bring himself to do again, and this is the beginning of Supes deciding to "find a better way" to save the day without having blood on his hands.

That, or maybe film executives still don't get Superman after all these years.

Either way, regardless of its flaws, I enjoyed "Man of Steel" for what it's worth, even more so than I enjoyed "Avengers" or most of the Marvel movies since 2008. That's right, I said it. And since its huge opening weekend, Warner is fast-tracking a "Man of Steel" sequel to lead into an eventual "Justice League" movie. Part of me wants to see that all happen, and part of me doesn't, only because it would never be quite as huge as "Avengers". "Avengers" has the monopoly on safe, family-driven popcorn entertainment that's fairly okay for kids, while DC's properties seem to be going in a darker direction (which I love) that looks like it'll eventually lead into making kids shit themselves.

In 3-D.

Anyway, go check out "Man of Steel", fuck the haters.

No comments:

Post a Comment