To say that summer of 2012 was big for geek moviemaking is a vast understatement.  That summer saw the return of Ridley Scott to science fiction filmmaking (Prometheus); it saw the culmination of Marvel’s cinematic “Phase One” and the first ever superhero team up movie (The Avengers); and it saw the first time that a filmmaking team and a major motion picture studio were ballsy enough to bring a definitive end to a hugely successful superhero franchise (recent surprising rumors notwithstanding).

The Dark Knight Rises was intended to bring a definitive close to Christopher Nolan’s “Dark Knight Trilogy” – really, the first time someone on film had taken a character that iconic and decided to give a proper conclusion to their story, instead of leaving off with the typical “there are other adventures in the future” status quo.  Dark Knight Rises took big narrative risks – bringing back D-lister Bane from his cultural death at the hands of Batman & Robin to be the film’s primary villain; introducing the slinky, fun loving Selina Kyle into Christopher Nolan’s dark, serious Batman world; focusing its narrative around a Bruce Wayne at the end of his career, a Bruce Wayne who is older but not wiser, who lets arrogance and ego get the best of him and who is handily defeated in combat.  The final result was polarizing – many thought it a worthy conclusion; many found it disappointing – but the reviews were solid, and like its predecessor Dark Knight Rises managed to make over a billion dollars worldwide.

But you already know all of that, you internet saavy person you; here’s a few things you might NOT know about “The Epic Conclusion to the Dark Knight Saga”…

Write about Film and GET PAID. To find out more about the perks of being a Film contributor at, click here.

This article was first posted on March 25, 2013