the_wake_1_cover_2013Editor’s Note: I got to tell you, I give this whole thing a spoiler-factor of about nine point five.

James Cameron’s 1989 movie The Abyss is one of my favorite movies (and if you could quit fucking around with deep sea diving and get a Blu-Ray version mastered, Jim, I’d sure appreciate it). It’s got a mix of claustrophobia, environmental danger, interpersonal conflict and threatening weird alien shit that, even a quarter-century later, it’s just hard to find anywhere else. I saw it in its initial theatrical release, I’ve owned it on VHS and DVD, and will forever harbor an inappropriate and filthy crush on Mary Elizabeth Mastrantonio because of it, despite the fact that she’s not still 29 any more than I’m still 18.

If I had to hazard a Russian Roulette interrogation guess, I’d bet that writer Scott Snyder is a big fan of The Abyss, too. Because the first issue of The Wake, the Vertigo miniseries he took a break from American Vampire to produce, is rocking a lot of the elements of that movie. We’ve got a female ocean-related scientist who’s been called back to her area of expertise. She’s trapped on an undersea oil drilling platform with a male former co-worker with whom she has a contentious relationship. The military is throwing their hand in. And there are aliens there: aliens that are threatening to use our oceans to wipe us out… only Snyder implies that, without Ed Harris there to suck pink goo at the bottom of the ocean and use his inappropriate and filthy crush on Mary Elizabeth Mastrantonio to whimper for our lives, we’re kinda fucked no matter what happens in the remaining nine issues of this ten-issue miniseries.

So make no mistake: you’re gonna see things that you have seen before in this issue. But is it worth checking out even if you’ve spent hundreds of hours watching The Abyss (Or perhaps thousands of hours, if you count the time spent freeze-framing on Mary Elizabeth Mastrantonio’s boobs)?

the_green_team_1_cover_2013-322861729The Green Team is one of those comic book superhero teams that is destined to become part of comic book history. By which I mean, in about 20 years, some hotshot, big idea comics writer like Neil Gaiman was in the 90s will ressurrect them and try to treat them seriously as an archetype of a particular type of comic, written by middle-aged adults about adolescents, trying to capture the zeitgeist of a particular period of history. And that purely theoretical comic book writer of 2028 or 2033 will be heralded as a genius for finding a way to take The Green Team seriously, the way that Gaiman was when he wrote Prez into Sandman #54 20 years ago.

But that will happen in 15 or 20 years. Today, The Green Team feels very much the way Prez did back in 1973 (before my time, but I remember the series getting some play in DC Comics house reprint ads in the mid, late 70s, maybe as a giant sized gallery reprint, and even at that age I thought the idea was ridiculous): an effort by someone too old to be part of youth culture, trying like mad to grab bits and pieces that they either do understand or that they’ve read about, to make a book to appeal to them… and ultimately feeling like its trying too hard and mising the mark.

And maybe that’s my problem; after all, I am old enough to remember Prez, which means that my only relationship to youth culture is related to the things I would do to Lindsey Lohan if I had a double-strength condom and an iron-clad fake name to give her. But the trials and travails of a bunch of rich kids with Twitter trying to prove themselves to daddies who want them to grow up to become bougouisie douchbags like themselves (mission accomplished!) somehow doesn’t land home with me.

Plus: we’ve already got an Iron Man, guys.

bounce_1_cover_2013-322861729When left to his own devices on creator-owned material, writer Joe Casey produces comics that are, in the language of critics, some pretty fucked-up shit.

Be it Automatic Kafka or Butcher Baker: The Righteous Maker,  Casey seems to like to traffic in higher-concept superhero stories, loaded with sex, drugs, psychedelia and other stuff that you won’t normally find in a standard superhero story. Like robots with existential malaise using drugs to find meaning in an empty life. Or a dude in a truck killing all comers and fucking anything that walks, moves or crawls. And no matter what, at some point you will find yourself reading and muttering, “Just what in the hell is goning on here?”

Welcome to The Bounce. A comic story that, in 20 short story pages, features not only superhero action, but copious drug use, cop murder, interdimensional travel, and government funded quasi-religious partical experimentation to fracture the nature of reality.

So as is often true to form on a Casey book, I really have no fucking idea what is going on. But that doesn’t mean there isn’t enough good stuff here to stop me from wanting to find out.

the_deep_sea_one_shot_1_cover_20131784141047If you are a fan of Lovecraftian fiction, The Deep Sea one-shot, written by Jimmy Palmiotti and Justin Gray with art by Tony Akins, will utterly fucking infuriate you. But not necessarily for the reasons you might think.

If you are, in fact, a fan of Lovecraft, you know the general basic tropes of the classics: a group of explorers go someplace unseen by human eyes. They find a weird city. They do something that awakens a slumbering elder god of some kind – Cthuhlu is always a favorite – whose visage and presence in the world is so utterly alien and wrong that it drives men mad to simply witness it. And then there is the implication that this awakening means the probable end of the human race. If you take that general summary and chuck in the odd racist comment, and you might as well be living in H. P. Lovecraft’s Medulla Oblongata.

Well, The Deep Sea hits all of those elements, save one. And it is the one that is the most common of those elements, and the one that makes the concluding implication of humanity’s doom a satisfying ending. And weirdly, it is the elimination of that element that makes The Deep Sea fresh and interesting despite following almost all the tropes of Lovecraftian fiction, and which will make the end of this comic book irritating to you.

Because you’re gonna want more.

green_lantern_20_cover_20131784141047If you’re anything like me, when you see Green Lantern #20, and its thickness, squared binding and eight dollar price tag, you will think of The Amazing Spider-Man #700 from just five months ago – an issue that was padded with secondary stories to pad out it’s length. So you might think that Green Lantern #20 would do the same to fill its 86 pages and get a little upset that you’re dropping eight clams on what would seem to inevitably be a big chunk of filler.

You would be wrong. Sure, there is filler here – I’m not sure I needed nine pages of messages of congratulations to writer Geoff Johns (although DC Entertainment President Diane Nelson’s message makes me believe she might be the brains behind the Horse_EBooks Twitter account) – but on the whole, this is a one-story comic book. So you’re damn sure getting your money’s worth with this comic book.

And it is a big story. This is Johns’s final issue driving the Green Lantern franchise, and he treats it like the series finale of a long-running television show, even though the Green Lantern books will continue, as the five full-page ads in this issue for those books attests. And as a series finale-feeling story, it brings back all the old favorite characters for a final bow, it throws all the old fan favorite moments at the wall, and as is befitting a sci-fi action story, it blows stuff up real good.

But this is a space opera, not hard science fiction. So while Johns puts all the pieces into place to make a slam-bang action-packed story, there are a bunch of elements required to push that story forward that are firmly based in the scientific principle, as defined within the Green Lantern universe,  of the Theorem of Shut Up That’s Why. So some of the points between A and Z require a lot of taking on faith to avoid nitpicking… but if you can, you’ll have yourself a damn fun read that brings all your favorites up to bat one last time, and even tells you where some of these characters would end up.

pathfinder_7_cover-155712338Dear Dynamite Comics: please reconsider the font you use to number issues. With God as my witness, I thought Pathfinder #7 was actually a #1. It’s the only reason I bought it.

Because normally I would never buy a sword and sorcery book, at least not sight unseen. I have a mental block when it comes to genre stories about quests and swords and paladins and magic users. You can give me a story about a hero in spandex attacking a giant monster, the same story with a hero with a laser pistol and a giant robot, and the same story with a dude with a sword and a dragon, and I will pick stories one and two almost every time. I’m the same when it comes to role playing games: Shadowrun and Call of Cthuhlu, yes; Dungeons & Dragons, no.

But I review comics, so I bought what I thought was a first issue, because frankly, I need to file copy almost every day, and hey: you never know. But while I was disappointed when I saw that it was actually a seventh issue, my spirits were lifted when I saw it was written by Jim Zub, the writer of Skullkickers, a sword-based adventure story that is a favorite outlier in my eyes due to the presence of a gun, and metric buttloads of solid humor.

Pathfinder #7, however, is no Skullkickers. It is a far more conventional D&D-style story, by which I mean it is very much like a game of Dungeons & Dragons. Zub gives us the well-balanced party of adventurers, cast as if by a demanding DM, with modern-style dialogue and some of the classic obstacles and antagonists of that game.

It is also a well-executed entry point for new readers, introducing a new adventure for the party, demonstrating internal conflict, and teasing one of the great battles one can find in a game of D&D.

You know, if you like that sort of thing.

age_of_ultron_8_cover_20131154508910We can’t bust heads like we used to, but we have our ways. One trick is to tell them stories that don’t go anywhere. Like the time I took the ferry to Shelbyville. I needed a new heel for my shoe so I decided to go to Morganville, which is what they called Shelbyville in those days. So I tied an onion to my belt, which was the style at the time. Now to take the ferry cost a nickel, and in those days, nickels had pictures of bumblebees on them. Give me five bees for a quarter you’d say. Now where were we? Oh yeah: the important thing was that I had an onion on my belt, which was the style at the time. They didn’t have white onions because of the war. The only thing you could get was those big yellow ones.

-Grandpa Simpson

What, exactly, is Age of Ultron about? This is a serious question.

We started out with a pretty straightforward end-of-the-world story with a bunch of killer robots that came literally out of nowhere and fucked up New York City. Then it was about infighting between superheroes, desperate last chances, and time travel. Okay, great. Now it’s about the Butterfly Effect, divergent timelines, and an alternate version of Marvel’s history where Hank Pym never existed, The Avengers broke up, and the world is under seige by Morgana Le Fey (“I toldja that Le Feys would be the end of America!” “Shut up, Dad!”). We’ve still got two issues left in Age of Ultron not counting crossover issues, which means we still have plenty of time for this series to tack in yet another direction, perhaps one about Friendship being Magic.

I’m not saying that Age of Ultron isn’t interesting; I was a rabid reader of What If? back when I was a kid, so I am a sucker for alternate versions of Marvel history, but I’m just not getting what writer Brian Michael Bendis is going for here. We’ve got a robot apocalypse that came out of left field, and that isn’t being addressed in other titles except in one-off “AU” issues that drop the character into the Ultron scenario for twenty pages before returning to the status quo in the next issue. And now, in issue 8, we are completely out of that apocalypse into an entirely different apocalypse that occurs when Hank Pym doesn’t exist – again, while none of this seems to be affecting the Marvel Universe as a whole. And all the while, we’ve got guys like Marvel Editor Tom Brevoort swearing that what happens in this book will have an effect on the greater 616, when it doesn’t seem to be having any effect right fucking now.

So what’s the endgame here? Is it to irrevokably change the nature of the Marvel Universe based on an apocalyptic event that led to some ill-advised time travel and cold-blooded murder? Is it to accentuate the importance of Ant Man to the Marvel Universe in time for the Edgar Wright movie in a couple of years? Is it to placate Bendis’s urge to apparently write the Marvel version of what might have happened if Arnold had blown Eddie Furlong out of his fucking socks the way we all wanted him to after two hours of bad acting in Terminator 2?

These are the questions I had when I finished Age of Ultron #8, a comic book that is cool if you like alternate versions of Marvel history, but which is yet another chapter of a story that seems to be bouncing from bad day to bad day without actually going anywhere in particular yet, and which, at this point in the story, just doesn’t feel like it matters.

deathstroke_20_cover_2013-153518301Editor’s Note: And one last look at last week’s comics before the comic stores open late today… and it contains spoilers. But they are spoilers on a book that has been cancelled and lives no more. So do you really give a fuck? Thought not.

“So the final issue of Deathstroke was in this week’s take. You gonna review it?” I said.

“Fuck that,” my co-Editor Amanda said, “As far as I’m concerned, that book’s been over since Rob Leifeld took over from Kyle Higgins last year. DC editorial took a perfectly good book about a professional dealing with the perils of entering middle age and turned it into a book about some badly-proportioned, footless steroid head beating on space douchebags.”

“But Justin Jordan’s been writing the book for the past few months. Do you think it’s improved at all since then?”

“I haven’t been reading it.”

“Why not? Jordan writes Luther Strode, and you like that.”

“Yeah, but so what? It’s damaged goods. Taking over Deathstroke after Liefeld had his grubby mitts all over it is like watching a buddy get married to a whore. He might be totally in love and committed to making it work, but here ain’t a force on Earth that can make people look at her and not picture when she had three dicks in her mouth. Let Deathstroke go under and lie fallow for a while. I’ll try it again when it feels a little less… dirty. You review the last issue.”

Okay I will. Despite not having kept up on Deathstroke since Higgins left the book any more than Amanda did. Which means that I have no idea what the hell led into the events of this issue, which includes all the Usual Suspects you’d expect from a big Deathstroke story. We’ve got Terra, Rose (Slade’s daughter who became Ravager before the New 52), Grant (Slade’s son who became Ravager back in the 80s – c’mon, at least try to keep up), Jericho (Slade’s other son, who was a good guy in the 80s before becoming a bad guy in… ah, fuck it) and, well, Majestic (for some reason), locked in a epic battle to the death that requires some ugly choices, brutal methods, and one deus ex machina on Slade’s part.

Which is fine, but what matters is: is it any good? And more importantly: does it work as a final story? You know, with “final” in subtextual quotes, since ain’t no one really gonna kill a character that appears on The CW’s Arrow?

avengers_11_cover_2013 Avengers #11 has all the components of an interesting, short-term change in direction to keep the book from getting bogged down in giant international and even cosmic events. A one-and-done that still services the longer story Hickman has been spinning out, this issue has several members of the team go undercover in an overseas resort to find out what AIM is up to and discovering that they are getting ready to auction off a superpowered weapon in a particular form. It allows the characters to show some humor, demonstrate how they play off each other when they’re out of costume, and try to deal with an independent nation-state that has diplomatic immunity when the team is not in a position to just use their powers and let loose.

So Avengers #11 really has all the hallmarks of a cool, quirky, one-of-a-kind issue, and that is good after several issues of giant stakes and a lot of bombast. However, it is also bad, because Avengers #11 also bears the hallmarks of Justice League International #16 from August, 1988. Where members of the team go undercover in an overseas resort to find out what Bialya is up to and discovering that they are getting ready to auction off a superpowered weapon in a particular form. And they show humor while demonstrating how they play off each other out of costume. And they try to deal with an independent nation-state. That has diplomatic immunity.

Seriously: there are about a half-dozen obvious parallels between Avengers #11 and Justice League International #16 and #17. And hey: these things happen. There are no new ideas under the sun, and I take it as a given that any similarities between these two books is either a matter of parallel thinking or simple homage, because while I think Hickman’s writing is often clinical and bloodless, I have never seen it be anything but relentlessly original. And I will therefore try to review Avengers #11 on its own merits as much as I can… but that will honestly only go so far. Because the fact of the matter is that my entire experience of reading this book was colored by that feeling of familiarity, to the point where the first thing I did after finishing it was to dig out my Justice League International trades to find the issue to see if my instincts were right (if you’re curious, the issue is in JLI volume three).

So yeah: I’ll try to review Avengers #11 on its own, but it’s gonna be like reminiscing about a high school misadventure with an old buddy over beers: it’s fun to revisit, but it’s not like you can forget living it the first time, when you were young.

batman_20_cover_2013Dear creators working in DC’s Batman office: there is a product available on the Internet called Skype. It is free. And it allows you create a virtual conference room, where you can invite any number of people to join, and then, you know, talk to each other.

I say this because there is obviously no communication happening about how Bruce Wayne is handling the death of his son. The writer of that death, Grant Morrison, has Bruce sucking down Man-Bat serum and going on a revenge rampage over in Batman Incorporated. Peter Tomasi has Batman scouring the world looking for a way to bring Damian back to life, including the psychological torture of the last Robin to get killed on his watch this month, and making an attack on fucking Frankenstein for answers last month.

And Scott Snyder, the writer of the main Batman title? Well, as a guy who has to turn in a comic book during this whole, sudden, “Damian’s-Dead” shitstorm, he has Batman affected by the event in the margins, while making the meat of the story a decent, if workmanlike, two-and-done featuring an antagonist no one really cares about, and a big Easter Egg in this week’s Batman #20 to delight the rubes (I was certainly delighted). However, as a guy who has reached A-List status at DC in the past year and a half, with arguably as much pull as Morrison, Snyder has clearly said, “Um, yeah: I’ll give you a couple issues mentioning this death, but this is Grant’s problem. I think I’m gonna scrap my Riddler plans and do a year-long story set in the past while you guys deal with the fallout from the whims of that crazy Scottish fucker.”

So if it seems every Batman writer has picked a different stage of grief to stick Bruce Wayne into over the death of his son, Snyder has clearly chosen “Acceptance.” Which means, at the very least, that it is the less histrionic of the two Batman titles on the stands this week. But the question is: is that enough to make it any good?