Give me books, fruit, french wine and fine weather and a little music out of doors. --John Keats
Showing posts with label YA Fiction. Show all posts
Showing posts with label YA Fiction. Show all posts

Thursday, March 6, 2014

"Paper Towns" by John Green

I have no idea when I bought this book (although I do know it was before Tuesday, September 21, 2010). I do know why I bought this book: first, the author is John Green, and second, it was on sale for $2.97.

The spine of Paper Towns caught my eye on my bookshelf (not my Future Reads shelf, which is where I'm supposed to be finding my next selections, if only to make the choice less agonizing, but that's my own rule so I am welcome to break it) as I was putting my youngest to bed on Sunday night. I knew absolutely nothing about the story, but I felt sure it would be a good read and I was fairly certain I wouldn't get stuck on it for weeks.

I was right on both counts: I enjoyed the book and finished it last night. And because I would really, really like to pick up another book now (though I haven't even given a thought to which one will be next), and because the rule I made in my last post is too new to break even if it is my own, I am proud to be posting about this book within 24 hours of completing it!

John Green is so good at capturing the anguish of teenage love. And the voice of a teenager. Or . . . I don't know, it sure has been a long time since I was a teenager, so I could be wrong about that. There were times where the "witty repartee" seemed a bit too slick to be believable. But it can't be denied that he tells a good story!

I find it difficult to describe the book's plot without giving too much away, so I'll err on the side of saying too little: a slightly nerdy teenage boy is starry-eyed about the beautiful girl who lives next door to him. For the first half of this book I was thinking Paper Towns was merely a variation on Green's Looking for Alaska, right down to the dynamics between the main characters. But, happily, I was wrong, and this turned out to be its own unique story, full of its own secrets.

And what do you know? On the very first page I found out the story begins in Orlando. Can you believe it? (Did I mention I'm going there next week?) But I only had to turn one page to discover it's not about the Orlando I'm going to. (At least that's my hope.) This is definitely not a Disney story. But I liked it (probably more than I would have liked a Disney story) and was absorbed by Quentin's hunt for clues. Paper Towns won't join the ranks of my Most Favorite Books Ever, but it was fun without being fluffy.


Tuesday, September 13, 2011

"Speak" by Laurie Halse Anderson

"When people don't express themselves, they die one piece at a time. You'd be shocked at how many adults are really dead inside--walking through their days with no idea who they are, just waiting for a heart attack or cancer or a Mack truck to come along and finish the job. It's the saddest thing I know."

I'm about to express myself. Madonna, eat your heart out!

I watched the movie version of this story before I even realized it was a book adaptation, but then I started hearing all kinds of good things about the book from other bloggers. I have been known to be a tad, shall we say, disparaging towards YA fiction. But as impressed as I was with the movie, I figured surely the source material couldn't be all bad. And when I saw this in the book section at Target (I was hardly even looking at the books, I swear!) it just sort of leaped off the shelf and into my hands, whispering, "Take me home with you." So I did. (Don't worry, I paid for it first.)

On the surface, Speak is kind of like a cross between the movie Heathers (only with less of its midnight black and razor sharp humor, and with fewer Heathers) and The Perks of Being a Wallflower, with the Angst-Causing Teen Issues whittled down from every single possible traumatic life experience to one or two. In case it's unclear to you, that's not a bad combination. Where Heathers may be a bit silly and unlikely (though still awesome!), Speak is steeped in reality. Melinda Sordino could be any girl in any high school in any state in America. That is, any girl with a Big Secret she finds so shameful that she doesn't feel like she can talk about it to anyone.

At just under 200 pages, of course I zipped through Speak, though the excellent writing and absorbing plot didn't hurt a bit in that respect. The book didn't quite reach critical mass for me, but I bet if I hadn't already learned Melinda's Big Secret while watching the movie, I would have found myself the prisoner of an inexorable Chain Reaction of Curiosity, rendering me incapable of putting the book down. You know how I feel about secrets! They drive me bonkers, and I can not rest until I have ferreted out every detail.

I won't tell you what Melinda's Big Secret was, on the off chance that this will leave you able to enter into your own Chain Reaction of Curiosity as you read, but I will mention that (as a result of the secret) Melinda sinks into a depression that consumes her for most of her freshman year of high school. That's not to say that the book itself is depressing. It can be heartwrenching, but it's not a complete downer. Sometimes it's even funny (though, as I mentioned, not Heathers-funny) in a wry and subdued way. And Anderson nails the teenage voice.

Although I am labeling Speak as "not suitable for children . . . or my mom," I do think my mother could probably handle this one. As could the average high school student. I mainly have my 8-year-old daughter in mind when applying this label. She's not ready for it yet.

Saturday, December 4, 2010

"The Ask and the Answer" by Patrick Ness

I had to force myself through the first half of this book. I was already strongly invested in the trilogy due to The Knife of Never Letting Go, and I never thought of giving up, but it wasn't until I reached the second half that this book regained some of the breathless momentum of its predecessor.

Spoiler avoidance hampers me from saying much about the plot; not only do I have to worry about spoiling this book, but the first one ended with such a cliffhanger that anything I say could spoil it too. However, I can't imagine anyone coming to this book without having read Knife first, and all you really need to know is that it's a continuation of Todd Hewitt's story.

One thing I really appreciated at the beginning of the book was the way that Patrick Ness managed to remind his reader of all the pertinent details from the first book without seeming like he was doing so. Reintroducing the characters and their situations was not merely a repetition of a list of attributes; Ness managed to seamlessly work this information into the story.

Another little bit of magic that Ness impressed me with was his villain. I can't explain to you why I did not find him completely hateful. I wouldn't say I ever really sympathized with him, but oddly enough, throughout most of this book I almost liked President Prentiss. I'm not usually one to root for the evil oppressor, but there was something fascinating about this one. As the book wore on he sort of lost his sheen, and by the end--as they say in Texas--he "needed shootin'," but for most of the book he was quite intriguing.

While reading, I marked several brief passages that interested me. I'll let you in on a few of them for your own personal edification. Be grateful that I'm sparing you my thoughts on each, though I will say I found more truth in them than in Paulo Coelho's steaming piles of crap. Here you are: We are the choices we make; nothing more, nothing less. How do you know you're alive if you don't hurt. A man is capable of thought; a crowd is not. To see the ocean once is to learn how to miss it. An idea lives on after the death of the person. AND, women don't really fart in their sleep . . . do we?

It's a good thing I was already prepared for the lack of resolution at the end of the story. Whoever warned me that this book was just as ending-less as Knife was definitely right, but since I was ready for it, I was much less frustrated by the fact. Even so, I'm going to take another break from Chaos Walking and read something else. But it won't be long before I wrap things up with Monsters of Men.

Monday, November 22, 2010

"The Knife of Never Letting Go" by Patrick Ness

This book doesn't have an effing ending and I'm not very happy about it. I mean, sure, it has a final page, and the last sentence even ends with a period, but it's not a ruddy ending. Patrick Ness has unapologetically dragged me into his trilogy and now I couldn't get out even if I wanted to.

The nice thing is that I don't want to. This is not the sort of book where I only have to read the sequels. No, I want to keep reading. I want to know what happens to Todd Hewitt. It doesn't hurt that I can't even imagine what might possibly be coming next.

But I can tell you a little bit about what came before. Todd Hewitt is just one month shy of his thirteenth birthday, which means manhood in the community of Prentisstown. Life may not be exactly as Todd wishes it--he's an orphan, and he's been stuck with a talking dog instead of getting his fissionbike fixed--but he feels secure in what he has known all his life on New World. And what he knows, above all else, is that a germ was responsible for killing all of the women in town, leaving the men awash in each others' Noise--the constant mental barrage of thoughts every resident transmits involuntarily.

Of course it's not long before everything Todd has ever known is turned on its head. He is forced into a journey--one that is metaphorical as well as physical--that opens his eyes along with his mind. His path is beset by tension and danger and askings and answers that cause Todd to mature in a way that he never would have, had he remained at home in his snug cocoon of ignorance.

Too bad the book kind of sounds like it sucks when I describe it. It really doesn't, at all. I promise. Well, except for the non-ending.

Don't let the presence of a talking dog put you off. Manchee is very different from Enzo in The Art of Racing in the Rain, but he's just as appealing. Either you will love him or you are not human. I have it on good authority that even people who don't like dogs (gasp! there really is such a thing) love Manchee. He made me laugh from the very first time he said, "Need a poo, Todd." (Though, of all the New World animals, my favorites were the crickets. I can hear real ones outside my open window as I type, and I giggle because now I know what they're saying.)

Even though the ending of this book just begs me to read The Ask and the Answer right away, I refuse to be manipulated. I'm reading something else first. But I will read the sequels soon. I have heard that the second book ends very much like the first (in that it doesn't), but surely the third book will end with some semblance of finality. If it doesn't, watch out. My wrath will know no bounds.

Monday, October 4, 2010

"The Outsiders" by S.E. Hinton

Here's a book from my "I can't believe I've never read this before" list. (Well, I don't really have such a list, but I ought to. I have lists for everything else. Why not one more?)

I'm sure I'm the only one who's been living under a rock for the past few decades, but just in case I've had some company, this is the story of fourteen-year-old Ponyboy Curtis, the youngest of a gang of "greasers" living in Oklahoma in the 1960s. Their central conflict is with the "Socs," a group of rich kids with too much time and money on their hands.

The greasers have some pretty serious issues to deal with in their lives, but none of those issuses were added for shock value (I'm thinking of the movie Thirteen when I say this). Instead, we're given an honest and realistic portrayal of life as a kid from the wrong side of the tracks. Granted, that portrayal may be slanted to get the reader to sympathize with the greasers, but it works.

What most impresses me about this book is that the author was fifteen years old when she started writing it. When I was that age, I couldn't see much farther than my plans for the coming weekend. And not only was Hinton young, but she managed a believable male voice. Writing from the opposite gender's point of view is something I've found even fully mature authors can have trouble with.

I watched the movie just a few months ago, and I've gotta say (beyond the horribly dated music) they did an excellent job with it. The book adds very little to the experience, although it does add some.

One of the main things I found in the book which I didn't glean from the movie (maybe it was there, but either I didn't notice, or I've forgotten since I didn't write it down) was the explanation for Johnny's line, "Stay gold, Ponyboy." I guess I always thought Johnny was basically just saying "stay cool," but there's more to it than that. Johnny is asking Ponyboy to retain the beauty of his innocence--to avoid being hardened by the harshness of reality, to hold on to the childlike tenderness in his heart. The wording came from this Robert Frost poem:
"Nothing Gold Can Stay"

Nature's first green is gold,
Her hardest hue to hold.
Her early leaf's a flower;
But only so an hour.
Then leaf subsides to leaf.
So Eden sank to grief,
So dawn goes down to day.
Nothing gold can stay.
Now I finally understand why that guy from high school told me to "stay gold, Ponyboy."

Tuesday, September 21, 2010

"Looking for Alaska" by John Green

Nothing like a little Young Adult fare to cleanse the palate. It's certainly the sorbet of the literary world, which is exactly what I needed to get over Anna Karenina.

Too bad I chose one that made me cry. Yes. I, of the iron will and the stone stomach, I who am devoid of sympathy, I who roll my eyes in the face of Nicholas Sparks and his tear-jerking ways. I shed a tear over this book. Or two.

In my defense, I did not boo-hoo. It was just a very quiet leaky-eye thing. I could have blamed it all on a wayward eyelash or a misplaced elbow (not my own, of course, because that's not possible. Try it. You'll see). Instead, a much more logical explanation is the fact that I cried for the time in my life that was awfully similar (though not so that anyone else would recognize it) to the cause of sadness in the book.

But I don't want to talk about my secret sorrow. I want to talk about banned books. It seems that next week is "Banned Books Week," which has come accompanied by a timely stink. Looking for Alaska is one of those books that has been frequently challenged, so far as to be called pornography. (Um, whaaa?) Hard-core, even! I am not a seasoned reader of "hard-core porn," but I hardly think a few scenes of teenagers making out constitutes any kind of porn at all.

However, I do have an opinion on book banning and I'm about to share it with you, like it or not. I must admit I am slightly ambivalent on the matter. On one hand, I am fundamentally opposed to the idea of banning books. The whole thing just seems wrong, up there with imprisoning journalists for speaking out against the government. On the other hand, there are many cases where age appropriateness should be taken into consideration when choosing reading material.

Looking for Alaska deals with a lot of topics that I don't want my kids reading about yet. Of course, my oldest is ten. He is completely unconcerned with this sort of book and I hope he stays that way for at least five more minutes. Once he hits high school, however, I'm pretty sure my resistance will fade. After all, it's kind of naive to think that high school students would be surprised by anything found in this book. I would not prevent my children from reading Looking for Alaska when the time was right, though I would want a chance to reiterate my opinions on smoking, drugs, drinking, and teen sex. Opinions which, if I've done my job right, my kids will already be plenty familiar with.

Because that's what it all comes down to: personal responsibility. It is each parent's job to be aware and informed, to decide whether they feel a book is appropriate for their own child, and when. It is not any other person's job to conclude that my child shouldn't read a particular book. Yes, I do ascribe to the somewhat old-fashioned notion that it is my job to give my children some guidance, rather than allowing them to open Pandora's box and flood themselves with all the evil in the world while they're still practically babies. But once they are ready for more adult themes, I'm not going to shelter them from books like these while I still have the chance to help them form their worldview.

Oops. I don't usually do this. I mean, I have opinions, but I prefer not to bring up touchy subjects on my blog. I like this to be my happy fun place. But these were the thoughts brought on by this book, and beyond expressing them, all I would have to say is that this book is edgy, well-written and a page turner. I can imagine that high school students must love it, just like the kids at the children's library loved Phoebe's singing because she told the truth.

And a sort of post script on the author: over the past few months I've gotten the idea that John Green can do no wrong. In the style of a true literary amnesiac, I can not remember which bloggers gave me that idea, although a quick google blogsearch shows me that two blogs I read (Raych and Nymeth) have discussed the author in general and this book in particular, so maybe it's their fault. One of these days I will also be reading Paper Towns, since I've already bought a copy based on the Can Do No Wrong theory.

Friday, September 17, 2010

"Jacob's Ladder" by Brian Keaney

I found Jacob's Ladder while hunting a selection for this month's Book Club meeting. The title caught my eye first, making me wonder if it was in any way related to the 1990 freak show of a movie by the same name (it wasn't). I flipped through the first few pages and was intrigued by the the idea of the main character waking up in the middle of a deserted field with no recollection of how he got there. (Remind you of college? Yeah, well, it's nothing like that.) The book met a couple of the more important Book Club criteria (it was cheap, and Books-A-Million had multiple copies on the shelves), so I decided we would give it a try.

It was an interesting and fast read. There were plenty of questions to keep me turning the pages--why were the children in Locus and how had they arrived there? What had happened to their memories, and when might they be able to return to the families they knew they must have loved but could not remember?

But even with the absorbing aura of mystery, I'm afraid this book won't evoke the best Book Club discussion. The story had immense potential, but it was only spun into a single thread. As I read, I yearned for the complexity and depth Keaney could have given it with further development. I wanted strands of many colors woven into a tapestry. Instead, the straightforward and unadorned narrative reminded me of The Alchemist. Of course, Jacob's Ladder was written for kids, so I probably shouldn't complain about its simplicity. For what it is, it's a great story and is well-written.

The author has his own blog and you can read an interesting bit about the book here. And now I am off to book club! I hope you have as much fun tonight as I'm about to.

Wednesday, April 28, 2010

"Thirteen Reasons Why" by Jay Asher

I have no business taking books out of the library when I already have so many books at home begging me to read them. But I heard about this book here, and when I found that my local library had a copy, I couldn't resist.

The premise is an interesting one, and quite unique. The narrator is one of thirteen people who Hannah Baker blames for her suicide. Just before overdosing on pills, she related her reasoning on audio tapes, which she then mailed to the first person on her list with instructions for them to successively pass the box of tapes on to each of the twelve subsequent people.

The writing isn't stellar, and I found myself not really believing that, #1, Hannah was actually depressed enough to kill herself (just judging by her tone on the tapes which, while perhaps bitter and alienated, didn't really sound suicidal), and #2, that her thirteen reasons were adequate to put her in that frame of mind. Ok, at least two of the thirteen were pretty harsh, but the other eleven . . . not so much. (Ironic thing is, I bet that is exactly what all thirteen people would have thought, too.) But neither of these things kept me from breathlessly flipping the pages. It's definitely an absorbing story.

The book does have a good message, too, which I hope that any teen reading it can recognize: be vigilant, and be kind.

Tuesday, February 23, 2010

"The Golden Compass" by Philip Pullman

I just had to see what the fuss was all about. Was this book really such a horrible anti-God diatribe that would subtly (or even overtly) brainwash my children, or was it as harmless as Harry Potter? As I first started reading, I was uncomfortable about the idea of every human in this alternate universe having their own personal "daemon," which sure sounded a whole lot like a "demon" to me, but it quickly became clear that a "daemon" is like an external soul with nothing evil about it, so I could accept "daemons" as no big deal.

Surprisingly, for most of the book it was slow going. In the first two sections I didn't find myself caring about any of the characters or even compelled to pick the book up beyond trying to get it over with so I could move on to something else. I didn't really become interested until page 337 (painfully close to the book's conclusion on page 399) when Lyra cleverly tricked Iofur in a way that hadn't even crossed my mind. From there until the end there was plenty of suspense to sustain my interest.

Because of the way most of the story dragged for me, I can't imagine a child sticking with this book (although I am sure there are many that must have). Not only that, but even I didn't see that anyone was trying to "kill God" like I'd heard. (Or will that come in one of the other two books of the trilogy?) One of the main characters was trying to destroy death, but no one said anything about killing God. Even if the author intended this story to be about killing God and somehow masked that idea with some sort of symbolism, I didn't pick up on it, and surely a child wouldn't either. For those two reasons, I have no fear of allowing my own children to read the story, although I won't push it on them any more than I would suggest any other book I didn't especially enjoy. My opinion is that this book is indeed as harmless as Harry Potter. (And, in case you were wondering, my opinion is that reading Harry Potter books won't make your child interested in practicing witchcraft any more than playing cops and robbers will make him grow up to be a burglar).

I haven't seen the movie (although I plan to), but I can totally picture Nicole Kidman in the role of the kidnapping lady, Mrs. Coulter. (Is this her role? It must be, as there is really no other significant adult female role.) Yet again, I can imagine the movie might be better than this book, but I guess I will have to watch it and see.

Friday, February 12, 2010

"The Lightning Thief" (Percy Jackson & the Olympians Book One) by Rick Riordan

I had heard of these books before but really didn't pay any attention until I saw a preview for the upcoming movie, which looked to be every bit as good as the Harry Potter movies. This is a wonderful thing, since I know there are only two Harry Potter movies remaining, and I wondered what would take their place.

I had heard that the Percy Jackson books are not as good as the Harry Potter books but that they are still enjoyable. Well, I would say that I concur. The story itself is imaginative and entertaining. I'm interested enough in the characters and their situations that I would like to read Book Two: The Sea of Monsters. However, the writing is choppy, with lots of one-sentence paragraphs.

Kind of like this.

Pretty annoying, huh?

I thought so, anyway.

The name Rick Riordan sounded familiar to me, but it wasn't until I was about halfway through the book and I flipped to the back to read about the author that I figured it out. As soon as I saw that Riordan lives in San Antonio, I thought, Big Red Tequila. Sure enough, that's how I recognized his name. We read BRT years ago in Book Club, and it was not one of my favorites. My biggest complaint was about the main character. He seemed amorphous and vague rather than solid and believable, almost as if the author couldn't decide how to write the character and ended up with a mess of contradictions that were not cohesive. I digress, of course, especially since I didn't see a similar problem in this Percy Jackson book.

I will say that this might possibly be one of the only books where the movie version is better. (Oh, wait, I forgot about Under the Tuscan Sun, where the movie had a plot and the book didn't). I can't say for sure until I've actually seen the movie (which I do plan to do, though I'm not sure if I'll go to the theater or wait for the DVD), but action outweighs thought in this book and, judging by the preview, they've done a decent job making a good movie out of the story.

Tuesday, February 2, 2010

"Peter and the Starcatchers" by Dave Barry and Ridley Pearson

This Peter Pan story would have been better if I'd read it to myself straight through. As it was, I read it to the kids bit by bit at bedtime, and it took us months to finish. This definitely interrupted the flow. It didn't help that in the second half there was too much back-and-forth with the trunk. Peter has the trunk. No, Slank has the trunk. Now Peter has it again. Now Black Stache. No, it's Slank. It was like watching a ping-pong match, and that's never fun for very long, even if the players are the really good Chinese guys who jump up on the table every now and then. Oh, I don't know, maybe ping-pong is too entertaining to be a fair comparison. Maybe it was more like listening to a baseball game on the radio. The book could have been much shorter than its too-long 451 pages if they had cut some of that out.

I did enjoy the prequel aspect of the book. It was fun to hear the back story about things like how Black Stache (who evidently turns out to be Captain Hook) lost his hand. I mean, I already knew Peter fed it to the crocodile (whose name, by the way, is Mister Grin, in case you didn't know), but here I got to read all the gory details. Speaking of gory, even my 9-year-old son commented that the book was a little bloody. My 6-year-old daughter really wasn't very interested in the story and would usually play by herself in her room when it came time for me to read it, which is really odd because she's the one who loves books and usually can't get enough of them. My 3-year-old daughter almost always joined us for Peter storytime, but I think that was mostly just so she could snuggle in my lap as I read.

This book tells us how Tinkerbell came to be (although it doesn't mesh with the story in Disney's Tinkerbell movie, which is surprising as this book is labeled as a "Disney Edition"). It also explains how Peter and his Lost Boys ended up on the island, although I really thought you had to fly--and not in an airplane!--to get there (past the first star to the right and straight on 'til morning), but Peter got there by boat. That aspect made "Neverland" seem a bit too common, even with the mermaids (which also were explained).

I feel like all I have done is complain about this book, which is misleading because it's really not all that bad a read. I did like Greg Call's illustrations, although it kind of annoyed me that Tinkerbell's wings had feathers. They're supposed to look like dragonfly wings. (There I go complaining again). And, ugh, there are already 3 other books in this series, and my son is expecting me to read them all to him. It's going to be a year before we're finished with all of them. I guess I just need to sit back and enjoy the ride. My 3-year-old is not going to want to sit in my lap forever.

Friday, January 15, 2010

"The Goose Girl" by Shannon Hale

Finally the long-awaited book was returned to the library, and this time I was lucky enough to be the one to check it out. I interrupted my reading about war in the Val d'Orcia for a breath of fresh air, and did not regret it for a moment. This book was every bit as magical as I expected it to be.

Once again throughout this book Hale exhibits her prowess with words. In one example of many, when the Crown Princess was sitting at her father's deathbed, a lesser writer would have said her chest felt hollow, or perhaps empty. Hale, however, describes Ani's chest as "an abandoned snail shell," making a clear point about her empty feeling while at once adding depth to the idea by letting the reader know Ani also felt wrenched and contorted inside, worthless and discarded.

I knew well the original fairy tale of The Goose Girl. This was good and bad. Good, because it is often quite enjoyable to read a familiar old story that has been fleshed out and given beautiful color and texture; bad, because the book held few surprises for me. It was obvious that Selia would be the maid to usurp the identity of the princess, and I knew the general direction the plot was headed at each turn. Also, a disappointing result of having read the sequel first was that I knew Geric was the prince to whom Ani was betrothed, so there was no surprise for me there, although I do wonder if I might have suspected his identity even without that foreknowledge.

As much as I have enjoyed Hale's writing, I am not sure that I will seek out any of her other novels. The third in the Books of Bayern series, River Secrets, follows a minor character named Razzo who was never especially compelling for me, although he does play a larger part in the second book than in this one. The fourth book, Forest Born, follows a character not even introduced (that I recall) in the first two books, Razzo's sister Rin. And Bayern is not like Narnia, constantly calling me back even after all these years. I am even more resistant to reading either of Hale's two books written for adults, as they both seem to be of the "chick lit" variety and I don't want them to ruin my opinion of her as an author. However, I will make my official excuse by pointing to my overlarge stack of books I already have waiting to be read.

Sunday, January 10, 2010

"The Graveyard Book" By Neil Gaiman

I picked this book up at the library because I enjoyed the movie Coraline (adapted from a book by Gaiman) and have been wanting to read that one, so this is kind of a substitute.

Fortunately for me, this book more than made up for my most recent foray into so-called ghost stories (The Ghost of Windy Hill, which would more accurately have been called "Sorry, Kathy, There's No Ghost on Windy Hill, So I Hope You're Not Too Disappointed"). This book was packed full of more ghosts than I could count, and it had a much more complex combination of story arcs.

Still, this book was a little different from your usual ghost story book. It didn't have the same creep factor. This was mainly because all of the ghosts were friendly and obliging. The tension and trouble came from the world of the living rather than the spirit world. It did have wonderful and nearly tangible atmosphere, however, especially at the beginning, as well as during the Danse Macabre (although I wasn't sure quite why that was a part of the book otherwise).

I loved that Mr. Frost turned out to be the man Jack. I didn't see that coming until the last minute. It's funny that I was thinking more along the lines of him being related to Robert Frost, and it never crossed my mind that he could be Jack Frost until he "put his hand down into the empty space where the floorboard had been," which is mere sentences before he pulls a knife and tries to kill Bod.

I was also pleased that, although Silas was pretty plainly a vampire, we are never specifically told this. I appreciate the author's assumption that I was smart enough to figure it out for myself.

I enjoyed this book like Nobody's business! (Get it?) I agree with one of the reviews on the back that says, "I want to see more of the adventures of Nobody Owens." I think in the next book some of the other Jacks may return as ghouls . . . and surely Scarlett will show up again.

Wednesday, December 23, 2009

"Distant Waves: A Novel of the Titanic" by Suzanne Weyn

Ever since Bob Ballard found the final resting place of the Titanic and I breathlessly read the details in the December 1985 issue of National Geographic, I have been fascinated by the story of this ill-fated ship. Of course the 1997 movie with Kate Winslet and Leonardo DiCaprio just whetted my appetite for more. So how could I pass up this book I found at my son's Scholastic Book Fair?

Unfortunately after reading this book I find I'm kind of annoyed that it was subtitled "a novel of the Titanic." This was false advertising. Other than a few brief mentions and some foreshadowing, the entire first half of the book has nothing to do with the Titanic. In fact, the entire book is more of an exploration of spiritualism.

Not only that, but though I had expected this to be historical fiction, far too many liberties were taken for me to apply this label. My definition of historical fiction is a novel in which true historical events are seamlessly interwoven with conversations and situations that very likely could have happened. It was hard enough to swallow that the narrator came into contact with so many famous historical figures (and not just on the Titanic itself, which may have been more believable); but when Nikola Tesla sneaks onto the ship, inadvertently causes initial damage to it with his "earthquake machine" before the iceberg finished it off, then tries to save everyone through time travel . . . well, let's just say my disbelief was too heavy to be suspended by such a thin thread.

The book did have a very sweet love story (between Thad and Jane) which I found myself rooting for, and a very satisfyingly happy ending (though, in a book filled with unbelievable coincidence, this was probaby the most improbable of all), and I give props to the author for the "Author's Note: What's Real in Distant Waves" addendum. If my expectations hadn't varied widely from the reality I might have enjoyed this book more. I think the back of the book should have given more of a warning that this book is more of an alternate history than historical fiction. Now that I know the story, I understand the last sentence of the blurb which ends by saying, "at least one of [the sisters] will find herself out of time." I thought that meant she would die, but I guess this actually refers to Tesla's time machine. Ack.

Monday, December 21, 2009

"Being Dead" by Vivian Vande Velde

I must preface this post by saying that the Mesa Public Library Friends' Bookstore in Los Alamos ROCKS. I have found buried treasure and I didn't even have to dig. I brought home eighteen, count 'em, eighteen books today, half of which were on my list of books I want to read, the other half just looking too intriguing to pass up, and most of which were only 50 cents each (and only slightly used)! An even better deal than paperbackswap.com! Now my stack of books to read is so tall that it threatens to topple over on me in my sleep, but that's a good problem to have. (Not falling books waking me in the night, but having a plethora of good and as-yet-unread books on hand).

The first of the eighteen books I chose to read is a collection of 7 ghost stories. I love a good scare! These stories were deliciously and satisfyingly creepy. The book was written for "ages 12 and up," and through most of the first story I thought about passing this on to my book-loving daughter next (as long as she could get past the cover art), but the story turned out to be just a little too creeptastic. And if I wasn't yet convinced, when the protagonist of the sixth story called her boss an anal sphincter (in the vernacular), that sealed the deal. My daughter can wait a few years before reading this book.

I do wish I could find someone who has read this book so I could discuss the story entitled "Shadow Brother" with them. Ambiguity is stalking me again. Kevin was haunting his father, and the narrator (Kevin's sister Sarah) hints at why this might be, but it's not spelled out for me. I want to know the truth! I've been told it's out there.

All in all, this collection of stories is a bunch of shivery fun. I was quite pleased that the book contained no stories with a silly punch line like "Vicks will stop that coffin!" or "inside the ancient box they found the source of the mysterious rapping noise, and it was . . . wrapping paper!" On the other hand, I'm not afraid of the dark or expecting a corpse to creep up behind me after reading it (which is probably a good thing). To me, this means the stories were just spooky enough.

Thursday, December 17, 2009

"The Lacemaker and the Princess" by Kimberly Brubaker Bradley

This book caught my eye at my son's Scholastic Book Fair and I just had to buy it. As if my stack of books to read were not already tall enough. But it looked like an interesting story, it was only $7, and I figured if I didn't care for it I could swap it when I was through.

This is a YA novel of historical fiction set during the French Revolution; the titular princess is Thérèse, the daughter of Marie Antoinette. I picked it up expecting a fun, fast read, and was not disappointed. It served well as a palate-cleanser after Tomcat in Love, and it went by like a breeze.

Throughout the scene where the mob of hungry women stormed into the grounds of the palace at Versailles demanding bread, I had braced myself to hear Marie Antoinette petulantly suggest that they eat cake instead, even though from what I have gathered that would not be historically accurate. So I was quite pleased to find that the author resisted that temptation, never allowing Antoinette to appear as callous and ignorant as she would have to have been in order to speak so thoughtlessly. In fact, Antoinette was never portrayed as anything other than beautiful, gracious, kind-hearted and generous; it just was not enough to please a starving populace.

Although Marie Antoinette may never have said, "Let them eat cake," the book still managed to clearly convey that the royal family was in large part clueless regarding the daily trials their people suffered merely in order to subsist. The royal family in general, and Marie Antoinette in particular, did their best to aid their people whenever they saw a need; however, so comfortably ensconced in their bejeweled palace, they remained oblivious to the amount and degree of need. They had a distinct separation from and ignorance or denial of the poverty that surrounded them. Just one example of how far removed the royal family was from reality is seen in the way Antoinette thought she was raising her daughter like any other child, without the burden of being treated like a princess, while the life of Thérèse was absolutely nothing like that of a common child. The "not a princess" concept was true only in theory, not in practice.

This is a good (if not especially in-depth) review of the history of the French Revolution, with great descriptions of life in 18th century Versailles (both in and out of the palace), and an enjoyable read. I was especially impressed that the author successfully managed to present both sides of the revolution in a balanced manner that keeps the reader from deciding that one side was right and the other side was evil.

I'll probably pass it on to my book-loving daughter and see what she thinks.

Tuesday, December 8, 2009

"Enna Burning" by Shannon Hale

I have been waiting so long for my local library's copy of The Goose Girl to be returned (whoever has it must be a REALLY slow reader!) that I finally gave up and tried one of Hale's other books. As it turns out, Enna Burning is actually a sequel to The Goose Girl, but I don't think it contained any spoilers, so I should still be able to enjoy "Goose" if the library ever gets it back. In fact, I may enjoy it even more now, since I am already familiar with several of the main characters.

Enna Burning was just as well written as The Princess Academy, although I think this one was geared towards slightly older children (perhaps young teenagers as opposed to preteens). Comparatively, this story has more danger, more romance and more angst in general. I was especially captured by the love which was developing between Enna and Sileph, and the sweet and pure relationship that grew between Enna and Finn. While it lasted, it was an engaging love triangle; until Sileph's lies were revealed, I felt just as torn as Enna between Sileph and Finn. Steadfast and unwavering Finn, with his heart of gold, certainly deserved to be the one to win Enna's love.

The story has the same fairytale-like quality as Hale's Princess Academy, although the writing itself doesn't have the same sweetness. "Enna Burning" actually reminded me more of M.E. Breen's Darkwood in tone, though "Enna" was the better book.

I thought it was interesting that this novel was set mainly in a country named Bayern. I wonder if it is common knowledge that Bayern is the German word for Bavaria (a southern region of Germany)? "The Forest" west of Bayern, where Enna was raised, certainly seemed to be modeled after Germany's black forest to the west of Bavaria. Not that this is a problem for me. I just found it interesting.

Sunday, November 1, 2009

"Darkwood" by M. E. Breen

Here is another children's novel that caught my eye at the library. Ostensibly I select books like these with my children in mind, but none of them seemed interested in reading it (though I can't imagine why).

While reading I was delightfully reminded of a handful of other books and movies, although I should have written them down as I thought of them, because now the only ones that come to mind are the Wizard of Oz novels, and even--somewhat inexplicably--the movie The Postman.

This book is a little bit uneven. It has a strong start, but when Annie reaches the castle gates in Magnifica the story seems to lose its grip on reality. I suppose that is forgivable, as Annie herself loses her grip on consciousness. Once outside the castle walls again, the story seems to get back on track. However, when Annie sneaks into the enemy camp and struggles with The Apothecary, the style of writing seems to change, and the story begins to read like a movie, with no thought or feeling evident--just action.

I thought Annie's two pet cats must actually be Kinderstalk, but I was wrong about that, although they were sent by the Kinderstalk to protect her. What threw me off was the section early on when one of her cats disappeared, and "in her place stood a Kinderstalk." Also, there were a couple of plot holes that annoyed me. First, once it was revealed that Uncle Jock and Aunt Prim were no relation to Annie and her family, I could not understand the connection between the two families. The tenuous relationship between Aunt Prim and Annie's mother ("Was she your friend?" "I guess so") doesn't seem to be significant enough for the expense of keeping Annie and Page safe in their home, and Prim doesn't seem to have enough control over Jock to bend him to her will. Second, unless I misunderstood, Phoebe Tamburlaine was taken by the Kinderstalk from her home in Dour County, where Uncle Jock and Aunt Prim lived. When Phoebe was raised as Page, first by Shar and Helen and then by Jock and Prim, why did no one recognize Page as Phoebe? Prim knew about Phoebe's disappearance from "a farm close to town," and she was described as "all white and gold" which sounds just like Page's appearance. I suppose drinking the witch's potion changed her enough that she no longer looked like Phoebe, but from their descriptions this is not clear.

I also had trouble understanding Bea and Serena's position. For a little while I even suspected them of not being as they appeared, but if this is true, it never came up. They remained good and helpful and kind. I understand the presence of the little clockwork man made by Serena, as its heart ended up replacing the king's; but I don't understand why, as she held the little man, Annie felt fear and Serena looked at her oddly. This scene was a big part of the reason I didn't trust Serena and Bea, and it was never explained to my satisfaction.

The story was left wide open for a sequel, if only because Annie was unable to find Gregor, and because she did not fulfill the prophecy and "devour the witch." These are loose ends which I am sure will be tied up in future novels.

Wednesday, October 14, 2009

"The Magician's Elephant" by Kate DiCamillo

This book caught my eye because of the interesting title and cover art, but seeing the author's name sealed the deal. I read her book The Tale of Despereaux a couple of years ago and thought it was so cute and sweet, and then when I saw that it was being made into a movie I re-read it, this time to my kids. (When I finally got a chance to see the movie I was actually somewhat disappointed in it, but that's another story for another time). This one looked like another perfect bedtime story book for the kids.

The Magician's Elephant has the same sweet and dreamy quality as "Despereaux", and it was a nice little story, but I wish I had borrowed it from the library instead of buying a copy. It's not one of those books I feel like I HAVe to own. And honestly, when you get to the end of the book and look back, you find that not much happened. I feel like I could sum up the entire story in two sentences. It may have made a better picture book than a novel. But perhaps DiCamillo "intended only lilies," as the magician claimed, and that is what this book is--though a bundle of sweet white calla lilies, not a bouquet of flashy and bright stargazers.

I have flipped through another of DiCamillo's books, The Miraculous Journey of Edward Tulane, several times with the thought of buying it, but for one reason or another have always decided against it. The cover is cute (a bunny in pajamas walking upright down a street at night, casting a long shadow) but after reading The Magician's Elephant I'm pretty sure I'll just look for "Edward Tulane" at the library instead of buying it.

Tuesday, October 13, 2009

"Princess Academy" by Shannon Hale

I have had my eye on books by this author for some time (she also wrote The Goose Girl, among other interesting-looking titles), but I have never seen fit to actually borrow one of them from the library until now. I think I originally intended to use her books for story time with my kids at night and we always had something else to read, but this week I gave up on that notion and decided to read it for myself.

I really like the author's style of writing. It is sweetly old-fashioned (in a good way). Do I contradict myself if I also say that it is timeless? Even though this book was published in 2005, it has the patina of an age-old fairy tale. Some of the new children's books have a sort of jarring quality to them, even if they are enjoyable, but this book avoids that pitfall. I slipped into it like a comfortable old fuzzy bath robe with matching slippers.

At times as I read I tried to decide what country Danland was modeled after. The mountains where Mount Eskel was situated made me think of Switzerland, but names like Peder (and their tradition with surnames) sounded more like Sweden.

I loved reading about the sweet relationship that develops between Miri and her childhood friend Peder. I was impressed with the character development throughout the book--even most of the minor characters seemed to have multiple facets rather than being two-dimensional. The Britta/Prince Steffan resolution seemed a little bit contrived in order to make a happy ending, and the bandit attack almost sounded like it was thrown in at the insistence of an editor hoping to add some action and excitement, but those are minor complaints as even these contributed to a most satisfying story that ended in the best way it could have. For once, I totally agree with a quote on the back of a book, this one reading, "Enchanting... In layer upon layer of detail a beautiful coming-of-age story emerges." I have only high praise for Hale's skill in crafting a story, and I am looking forward to reading more of her books.