Wednesday, November 28, 2012

Batman, Inc in the DCnU

Batman, Incorporated began on the final pages of Batman and Robin #16, a postscript to that story and a prologue to a new one. The publication history is torturous: Batman: The Return introduced the menace of Leviathan, then eight issues of Batman, Incorporated ran before plans were altered or postponed by the DC Universe's reboot in Flashpoint. Then what should have been two issues was run under the title "Leviathan Strikes." Since then, six other issues have been published, restarting the numbering of a series which had barely begun. So five numbers have been used twice, there were two one-shots, and we have an issue #0 which was, if this bit of confusion means anything, presented with a splash page saying it was "Before the new 52" although it was published in the middle of the other numbers and there are no identifiable glitches in continuity between then and now. To muddy the waters a bit more, Batman, Inc #5 (in the new numbering) hearkens back exactly or approximately to a timeline from 2007's Batman #666, published five and a half years ago and yet another look at that possible (and possibly same) future in Batman #700. Confused? You should be.

We should presume that Morrison's telling the same story he was telling with or without the DCnU reboot, give or take minor glitches (such as, perhaps, Jason Todd being free from prison; Dick Grayson taking back the Nightwing identity; and Bruce using Damian as his Robin, despite an earlier pronouncement to the contrary). Perhaps the other Batman titles are navigating an altogether different course -- the Court of Owls is sufficiently similar to the Black Glove, how could they have coexisted without warring or merging? But Morrison's never had much coordination with the other writers on the bat-titles, and even if Inc is shunted to a tertiary position while Scott Snyder and others take the higher-profile titles, it appears that Morrison's tale continues on, with no sharp delineations from the time it began in Batman #655 over six years ago. To be sure, his plans have evolved along the way, considerably, but Morrison loops the story backwards with flashbacks to the John Mayhew plot, and his rendition of the night Bruce rang a bell to summon Alfred almost as seamlessly as though it had all been planned in advance.

We've known since February 2012's Leviathan Strikes that the villain of this extended story is Talia after Morrison's two previous long maxi-arcs (running in three different titles) both centered around Doctor Hurt.

Once we dispense with the confusion of reboots and how it fits with Snyder, et al's work, the story remains tangled in time. Batman, at the very end of time in Return of Bruce Wayne #6, saw backwards to the vastly earlier time (the mid 21st century, it may be safe to say) when Talia's putative plan played out, a look back first mentioned in The Return when Bruce says he has to protect his allies from "what's coming, what I saw." Apparently, we see that vision (or a slightly more detailed version of it than Batman himself saw) in Inc Vol. 2 #5. It is a vision which Bruce believes will not come to pass (and given its level of horror, we may be sure will not come to pass), which puts into play that the future is malleable: Bruce was at the end of time looking back, but for reasons contained within Morrison's story (and not, likely, within Flashpoint, which was driven by other forces), Bruce believes he can alter it, but not completely. It is also clear that his vision was not complete (in Inc Vol. 1 #1, he calls it "a glimpse of the big picture", and he was despite that glimpse surprised to learn that Talia is Leviathan). He also calls the upcoming struggle with Talia "the fight of my life." And as he says in Vol. 1 #6, "Something big, something bad is coming. And no. Not everyone is going to survive it." So while he believes some portion of the vision can be addressed, he believes that some deadly portion of it cannot.

After extensive foreshadowing that the death of Damian is at stake, we receive a vision of a future in which Damian is Batman, which has featured in three full stories: Batman #666, Batman #700, and Inc Vol. 2 #5. Add in a non-incidental similarity to a reference in Batman #665 when Bruce awakens from a stupor to imagine a grinning Damian telling him that the third Batman is the worst of them all, and remembers a previous dream in which a Batman "sold his soul to the Devil and destroyed Gotham." At the time that served as an elaboration on his first foggy meeting with Michael Lane (the third "Replacement Batman" trained by Doctor Hurt). It also seemed possibly prophetic in Batman and Robin #15, when Doctor Hurt tried to deal for Damian's soul. And it very obviously hearkened to a scenario seen in Batman #666, when Lane and Damian fought a showdown using devilishly-provided longevity. I've previously written up that issue here.

The story in Batman #700 seemed to tell a story (tied in with three others in that issue) of the real future with Damian as Batman, one less haunted by apocalyptic overtones, and no indication that Damian had gained longevity by dealing with the Devil. And yet, it has a striking similarity to Inc Vol. 2 #5 in a baby who is infected with Joker virus. In that telling, Damian obviously does have such powers (rising again after being mowed down by machine gun) and the panel showing him mourning the death of Batman (apparently Bruce, but again see my earlier write-up) indicates that we are back in the #666 timeline, one which was never assured to happen, but which shows what might. Morrison didn't plan this far ahead in 2007, but here we are, and that timeline with the ultimate grim outcome – the total destruction of Gotham suggested back in #665 – coming to play, with Doctor Hurt, as good as the Devil himself, standing by the shoulder of the President, whispering bad confidences to destroy what was once his home city when centuries earlier he was the 1760's Thomas Wayne. This seems to validate that Doctor Hurt remains in the wings for future use, living until he's freed from the coffin near Wayne Manor.

Now, the story in the present takes a strange turn. Damian is cast out from Bruce's shelter, seemingly left to a high risk of death without such protection. We still have a flash forward teaser from Inc Vol. 1 #1 showing Bruce, looking over graves, seeming to quit his Batman identity before being arrested by Commissioner Gordon. With Inc. agents set up around the world, it seems as though the fight of Bruce's life is to begin, and with Damian's death perhaps the tragic end of a story being written so far with the prophetic power of Greek tragedy.

Thursday, July 26, 2012

Close To Home

Two fisherman trawling the bay near a large American city pull their net out of the water and bring up a dead man's body. Examining the nearby water, they see three more bodies. It's later learned that smugglers bringing in workers from China for what is apparently slave labor, and throwing sick men into the water to drown. Grim business and not, probably, a fit story to tell children. But this story did appear once in Detective Comics. In the first issue, in 1937.

A week ago, an American carried guns into the premiere of The Dark Knight Rises and fired bullets into seventy of his fellow citizens, killing a small child and eleven others. He styled himself, it is reported, after the Joker. In many theatres, but not, it is said, that particular one, a trailer for the forthcoming film Gangster Squad showed gunmen shooting from behind a cinema screen into the audience. I was watching this at very nearly the time that the Colorado shootings took place, thinking of what the filmmakers intended: To make audiences think, this violence is coming for you. To break down the barrier between art and life and emphasize, "to you."

This week, the planned sales of Batman, Inc. #3 were put on hold due to a perceived similarity between a scene in the issue, almost certainly the panel which is shown above, and the events in Colorado. There's no denying a similarity. And yet, by the standards of this long-running story, the scene is mild. Even if the gun were fired, it would still be a far cry from the face-eating scenes in 2009's Batman and Robin #5 which coincidentally preceded a face-eating attack in the real world.

Comics have long intended to represent realistic tragedies, so their heroes might face them. Lex Luthor debuted in a story that depicted a fictionalized version of the German-Polish war that soon became World War Two. That war soon became part of countless comic stories, and no one can deny that its accumulated horrors make anything happening lately seem small in comparison.

But there's a disturbing circularity in the last week's events. The shootings in Colorado happened at a Batman film, and bore some similarity to events in previous Batman fiction, and then immediately an image in the comics bore some similarity to the real event. It could have been aligned even more strikingly if, say, Batman #676's "Green Vulture" had debuted this week, with a red-dyed hack of a criminal aiming a gun at a family, shouting "Body count!" and eventually giving himself up easily. There is no shortage of older scenes one might read and wonder if they inspired some details of the real-world tragedy. So many, in fact, that the possible connections get lost in the noise. Gangster Squad didn't invent the idea of a film showing the audience of a film being shot. A berserk gunman may imitate a work of art accidentally or quite on purpose, but the tragedy is simply the act and not the style. Acts like this have been periodic events in American life since one occurred in 1949. Months after America's first spree killing, a similar tragedy unfolded some 60 miles away. Life can imitate art, and it can also imitate life.

Friday, July 20, 2012

The Dark Knight Rises (2012)

Note: This review is structured in two distinct parts. The first part describes the film without revealing details of fact beyond what could be easily deduced from the trailers and other pre-release promotional materials. The second part includes full spoilers in a more complete review.

I. Non-Spoiler Review

Eight years have passed since the final moments of The Dark Knight. Harvey Dent, his crimes hidden by a lie that Batman and Jim Gordon agreed to, has been remembered as a martyr. Some tough anti-crime legislation in his name has allowed the city to put most major crime away. Batman has not been seen since then, and as we all know very well, that absence must end when a new threat arises.

The first of the movie's many acts is stolen by Anne Cathaway as Selina Kyle. She's as confident and glamorous as any Catwoman you've imagined, without ever for a moment trying too hard. She may have been tacked to the plot as an add-on or even merchandising gimmick, but at times the gimmick exceeds the main story in worth.

Though whatever shortcomings the movie may hold, it's not for a lack of inspired performances. Tom Hardy's performance as Bane is brilliant, as is the character himself. One imagines many action casting decisions over the years where a powerfully-built brute is chosen and capable acting is sacrificed. Not here. With a megaphone-like voice emanating from his mask, Bane intimidates you in your seat in three ways at once, for his diabolical evil, his great power, and the quickness of his mind. Neither the script nor Hardy try to make this role bigger than the last movie's Joker, but there is nothing to apologize for in the choice of villain.

Christian Bale gets to play Bruce Wayne / Batman many ways in this one. As a scraggy shut-in, a man of uncertain will to live, and with - in comparison to the earlier films - more (and more comprehensible) time in the bat mask itself.

This is a film with many, many nods to comic books and graphic novels. Fans will challenge one another to see who can catch more sly references, though some of them are exceedingly obvious to anyone who knows anything about Batman. More front and center, fans may ask themselves which previous Batman opus is the most important inspiration for this plot. There is no one right answer.

For me, and I suspect for by far most viewers, this film will languish in comparison to The Dark Knight because it lacks, for the most part, that film's moral complexity. TDK, as I argued in my review, transcended the super hero genre entirely, and served as a workable crime movie of the second, if not the first, rank. The Dark Knight Rises is an action movie. Even in comparison to Batman Begins, this is a movie of the pre-Nolan genre of super hero movie, and no matter how well it carries off that task, it will have people second-guessing the Joker's line from TDK: "You've changed things. There's no going back." This is an epic story, in more ways than one. But all of the things that made Nolan's Batman remarkable were put back on the shelf. One wonders how, having earned the plaudits he did for the previous movies, he could be so willing to go back. This film might have served as a good third movie in the previous Batman series. If it had come then, no one would have complained. Coming after TDK, the appeal will have to be in just how well it does as an epic.

II. Spoiler Review. Very big spoilers follow. After a few blank lines, they begin. You were warned.






For eight years, Bruce Wayne has been shut in his home, reclusive and so beaten up from his days as Batman (perhaps just that last fall that killed Harvey Dent) that he cannot walk easily. Gotham has moved on and it thinks it's doing fine. It seems fine, but that's because nobody knows that Bane is coming. Like a freight train he's coming, and in a sharp distinction from the comics' Knightfall, he's not after Batman. He's simply after Gotham. Like R'as al-Ghul and the Joker before him, destruction is his goal, not profits. In fact, we will learn early on, he like Bruce was trained by the League of Shadows. As we learn while his plan is underway, he in fact wants to pick up precisely where R'as left off. Destroying Gotham so it may begin a renewal is his only aim. He is perfectly willing to overcome Batman when that proves to be necessary, but that is an afterthought.

In the first of many events shocking in terms of the Batman comics' mythology, Selina steals Martha Wayne's very pearl necklace right in front of Bruce's eyes. She's very skilled, morally gray (a thief, but not a destroyer), and she helps wake Bruce from his long sleep. In fact, she's working for Bane, although she doesn't appreciate the evil she's serving.

Bruce somehow manages, after years of hobbling on a cane, to rush out to challenge Bane's gang and end up escaping the police. The speed of his recovery is inexplicable; was he insufficiently motived to walk normally during the last eight years? The dialogue of the police officers is drawn right from Batman's reappearance in The Dark Knight Returns; moments later, when Selina disappears on him, he says, "So that's how that feels," a line Bruce says about Superman in Kingdom Come. So we see the homages are in full force. Even more so when we find out that Bane's first caper served simply to bankrupt Bruce.

As Bane's evil plan moves forward, Jim Gordon works through a Nolan favorite, Joseph Gordon-Levitt's Detective Blake, who gets a curious amount of screentime. Bruce gets in bed with another Nolan regular, Marion Cotillard as Miranda Tate. Both of these serve very well all film long before escalating dramatically in importance during the final minutes.

Bane of course breaks the poorly-conditioned Bruce in a fight which is no fight at all. He keeps Bruce in custody, in a death trap that's almost impossible to escape from, which of course means that he escapes from it. The mood here has a touch of Batman, R.I.P. to it in that Bane wants Bruce to suffer psychologically, broken, and watch the harm he does to Gotham. The harm he does is brilliantly effective. Using a nuclear weapon to hold the whole city hostage indefinitely, Bane creates a city cut off from the United States, clearly a nod to No Man's Land, right down to the chalk bat-symbols written on walls.

Of course, Bruce gets back into shape, escapes his prison, and goes back to Gotham to stop Bane. It is in carrying out these obligatory steps where the film is by far the weakest. It is so formulaic that this all must happen, we wonder where the brilliance of The Dark Knight went. It is obligatory, and takes a long time in unfolding. The scenes of Bane's destructive three-month dictatorship over Gotham (with Jonathan Crane returning as a judge in a kangaroo court) come as a refreshing break between scenes of Bruce getting in shape which may as well have had the Rocky theme playing over them.

Bruce does return, and he does get the best of Bane in a fight. As soon as he threatens to kill Bane, the movie becomes something else entirely. Suddenly, Miranda (note, the wizard's daughter from Shakespeare's The Tempest) drives a dagger into Batman's ribs, and the comic fan may recall that in Bane's second attack on Gotham, he was allied with Talia. So here, where their backstories are intertwined in a bit of explication with scenes of a child whom we thought was Bane in flashback was actually Talia. Her knife attack seems fatal, and given the movie's promotional claims that the legend ends, we wonder if it might be. In fact, being bled by a woman is Robin Hood's death, and this simple act resonates with a vast web of comics (and meta-comics) lore: Alan Moore cited Robin Hood as the sort of legend that Batman ought to be, and Neil Gaiman gave Batman such a death (among several) in Whatever Happened To The Caped Crusader? That story comes back in yet another reference as Batman escapes the injury to lash the nuclear bomb to his flying "Bat" vehicle and soars off to sea, getting far enough that the detonation spares the city, but takes him with it, very like a sacrificial death Batman chooses in Gaiman's story. By this time, Bane and Talia are dead. The city is saved.

More twists await. While Bruce (whose secret was at last made known to Gordon) has gone, we see that Detective Blake, himself an orphan, is preparing to play a very Batman-like role which will begin in the near future. The kicker: We learn that his real name is Robin. And for the twist of twists, a la The Dark Knight Returns, we see a final sighting, real unless it's Alfred's wishful thinking, of Bruce and Selina romancing one another in Florence.

This is a movie full of wonderful elements, but for the reasons I've already noted, it sags terribly in the middle act, and aspires to something so much less than it could have been. This will not be remembered as the best movie of the series - more likely the worst, but the worst of a very good trio. And though it endures poorly, it ends well. And isn't that what a super hero story is supposed to do?