The Dark Knight Rises: 9 Things Nolan Should Have Done

1. Left Batman as Gotham€™s Protector

Possibly one of the most hotly contested topics of recent months is the trilogy-ending finale of Nolan€™s run on the Batman franchise. Some are arguing that it was the perfect way to complete a Batman story, others, usually the comic book fans (and I include myself when I say this group), felt that it was nothing short of a slap in the face. They say the more you know, the lonelier you get. It€™s easy to feel alone, when you know in your heart of hearts that Batman would do the exact opposite of something that he€™s done in a movie that the vast majority of the audience ate up. But if you know Batman, how can you share in this jubilation? Imagine you came home one day, and your father was just€ someone else, but no one around you seemed to see it? That€™s how many of us feel about Nolan€™s Batman €“ you can troll me all you like, that€™s just the way it is. The devil is in the details; Nolan having Batman effectively abandon his post as Gotham€™s protector because he €˜just can€™t hack it any more€™, is probably in direct opposition with what we know, as a character, he would do. All it€™d have taken to fix was one tiny adjustment too, and then we could all have had our cake and eaten it: John Blake enters that Batcave, finding himself alone. As he explores a final shot reveals Batman waiting in the shadows. Batman looks at Blake and says €œwelcome home€. Credits. Or at least something along those lines. This way, Nolan€™s ending remains intact, and an army of Batman fans aren€™t left wondering why the hell Batman just pussied out of his own mission at the very last moment. So, undoubtedly, a few of you have more to add, and some of you have some venom to spill. Do let us in on it, you lovely (most of the time) people.
Contributor
Contributor

Stuart believes that the pen is mightier than the sword, but still he insists on using a keyboard.