Showing posts with label Martin. Show all posts
Showing posts with label Martin. Show all posts

Saturday, February 27, 2016

March

A book so well-written, it causes envy and jealousy within me. How could I possibly expect to write as well as this? If all published works had to be this well-written, few authors would stand a chance.

I realized while reading this that most of Geraldine Brooks's sentences were detail-in-action. (And certainly not the other way around, which mars many works of good writers.) Her sentences are doing one of two things: they're either description, or they are action. Too much of either one would be boring, even if it's well-written and boring. Therefore most of her sentences are a combination of the two, detail-in-action.

In this, she takes a mostly-absent character from Alcott's Little Women (which, embarrassingly, I have never read, though I have it around here somewhere) and fills in his gaps. Where did March go when he enlisted? What did he do? Well, he did these things.

This book is a masterpiece (and therefore worthy of its Pulitzer) of its time, and of its rendition of the people of its time. Yet like all good works, it makes the reader understand that the people of its time are also the people of this time, and vice-versa. Here you have racism among the Northerners and the Southerners, and neither is treated like a stereotype. And so it is today. March comes home a bitter soldier who has seen and done too much, and who has brought with him a PTSD and a Blakian Experience that will never be undone. And so it is with returning soldiers today.

This is a book of all times, of all wars, of all soldiers and of all victims. Wars in Iraq, Syria, and anywhere else of any time will be similar to Brooks's Civil War rendition here.

The sudden POV shift jarred a little, and the shift back to March disoriented a little (I had to go back  to be sure that it was his turn again), but the reader will see the necessity of the shifts. Brooks could have superficially prepared the reader, perhaps by placing character names at the beginning of each chapter--a la George R. R. Martin in his Song of Ice and Fire books--but such is not her way. You'll be able to bear it and move on.

She does an interesting thing with Grace, who seems to turn up a little bit more coincidentally than maybe she should--but the reader will see the necessity for this as well. Brooks gets away with these two things that would have torpedoed lesser writers (such as myself).

This was a quick, intelligent and gripping read that sounds all too true, and will perhaps leave you a little emotional throughout, and certainly at its end. But you owe it to yourself to read it, if not for the great writing and experience, then perhaps to better understand a returning soldier you happen to know today.

Saturday, February 14, 2015

A Dance with Dragons by George R.R. Martin -- Book Review


Photo--Paperback copy, and the one I read, from its Wikipedia page.


A very good book, but not as good as its predecessors.  This has been much remarked upon, so I won't belabor what's already been said...

Except to say that Martin has to try something different, and focus on different characters, doesn't he?  Readers forget that the writers themselves also have to be entertained (as U2 reminded its fans when the band made techno-pop stuff the masses hated); I would imagine that after approximately 4,000 pages (which probably means up to 8K to 12K pages, edited and often deleted), Martin felt that, to stay sharp, he would have to focus on different characters--many of them not the major ones--and also do little things, like refer to characters by their new status, or tongue-in-cheek nicknames, in the chapter headings.  This doesn't always work, and is at times confusing, but you've made it this far, through 5K or so pages, so you'll get it before long.  He did this a bit in the previous book, perhaps less successfully and more irritatingly, but you got through that, right?  So will you here.

And you'll like this one more than the last, I think.  It really picks up in the second half--maybe the last third, if you're picky--and it goes by in a rush after that.  Like Stephen King and maybe a few others, Martin's writing is compulsively readable, even when its not at its best, so you'll find yourself sailing along, even if you're not completely thrilled with what's going on.  This is a must, if one is to read about seven thousand pages before it's all over, so it's a good thing he's able to do this.

By the end, you'll be far further along than the Game of Thrones series on HBO, so you'll have to be quiet about what happened.  (Notice the lack of a summary of any kind here.)  There won't be another book in 2015, or so said Martin recently in an interview, so we'll have to make do with the show for now.  I expect the show to drag out quite a bit of what happens here, unless they want to finish with the show before Martin finishes with the books.  (He'll share his outlines and notes of the last two books with the show's creators, I would assume.)  If so, this would be a rare event.  Normally the book(s) end first for the movies and shows (a la Harry Potter) to drum up even more interest in the movie and successive books.  That may not be the case here, as J.K. Rowling was a quicker writer than is Martin.  But who knows?

Tuesday, January 20, 2015

A Feast for Crows by George R. R. Martin



Photo: The book's hardcover edition, from its Wikipedia page.

A gripping continuation of the saga, and--if possible--a bit more  gritty and ghoulish than its predecessors.  (The title refers to the incredible number of mutilated and rotting bodies laying and hanging and floating all over the land.)  But it still envelops you in its web of world-building.
 
Martin continues to embed us in this world, and does so here by focusing more on some of the more minor characters of the other books, as well as a couple of new ones, while also furthering the paths of Cersei, Jaime, Sam, Sansa and Arya.  Brienne of Tarth gets a larger stage than ever before, as does Sandor Clegane, who she killed in the show, but not yet (if at all) in the books.  He reappears with a woman (maybe) under a grey cloak, who may, or may not, be a character somehow brought back from the dead.  You'll have to decide, but I have my doubts--though, in truth, I don't really know what I'm doubting.

Sansa and Arya hide under assumed names--names that they take to heart a bit too much for me at first, to the extent that the chapters are entitled with their adopted names, to the amazement and confusion of all.  The girls even call themselves these fake names in their thoughts, which got to be a little creepy.  You get used to it, but they became just a smidge too Sybil for me.  And it was a little jarring, and a tiny bit confusing, what with all the names already for the reader to deal with.  But I stayed the course.

Gone from the narrative are Tyrien, Jon Snow, and Stannis.  They're around, just not in the book.  The same cannot be said for the Onion Knight, Stannis's Hand (or, for that matter, for Jaime's hand; sorry), who apparently gets killed off-, off-, off-stage.  Just a quick quip from one of the characters--easy to miss in these 900+ pages.  But characters have the tendency to not die, and not just like Beric Dondarrion, who has died, and not, six times now.  But characters also tend to just re-appear, not dead, though other characters, and sometimes the reader, thought they were.  So, again, I have my doubts.

Speaking of Beric Dondarrion, I had to look up his last name to finish one of the sentences above.  I don't mind telling you, there's a large city of names being thrown at you by now in this series, so if you find yourself pausing for a moment after reading about a character, and thinking, "Wait.  Who the hell is this again?", don't feel bad.  What can you expect with literally dozens of names, and two newly fake names, and a handful of new characters, all being thrown at you at the same time?  Don't stop reading because you forgot, for example, Beric's last name.  Keep with it.

The reader will be rewarded at the end, if the reader, like me, was wondering how one of the characters could get away with so much for so long.  Maybe the tide has turned on that.  Speaking of the tides, there's a new group of people to deal with who pray to the god of the sea, a religion founded on the baptismal drowning of its believers.  Sort of.  Anyway, they need a new king, and they get one, kind of.  This takes a long time to happen, and is a bit interesting, and a bit not, at the same time.  This is perhaps my only complaint here.

But the 900+ pages whisked by--no small feat, that.  The book is good enough to throw all this at you, which would be annoying from most books and book series, but is not here.  It has now become addicting, to the extent that I find myself occasionally thinking and speaking like its characters.  I don't look forward to seeing something now, for example.  Now I yearn to set my eyes upon it.  It's become such an addiction that I was dismayed to find that I do not have the fifth in the series, A Dance with Dragons.  I'll have to pick it up soon, once the temps warm up enough outside so that I don't have to worry about my breathe immediately freezing and falling like dead weight upon my foot.  (It's one degree out right now, with a -20 wind chill.  It's so cold I'm losing a fortune in heating, but I'm so glad to be comfy and warm that I don't care.)

Perfect weather for this book, as it's often cold and wet and miserable for all its characters, internally and externally.  Makes me want to drink some warm or hot wine, or maybe some dreamwine, and build a fire until the wind and cold subside.  See?  You get engrossed in that world.  Or, maybe I've read too much and not slept enough.

Tuesday, January 13, 2015

Game of Thrones -- A Storm of Swords by George R. R. Martin



Photo: U.S. hardcover, from the book's Wikipedia page

Unbelievably entertaining and engrossing read, which--as I pointed out in my review of its predecessor--is really saying something, since I knew every major thing that was going to happen.  That in no way took away from the read, and may even have enhanced it.

As is necessary for high fantasy, and perhaps fantasy in general, the writing is so totally enveloping that it is like you're in that world.  World-building has to be perfect in books like this, but I'll bet that it's rarely this much so.  The Lord of the Rings books were less world-built than are these; I don't mean that as a negative towards Tolkien, as he paved the road and showed the way.  But Martin doesn't focus on over-description of grasses and trees.  Instead his writing is completely focused on completeness in every way: how everything looks, smells, etc., just as you're taught in writing classes, though not to this extent.  He doesn't just description from all of the senses: he focuses more on the sight and the sound, and less on the others.  And he does not describe to the detriment of the action, as Tolkien did.

Some scenes are better in the show, but to describe how and why would be to partly ruin the experience of reading the book, or watching the show.  So just a quick mention of what things are different, without mentioning how they're different:

--though the end of this book brings you up-to-date with this past season's end, the book ends with something not yet seen on the show.

--Brienne of Tarth does not do in the Hound.  I prefer the book's way.  It struck me as unrealistic that Brienne would run across Arya and the Hound, way out in the middle of nowhere, on an outcropping.

--Ygritte does not get killed by a little boy shooting an arrow.  I prefer the show's way, though I admit the book's way is much more realistic.  Martin does not go for the melodrama.

--Something major happens to Jon Snow on the Wall in the book and not in the show.  At least not yet.

--Littlefinger's dialogue before his push is much better in the show.  Essentially the same in both, but the show just nails it so much better.

--(Martin is better than the show's writers with the overall dialogue, and the everyday expressions, etc.  But at a climactic moment, the show's writers really nail it.  And this isn't because I saw it before I read it.  Trust me.)

--The book emphasizes how many guys Cersei sleeps with.  It's clearly a weapon for her.  The show does not...well, show this.

--The book makes it very clear who killed Joffrey.  Good to know I got it right from the show.  We know from the show that Littlefinger was behind the whole thing (which I wouldn't have figured out), but who exactly put the poison in the cup?  Oops...You did know it was the wine and not the cake, right?

--The book breaks the battle of the Wall into two or three distinct parts, over a few days.  The show gives it to us all at once, all in one episode.  I like the show's take better.

--The book does not show the giant's attack in the tunnel like the show does.  It was a good call of the show's to do so.

And there's more, but you get the idea.  I realized while reading that the show made some excellent decisions about what to emphasize (the scene between Tywin and Tyrien was better in the show, too, as is Tyrien's dialogue at that climactic moment) and what not to.  It is a rare thing that a show is better than its material, but it's a close call here.

But that's not why you should read the book.  The writing does something that the show, no matter how hard (or successfully) it tries, cannot duplicate: it envelops you into its world-building so completely that even a visual medium cannot match.

P.S.--This was the last book I read in 2014.  It was my 25th, for a total of 10,283 pages.  About 27% of those pages were just the three Game of Thrones books I read.

Tuesday, December 23, 2014

I Return, and with A Storm of Swords

Yes, it's been a long time since my last entry.  I never go a month between blogs, but it's been a trying time.  I won't bore you or whine about the details, except to say that I almost lost a loved one--but Jackson the Greyhound is doing much better and is still very enthusiastically with us.  But a week-plus worth of vet bills isn't cheap, and the predictable had to happen, made even worse by the time of year.  Of course, all the vet bills had to come after I finished my Christmas shopping--and finally spent a bit on myself and a few loved ones.  Isn't that always the way?  I've also hit a really tough insomnia time: three hours a night, or none at all, for about a month.  Sometimes I get five hours, but I get a couple of hours, can't go back to sleep, then I get a couple of more...Overall, not restful.  As might be expected, this has led me to get a bit run-down, and a little sick, though nothing really terrible.  So I'm very out-of-whack, and exhausted, and just overall feeling really out of it.

But, surprisingly, I'm also very energetic, and I've had a series of minor epiphanies (if there can be such things) and I have a new-found appreciation for my space in life and those who occupy it with me.  Always good to have, but even more so at this time of year.  And so I am grateful.  Perhaps there will be more about this to come.  And thank-you to those who emailed and voiced concerns.  I'm fine.

In the meantime, I will leave you with a very quick review of A Storm of Swords, as I have decided to read the books while the series takes its long intermission.  And so--


Photo: U.S. hardcover, from its Wikipedia page


Unbelievably entertaining and engrossing read, which--as I pointed out in my review of its predecessor--is really saying something, since I knew every major thing that was going to happen. 

That in no way took away from the read, and may even have enhanced it.

As is necessary for high fantasy, and perhaps fantasy in general, the writing is so totally enveloping that it is like you're in that world.  World-building has to be perfect in books like this, but I'll bet that it's rarely this much so.  The Lord of the Rings books were less world-built than are these; I don't mean that as a negative towards Tolkien, as he paved the road and showed the way.  But Martin doesn't focus on over-description of grasses and trees.  Instead his writing is completely focused on completeness in every way: how everything looks, smells, etc., just as you're taught in writing classes, though not to this extent.  He doesn't just description from all of the senses: he focuses more on the sight and the sound, and less on the others.  And he does not describe to the detriment of the action, as Tolkien did.

Some scenes are better in the show, but to describe how and why would be to partly ruin the experience of reading the book, or watching the show.  So just a quick mention of what things are different, without mentioning how they're different:

--though the end of this book brings you up-to-date with this past season's end, the book ends with something not yet seen on the show.

--Brienne of Tarth does not do in the Hound.  I prefer the book's way.  It struck me as unrealistic that Brienne would run across Arya and the Hound, way out in the middle of nowhere, on an outcropping.

--Ygritte does not get killed by a little boy shooting an arrow.  I prefer the show's way, though I admit the book's way is much more realistic.  Martin does not go for the melodrama.

--Something major happens to Jon Snow on the Wall in the book and not in the show.  At least not yet.

--Jeyne of Westerling does not attend the wedding, which is like getting to the airport late and missing your flight, which then crashes.

--Littlefinger's dialogue before his push is much better in the show.  Essentially the same in both, but the show just nails it so much better.

--(Martin is better than the show's writers with the overall dialogue, and the everyday expressions, etc.  But at a climactic moment, the show's writers really nail it.  And this isn't because I saw it before I read it.  Trust me.)

--The book emphasizes how many guys Cersei sleeps with.  It's clearly a weapon for her.  The show does not...well, show this.

--The book makes it very clear who killed Joffrey.  Good to know I got it right from the show.  We know from the show that Littlefinger was behind the whole thing (which I wouldn't have figured out), but who exactly put the poison in the cup?  Oops...You did know it was the wine and not the cake, right?

--The book breaks the battle of the Wall into two or three distinct parts, over a few days.  The show gives it to us all at once, all in one episode.  I like the show's take better.

--The book does not show the giant's attack in the tunnel like the show does.  It was a good call of the show's to do so.

And there's more, but you get the idea.  I realized while reading that the show made some excellent decisions about what to emphasize (the scene between Tywin and Tyrion was better in the show, too, as is Tyrion's dialogue at that climactic moment) and what not to.  It is a rare thing that a show is better than its material, but it's a close call here.

But that's not why you should read the book.  The writing does something that the show, no matter how hard (or successfully) it tries, cannot duplicate: it envelops you into its world-building so completely that even a visual medium cannot match.

Friday, November 28, 2014

A Clash of Kings by George R. R. Martin -- Book Review


Photo: Hardcover for the book, from its Wikipedia page.  Not the edition I read.

 
You ever notice the longer a book is, the less you have to write about it?

Anyway, I suppose you wouldn't be reading this review if you haven't already a) read the book; b) seen the HBO series; or c) both, so I won't waste time writing about things you already know.

I'll just point out my favorite parts of this book.

1.  It reads very quickly.  Because it's 1,009 pages, this is no small thing.  Martin doesn't seem to get the recognition for his writing that he deserves.  I'm impressed by his vivid descriptions of just about everything.  Typically, overlong description is probably what Elmore Leonard meant when he said he tried to not write the parts people skip.  But when you're world-building as Martin is here, you really do have to describe almost everything.  This can be tedious in lesser hands.  But I found myself not skipping these parts.  In fact, I didn't skip any parts.  And a neat writerly trick I noticed from him: his sentences have much more alliteration, assonance and consonance than you'd think they would.  These things make the pages move.

2.  Daenerys's trip through the House of the Undying Ones was unbelievably well-written.  (And a figure in there murmurs the title of the entire series: A Song of Ice and Fire.)  Martin somehow encapsulates the themes of the entire series in one trip through this house, and does so both literally and figuratively--and mysteriously.  No small feat, since I've seen the episode already.  But seeing the show does not take away anything from the reading.  If you've been holding back for fear of that, don't delay any longer.

3.  The battle for King's Landing at the end was amazingly taut and suspenseful--again, no small feat, considering I've seen the episodes.  Even though you know what's coming, you're quickly turning the pages.

4.  Martin is able to delve deeply into all of his characters.  This is a helluva achievement because a) he writes about some women, notoriously difficult for a male writer to do; b) he gives equal time to every character, and there's a lot of them; c) he somehow holds it all together without confusing the reader; d) he knows just when to cut away from a character, and he knows just when to come back to a character; e) he doesn't fall into a pattern with his character cuts; he'll go away from a character and come right back to him again, then not return for many chapters.  In other words, it's not always A then B then C and then back to A again.  He cuts to and fro depending on what his story dictates.  I can tell you from personal bitter experience that all of this is not easy to do.  Agents and editors say not to write from too many POVs for a reason.  This may be the exception that proves the rule.

5.  The book is great even though the series follows it very, very closely, with only minor exceptions.  (And one or two major ones.)  But, again, no small feat, since I've seen the episodes and the episodes parallel the book very, very closely.

Anyway, even if you've seen the show, you should read this.  In fact, because you've seen the show, you should read this.

And I don't normally like these kinds of books.  World-building, sword-and-sorcery, knights and fair ladies, medieval stuff...not normally my thing.  Epics in general, especially fantasies, are not for me.  It took me over twenty years to read the three Lord of the Rings books.  I've never even tried to read any of the Harry Potter books (though I have them all).  I'm just too damned impatient for long books and long series.

But, as I mentioned, these may be the exception that proves the rule.

Friday, June 6, 2014

A Game of Thrones by George R. R. Martin


Photo: Title Card from the Series, from its Wikipedia page.

Book 1 of the long series was not a disappointment.  This is a helluva achievement in of itself, considering its 807 pages.  But it's even more impressive considering that I, like much of the known cable-connected world, have seen every episode of the HBO series.  Still, despite how incredible the series is (so much so that I am considering starting a blog about it, so look for that if you read my blogs), this book matches the series' awesomeness.

I started reading it because I wanted to see how close the series followed it.  I've also listened to every commentary available on the DVDs thus far (because I'm nerdy like that) and so I know how devoted the series' creators are.  Knowing that, how faithful to the book were they?  Answer: Very.  As in, basically page by page, and often verbatim.

But if you've seen every episode, you might say, wouldn't you be wasting your time if it's so close to the book?  Answer: No, as it turns out.  I thought the answer would be Yes, especially considering that the monumental struggle I had with the Lord of the Rings books.  (Much easier to read if you've seen the movies.)  But reading this was a breeze, despite the length.  Seeing it in words was different than seeing it on HBO.  I didn't see the characters from the series as I read the book.  (Well, except for Tyrion, played wondrously well by Peter Dinklage, who caught every single nuance of movement and voice from the character on the page.)  The book's characters were their own.

Martin is a very good writer; so much so that his turn of phrase was often surprisingly good even though I knew what was coming.  His words often summed up a scene better than the actual image did from the series.  I'm thinking specifically of the very last scene of the book and of one of the seasons, when Dany sat naked amongst the ashes of her dead husband, the woman who helped kill him, his horse, and three live dragons.  The book visualized this very well, even better than the actual visual image did.  (This is aided by the book's inclusion of the dragons breastfeeding with her, which the series did not show.)

The biggest difference: Tyrion and Jon Snow get along extremely well, and are almost good friends in the book.  The series does not show this.

So this is a rollicking good read.  If you were thinking about reading it, but holding off because you've seen the show, delay no longer.

Pick it up.