So effective a compendium of a few related (and maybe connected) stories that I remembered one of them over 15 years later. I wanted to re-read a first-person account of regret, and I remembered the one here of a college student in the 60s who barely made it to college, on a scholarship, only to learn that passing his classes and staying in college was literally a matter of life and death. Fail out, and he'd be drafted into Vietnam. Stay, and he'd live.
The bulk of the story was the Freudian death-drive of this character, and of the many around him. It was sick and depressing but very real. Anyone with a college degree may remember his own college days, and how his friends dropped like flies around him as they were unable to make the transition to self-responsibility and maturity. That, and not intelligence, I assure you, separated those who stayed and got a degree and those who didn't. You would think that since failing out could be deadly that these men would go to classes and pass out of basic necessity. But that's not the way it was when I went to college, and I doubt that the added stress would help them do better. It would make them fail out all the more, as most people that age simply cannot handle that much stress, while being on their own and education in college are stressful enough. Hearts, and the Queen of Spades, did these guys in.
The narrator of this part, surprisingly, is the only character not of importance in the other parts.
The book starts off with the story that led to the movie with Anthony Hopkins. It's very good, and also memorable, but it stops abruptly after a few hundred pages. It's long enough to be a full novel in itself, and it's got that nostalgic, past / childhood / innocence vibe that he did so well in IT. In fact, I feel that King stopped this one where he did because it was becoming another IT, and he didn't want it to go there. I'll bet he intended the other parts to all tie in solidly together in a long opus like IT, but then kept them apart when he realized he had something so close to IT that he had to make it markedly different. That's just a guess, and the interconnections later I think show me right, but that's up to you. There's a Beverly Marsh figure named Carol, and a Stuttering Bill, too. Pick up IT and fast-forward everyone about 12-15 years, so that IT's crew would be facing the Vietnam War in the face when they were of college age, and you've about got it. It takes place in Bridgeport, Connecticut, on the Housatonic--where Stephen King did spend a few years of his childhood--rather than in Derry, NH, but it's essentially the same.
The Willie Shearman section connects the least with everything, except there's a glove, and a theme of shame and penance. I kept waiting for it to strongly connect, or to be an important part of one of the other sections, but that never quite happened. The action he's ashamed of happens in the beginning story, and it's referred to in the last one, but Willie wasn't a huge part in that action, and he's a minor part in the Vietnam War section (and there's a strange joining of two characters from the first story that hits more as coincidence than connection; or, what's the chance of two characters from the same town coming together in the same platoon in Vietnam?), so the very small story with him as the sole character feels more like a character study than anything else. And it's a disconnected mystery about how the glove makes it from this section to the last.
But all in all this is a tremendous achievement in Stephen King's non-horror canon. Because surviving Vietnam was undoubtedly a horror, and the terror of surviving college to avoid the draft must have been a horror of a different sort. Both involved better men than me. This book is an off-shoot of the Tower, but you don't have to read that series to appreciate this. It worked for me like Bag of Bones did, and like some of the others of this time. And these were a helluva lot better than the drivel he's producing now, that's for sure.
His newest comes out in a few days, and I'll buy it and read it, but...well, what a drop-off there's been. I used to rue that so much of his stuff was tinged with the Tower, but I now see that his work has suffered since he's veered from the Beam. He needs to get back on it, and see where his literary legacy has gone, and get back to serving whatever Tower he'd been faithful to before.
Showing posts with label Connecticut. Show all posts
Showing posts with label Connecticut. Show all posts
Sunday, June 5, 2016
Wednesday, June 6, 2012
Sarah's Key by Tatiana de Rosnay
photo: cover of French version, second edition, from the book's Wikipedia page
Very effective book--about the French populace not recognizing the culpability of the French police being the Nazi's stooges in 1942--that would have been great without the emphasis on the present-day relationship struggles and the moralizing/browbeating by the author, through the main character. Though the real incidents portrayed via Sarah were real and horrifying, there isn't too much room for moralizing and browbeating in fiction. I could've taken quite a bit of that, as it is that warranted, but this book crosses the line and becomes a bit of a soapbox.
Having said that, this book is worth the read just for the scenes with Sarah, culminating upon her return to her apartment--though, really, culminating with a car and a tree in Connecticut. The tragedy of the tragedy ends with that car and tree, as we want our victims to live long and prosper. That doesn't happen too often in real life, and it doesn't happen here, and the tragedy is multiplied because of that, and because of the reasons behind the suicide. You never want the victim of unspeakable horrors to commit suicide, but the reality is that they often do. All of this is very sad, and it will stay with you, whether you want it to or not. Sarah's character will be a long-lasting one in the world of fiction, and Sarah's key is one of the better metaphors and symbols to come along in a long time. In fact, as such, it is shockingly underused in the book.
That the book focuses instead on the relationship between the main character and her husband is an author's mistake, I think, that is further highlighted by her comment in an interview at the back of the book that she did not want to write a book of historical fiction. Her aim was to include a bit of that, but to focus instead on creating a parallel to a modern-day relationship and its problems. It is this parallel, unfortunately, that very much doesn't work. You expect them to cris-cross at some point, and of course they do, but when they do, the moralizing starts, which degrades the effect of the tragedy. Part of the tragedy, in fact, is that the tragedy was largely ignored. It needed to stay tragic, rather than become fodder for a soapbox.
This failure with the parallel--and, I think, a failure on the author's rationale, as she states in the interview at the end that she thinks her readers want a book more about relationship struggles (and, hell, maybe they do, though this reader doesn't)--is that it counts too much on that moralizing, and on over-sentimentality, and on a large dose of coincidence. The main character's marriage ends in divorce, it is said, because the husband couldn't handle her devotion to the tragedy, and to her unborn baby (though the marriage was actually in trouble long before that, and one supposes that the husband would've had a problem with her focusing her attention on anything and anyone at all but him, and he was cheating on her for many years even before the timeline for this novel started); another man's marriage falls apart because his wife couldn't handle his preoccupation with the same thing--even though Sarah was this man's mother, so he had a much better reason for his preoccupation. Anyway, the main character and this man, separately, move to NYC after the failure of their marriages, and they both think about each other and keep track of each other without letting on to the other. They fall for each other right away, though the man was also upset with her, and his marriage was fine at the time. That they get together at the end, and the name that she gives her new daughter, will not surprise even a six year old reader, especially since the main character goes out of her way, several times, to narrate how beautiful this man's fingers and hands are...
...sigh...It becomes Schindler's List Meets Sleepless in Seattle. I do not exaggerate. (Well, perhaps a little.)
Could've been an outstanding book had the author book-ended the main story with the suicide, perhaps, or otherwise focused more on that. Focusing the entire second half of the book on the aforementioned things, rather than on Sarah at all, or on the tragedies in her childhood, and then at the end of her life, actually degrades the real-life tragedy and drags the whole thing into quasi-sappy melodrama.
Sarah deserved a LOT better than that. Sarah, in fact, transcends the trappings of this novel she's trapped in, and will live within you, outside the rather narrow confines of this book's borders. She's a character, much like Shakespeare's Juliet, that is superior to the work she's placed in. You'll be grateful, though, that the book exists as a vehicle for her to be born in, and then to survive and surpass.
For a look at a movie review from the New York Times that agrees with my assessment of the book the movie's based on, go to http://movies.nytimes.com/2011/07/22/movies/sarahs-key-directed-by-gilles-paquet-brenner-review.html. Its final word is the same as mine, in terms of the essential fault of the book and film: both stories couldn't co-exist in the same vehicle, and the one about the pitfalls of today's relationships trivializes the truth and tragedy of the horror that really did happen in Paris, France in July, 1942.
Very effective book--about the French populace not recognizing the culpability of the French police being the Nazi's stooges in 1942--that would have been great without the emphasis on the present-day relationship struggles and the moralizing/browbeating by the author, through the main character. Though the real incidents portrayed via Sarah were real and horrifying, there isn't too much room for moralizing and browbeating in fiction. I could've taken quite a bit of that, as it is that warranted, but this book crosses the line and becomes a bit of a soapbox.
Having said that, this book is worth the read just for the scenes with Sarah, culminating upon her return to her apartment--though, really, culminating with a car and a tree in Connecticut. The tragedy of the tragedy ends with that car and tree, as we want our victims to live long and prosper. That doesn't happen too often in real life, and it doesn't happen here, and the tragedy is multiplied because of that, and because of the reasons behind the suicide. You never want the victim of unspeakable horrors to commit suicide, but the reality is that they often do. All of this is very sad, and it will stay with you, whether you want it to or not. Sarah's character will be a long-lasting one in the world of fiction, and Sarah's key is one of the better metaphors and symbols to come along in a long time. In fact, as such, it is shockingly underused in the book.
That the book focuses instead on the relationship between the main character and her husband is an author's mistake, I think, that is further highlighted by her comment in an interview at the back of the book that she did not want to write a book of historical fiction. Her aim was to include a bit of that, but to focus instead on creating a parallel to a modern-day relationship and its problems. It is this parallel, unfortunately, that very much doesn't work. You expect them to cris-cross at some point, and of course they do, but when they do, the moralizing starts, which degrades the effect of the tragedy. Part of the tragedy, in fact, is that the tragedy was largely ignored. It needed to stay tragic, rather than become fodder for a soapbox.
This failure with the parallel--and, I think, a failure on the author's rationale, as she states in the interview at the end that she thinks her readers want a book more about relationship struggles (and, hell, maybe they do, though this reader doesn't)--is that it counts too much on that moralizing, and on over-sentimentality, and on a large dose of coincidence. The main character's marriage ends in divorce, it is said, because the husband couldn't handle her devotion to the tragedy, and to her unborn baby (though the marriage was actually in trouble long before that, and one supposes that the husband would've had a problem with her focusing her attention on anything and anyone at all but him, and he was cheating on her for many years even before the timeline for this novel started); another man's marriage falls apart because his wife couldn't handle his preoccupation with the same thing--even though Sarah was this man's mother, so he had a much better reason for his preoccupation. Anyway, the main character and this man, separately, move to NYC after the failure of their marriages, and they both think about each other and keep track of each other without letting on to the other. They fall for each other right away, though the man was also upset with her, and his marriage was fine at the time. That they get together at the end, and the name that she gives her new daughter, will not surprise even a six year old reader, especially since the main character goes out of her way, several times, to narrate how beautiful this man's fingers and hands are...
...sigh...It becomes Schindler's List Meets Sleepless in Seattle. I do not exaggerate. (Well, perhaps a little.)
Could've been an outstanding book had the author book-ended the main story with the suicide, perhaps, or otherwise focused more on that. Focusing the entire second half of the book on the aforementioned things, rather than on Sarah at all, or on the tragedies in her childhood, and then at the end of her life, actually degrades the real-life tragedy and drags the whole thing into quasi-sappy melodrama.
Sarah deserved a LOT better than that. Sarah, in fact, transcends the trappings of this novel she's trapped in, and will live within you, outside the rather narrow confines of this book's borders. She's a character, much like Shakespeare's Juliet, that is superior to the work she's placed in. You'll be grateful, though, that the book exists as a vehicle for her to be born in, and then to survive and surpass.
For a look at a movie review from the New York Times that agrees with my assessment of the book the movie's based on, go to http://movies.nytimes.com/2011/07/22/movies/sarahs-key-directed-by-gilles-paquet-brenner-review.html. Its final word is the same as mine, in terms of the essential fault of the book and film: both stories couldn't co-exist in the same vehicle, and the one about the pitfalls of today's relationships trivializes the truth and tragedy of the horror that really did happen in Paris, France in July, 1942.
Subscribe to:
Posts (Atom)
