Geroge R.R. Martin - A Storm of Swords (Part I)

I wistfully recall the halcyon days of my youth when the prospect of reading a book a week was not only achievable, but usually surpassed during vacations, holidays, and quiet weeks when the office was slow.

Not so anymore. I'm currently cruising at the #35 mark, and if I want to hit 52 books this year it's gonna have to come at the cost of reading monstrous tomes like George R.R. Martin's A Storm of Swords, the third in his projected septilogy (yup, it's a word) of fantasy epics under the banner A Song of Ice and Fire. It's also the lengthiest of the lot, clocking in at 1,176 pages, which might explain why this review is going to come in two parts: I'm up to page 534 as of this morning, and plan on having it finished in time for next Monday's post. So be aware the below constitutes my impressions based on only half the book.

At the end of previous book A Clash of Kings, everyone's in a pretty rough spot. The Lannisters, under petulant child king Joffrey, still sit atop the Iron Throne, having demolished their competition in a vicious water battle. All of our favorite characters are either in exile (Bran), mortally wounded (Tyrion) or undercover with one enemy (Jon) or another (Ayra). It was a dark and fantastic middle chapter, an EMPIRE STRIKES BACK looking toward the promise of a RETURN OF THE JEDI to wrap things up in a delightful Ewok celebration.

(For those so inclined, please feel to exchange the STAR WARS trilogy for INDIANA JONES or LOTR...we're all friends here)

But ah! Not so fast! Like the bolt of lightning that struck Lucas who then proceeded to piece by piece dismantle his great work by explaining everything, Martin realized that three books weren't going to cover the story he wanted to tell, so instead of the rousing conclusion you would expect, A Storm of Swords comes in and reminds you that the good guys don't always spring right back, ready to fight for another day (quick GM note: unlike Lucas, though, it doesn't suck). In fact, things at the mid-point of the novel seem just as dismal as they ever did. The nameless threat from beyond the Wall of the North continues to get closer and closer, decimating the Black, the soldiers who guard the Wall. Young Robb Stark, despite winning every battle he is in, seems to be losing the war due to politics and the desires of a young heart, as he breaks a potential alliance by marrying someone else. Jon Snow, the bastard son of the late Eddard Stark and ostensibly the "hero" of the books is now aligned with the Wildings of the North, having gone undercover after killing his mentor. Tyrion, the shining character of the series, the Imp whose machinations and manipulations are an homage to the classic Shakespearean villains, is battered and beaten, forced to act as the King's money man forced to marry Sansa Stark in a move that has got everyone in an uproar.

And in the background slowly comes Daenerys, keeper of dragons and an army of Unsullied, who vows that the Iron Thrones is her by right.

If you're confused by the number of players and continuous switching of allegiances, well I think that's exactly where Martin wants you to be. The books that make up A Song of Ice and Fire revel equally in the maneuverings of the nobility and the epic bloody battles. This is historical fantasy at its most ambitious, and things can admittedly get a little confusing. If I have a complaint to the book at all, it's that halfway in I don't see a clear objective to the novel - it just feels like a long interlude between novels, whereas both A Game of Thrones and A Clash of Kings seemed to have a solid through-line amidst the myriad of tales being told.

But that's nothing I hold against A Storm of Swords, especially since there's another 500 pages to go. What I've read so far has been filled with the moments that have made the other book such fun, and I'm sure it'll end the same way.

NEXT WEEK: THE CONCLUSION!