Drew: We read a lot of comics at Retcon Punch. One of the best thing about reading so many comics (besides, you know, reading so many comics) is that when we do pick up the odd issue of a title we’re not reading — usually for a crossover event — we still kind of know what’s going on. We may not get every reference to what has happened before, but because we’ve seen glimpses of, say, the Red Lanterns in Green Lantern: New Guardians, we kind of know what’s going on with them when we pick up Red Lanterns 13. This works well enough for stories set in Gotham or Oa, where our coverage of related titles is relatively robust, but it breaks down if crossovers are happening in our blind spots. The Superman and Young Justice groups happen to both be blind-spots for me, which makes jumping into a title like Superboy at issue 14 a particularly disorienting experience. Continue reading →
Today, Drew and (special guest writer) Nick Idell are discussing Superboy 0, originally released September 12, 2012. Superboy 0 is part of the line-wide Zero Month.
Drew: I’ve never been a big fan of origin stories. They tend to be overly plotty, displacing more telling character moments in favor of unwieldy exposition. In short, I see them as a necessary evil we often need to get out of the way before the real story can begin. It’s unfortunate, then, that I live in an age where superhero origin stories are so ubiquitous, every third Spider-Man movie needs to revisit that well. We’ve fetishized origins, pushing them to ever-increasing complexity, straining the very limits of pre-title copy that attempts to explain it all. “The Supergirl and Robin of Earth-2 are trapped on Earth-1” sounds relatively snappy, but likely requires an explanation of what the fuck Earth-2 is, and how exactly they get trapped in the first place. These baroque origins relay details, which requires more space to properly explore, resulting even more bloated exposition. “Scientists clone Superman” is such a clean, self-contained idea, but Superboy 0 finds writer Tom DeFalco ladling on the details, buddying the message into an inexplicable hash.