I would be happier if the producers of the James Bond movies could make up their minds about whether they're doing continuing story lines or not, but I suppose that's not something that has specifically to do with this movie. But even without that, I find Spectre to be much more difficult to make a decision about as to whether I liked it or not. But, see, that's not exactly true, either, because I quite enjoyed watching the movie. Most of the movie.
Okay, I can't do this without spoilers, so be warned.
In a general sense, having Spectre be a direct sequel to Skyfall worked really well. In the specific sense of the antagonist being Bond's "brother," it was kind of a disaster. Seriously, we're supposed to believe that this kid who didn't like the fact that his father took in young Bond after the death of James' parents killed his father and grew up to become the leader of a massive, secret terrorist organization all to more effectively torture James. And kill all of Bond's girlfriends. Yeah, that just doesn't fly. It more like hobbles around on the ground and you just want Christoph Waltz to die.
Speaking of Waltz, I'm a bit tired of him. He might be fine in this movie if I hadn't seen him play the same character in about half a dozen movies at this point, but I have seen him continuously play the same character -- the sort of crazy, kooky, villain -- in film after film, and it's grown tiresome. Maybe some other actor could have gotten me to buy into the villain being Bond's long-thought-dead foster brother, but not Waltz.
Still, it is a Craig Bond movie, and it's highly enjoyable. The action is great, and Daniel Craig still puts on a very believable James Bond. I'm still very much liking Ralph Fiennes as M, and Ben Whishaw is great as Q. Andrew Scott even puts in an admirable performance as C, though it was difficult not to expect him to be a bad guy after his go as Moriarty in Sherlock. He just has that feel. Also, I do really like Naomie Harris as Moneypenny. Lea Seydoux is fine as Swann, which I only say because it doesn't seem that she did anything with the role that a dozen (or more) other actresses couldn't have done.
So... the bottom line:
Spectre is quite worth seeing in the theater, especially if you're a Bond fan. It's also essential viewing for the Bond fan, since this one continues to delve into Bond's backstory. Aside from Waltz and the whole "brother" thing, it's a really good movie. Great action, good acting, stunning visuals. Despite Waltz, I'm sure I'll be buying it on disc as soon as it's released. If you're not a Bond fan or if you're not familiar with the Bond movies, this is not the movie for you. It's certainly not a good place to start if you haven't seen any other Bond films. I do hope, though, that they move away from exploring Bond's childhood soon. I mean, why is it, after all, that we have to make orphans of all of our heroes?
About writing. And reading. And being published. Or not published. On working on being published. Tangents into the pop culture world to come. Especially about movies. And comic books. And movies from comic books.
Showing posts with label James Bond. Show all posts
Showing posts with label James Bond. Show all posts
Monday, December 7, 2015
Spectre (a movie review post)
Labels:
Andrew Scott,
Ben Whishaw,
Christoph Waltz,
Daniel Craig,
girlfriend,
James Bond,
Lea Seydoux,
M,
Moneypenny,
movie review,
Naomie Harris,
Q,
Ralph Fiennes,
Sherlock,
Skyfall,
Spectre
Sunday, April 21, 2013
How To Be... a Super Spy!
This is where it all started. This whole series came out of this idea of what it takes to be a super spy, and it was my wife's idea to use this as my series (she said to make sure she gets the credit for giving me the idea that gave me my idea). You might be wondering why we would be trying to figure out what it takes to be a spy, but, really, it's no secret. We think our daughter would be a great spy. She has so many of the basic personality traits one would need: naturally athletic, a drive "to win," an innate desire to make sure other people do what's "right" while being willing to manipulate events to get what she wants. I could go on. And I will in just a moment but more in general rather than about her specifically.
Let me just make it clear: these are the things you need in order to be super spy like James Bond or Jason Bourne or Sydney Bristow, not just a regular spy. The requirements to be a regular spy are much less and more varied depending upon the kind of spy you want to be. Or are willing to settle on being. I'm just going to assume that everyone wants to be a super spy, so that's what we'll look at.
So... how do you go about being a super spy?
1. A super spy needs to be kinesthetically gifted. While it's possible to learn the physical skills one would need without any natural inclination, it makes it much more difficult. A great spy will be able to learn physical disciplines easily.
2. A super spy needs to have a sort of moral ambiguity about them. Which is not to say that they need to not believe in anything, they might have a very heightened sense of right and wrong (or, at least, what they believe to be right and wrong), but they need to be willing to do what needs to be done for the greater good.
3. A super spy needs to have a facility with languages. This is probably the toughest one (and the one my daughter is missing). A regular spy may or may not know any other languages but probably doesn't know more than three or four. A super spy needs to be able to go anywhere and do anything and be able to understand what's going on around her. Minimally, she needs to at least understand the language when it's being spoken even if she can't speak it back. Information is currency for the spy, and language is the root of that currency.
4. A super spy needs to have strong interpersonal and social skills. The spy needs to be able to blend in with the crowd and appear to belong in any group. The spy also needs to be able to manipulate her target. This doesn't come about by being shy. The spy has to be able to win people over, make them trust her, do her bidding. It's not really the career choice for people that don't like to interact with strangers. If that's you, maybe you'd be better as an analyst. Not that you can't be a regular spy and be an introvert, especially if it's part of your cover, but you'll never make it as a super spy if you can't put yourself out there.
5. A super spy has to be smart. Not just smart, either; a super spy has to be able think quickly and take decisive action. Often within moments. Or seconds. Immediately. Sometimes, it doesn't even have to be the correct action, but no action at all, stopping to think about it, will get you killed.
There are tons of other things, but they're specific skills that apply to these basic concepts. Like a super spy should know Arabic. Or a super spy should know how to sky dive. Or a super spy must be proficient with handguns. Basically, there are a lot of individual things to learn, too many to list, but the individual skills are not as important as the underlying ability to learn and use them.
For free, because I found it interesting, one site I looked at said (and I have no idea if this is based on any actual data or just pulled from some guy's butt) that only about 10% of the population is born with the necessary characteristics to become a true super spy.
Let me just make it clear: these are the things you need in order to be super spy like James Bond or Jason Bourne or Sydney Bristow, not just a regular spy. The requirements to be a regular spy are much less and more varied depending upon the kind of spy you want to be. Or are willing to settle on being. I'm just going to assume that everyone wants to be a super spy, so that's what we'll look at.
So... how do you go about being a super spy?
1. A super spy needs to be kinesthetically gifted. While it's possible to learn the physical skills one would need without any natural inclination, it makes it much more difficult. A great spy will be able to learn physical disciplines easily.
2. A super spy needs to have a sort of moral ambiguity about them. Which is not to say that they need to not believe in anything, they might have a very heightened sense of right and wrong (or, at least, what they believe to be right and wrong), but they need to be willing to do what needs to be done for the greater good.
3. A super spy needs to have a facility with languages. This is probably the toughest one (and the one my daughter is missing). A regular spy may or may not know any other languages but probably doesn't know more than three or four. A super spy needs to be able to go anywhere and do anything and be able to understand what's going on around her. Minimally, she needs to at least understand the language when it's being spoken even if she can't speak it back. Information is currency for the spy, and language is the root of that currency.
4. A super spy needs to have strong interpersonal and social skills. The spy needs to be able to blend in with the crowd and appear to belong in any group. The spy also needs to be able to manipulate her target. This doesn't come about by being shy. The spy has to be able to win people over, make them trust her, do her bidding. It's not really the career choice for people that don't like to interact with strangers. If that's you, maybe you'd be better as an analyst. Not that you can't be a regular spy and be an introvert, especially if it's part of your cover, but you'll never make it as a super spy if you can't put yourself out there.
5. A super spy has to be smart. Not just smart, either; a super spy has to be able think quickly and take decisive action. Often within moments. Or seconds. Immediately. Sometimes, it doesn't even have to be the correct action, but no action at all, stopping to think about it, will get you killed.
There are tons of other things, but they're specific skills that apply to these basic concepts. Like a super spy should know Arabic. Or a super spy should know how to sky dive. Or a super spy must be proficient with handguns. Basically, there are a lot of individual things to learn, too many to list, but the individual skills are not as important as the underlying ability to learn and use them.
For free, because I found it interesting, one site I looked at said (and I have no idea if this is based on any actual data or just pulled from some guy's butt) that only about 10% of the population is born with the necessary characteristics to become a true super spy.
Thursday, April 18, 2013
How To Be... Q
So you want to be Q?
Well, unfortunately, you need to be born in the Q Continuum. Sorry. It's just not gonna work out for you.
Oh, wait!
You meant this Q
Well, that requires that you join the British Secret Service. Maybe. And being able to make nifty spy gadgets.
Oh, no, wait! That's not right, either...
How To Be... a Quantum Mechanic
Okay, so there's really no such thing as a "quantum mechanic." Yet.
However, with quantum communication on the horizon (possibly closer than you think), and quantum computers in development (the first one has already been built), and the possibility of all of this leading to artificial intelligence and robots and warp drive (also in development and has been done on a small scale), I can't think of a better name for the guy that has to come around and fix your tech when it breaks down. I imagine, at first, at least, that this will take a lot more schooling than a trade school.
My advice? Take as much quantum physics as you can. The next generation of technology is coming. It can't hurt to be prepared.
Well, unfortunately, you need to be born in the Q Continuum. Sorry. It's just not gonna work out for you.
Oh, wait!
You meant this Q
Well, that requires that you join the British Secret Service. Maybe. And being able to make nifty spy gadgets.
Oh, no, wait! That's not right, either...
How To Be... a Quantum Mechanic
Okay, so there's really no such thing as a "quantum mechanic." Yet.
However, with quantum communication on the horizon (possibly closer than you think), and quantum computers in development (the first one has already been built), and the possibility of all of this leading to artificial intelligence and robots and warp drive (also in development and has been done on a small scale), I can't think of a better name for the guy that has to come around and fix your tech when it breaks down. I imagine, at first, at least, that this will take a lot more schooling than a trade school.
My advice? Take as much quantum physics as you can. The next generation of technology is coming. It can't hurt to be prepared.
Sunday, November 11, 2012
Skyfall -- Just a Name
On the surface, Skyfall is a really excellent movie.That's because it's a really excellent movie. If you take it as an individual movie and forget that James Bond already exists. That includes forgetting the previous two Daniel Craig Bond films. As an individual movie, it really only has one flaw: its title. The title is a lie and has nothing to do with the movie at all.
Yeah, yeah, I hear those of you out there that have already seen it saying, "But..." (and I'm not finishing that sentence, because I'm avoiding the spoiler). It seems pretty obvious to me that the title was arrived at completely separately from the movie. Something like:
"Wouldn't Skyfall be a cool title?"
"Sure, but it has nothing to do with the movie."
"Well, can't we work it in somehow?"
So, yeah, the "word" was just thrown into the movie so that it could be used as a title and has absolutely no meaning whatsoever. I felt a little bit cheated by that. But not really enough for it to take away from the movie experience overall. It's sort of like the pricker you get in your finger while picking blackberries; it's annoying, but it's not gonna keep you from enjoying the cobbler.
So for the movie itself:
The action was great. There was only one bit that I thought really strained plausibility (it had to do with a subway train), so that was pretty good. But, then, these new Bond films have been better at "keeping it real" than some of the older ones.
The acting was great. Daniel Craig is a great Bond, and, of course, Judi Dench is just great. Ralph Fiennes is also in this one, and he was surprisingly good. I say "surprisingly" because, while he can be great, he is not always great, and this seemed like the kind of role where he was more expected to look good rather than be good, but he was quite good, and I'm glad that his character is one that will (should) be returning.
The tech... well... there's a lot of computer stuff in this, hacking and all sorts of things like that, and, mostly, that was okay, but...
Well, I went to see this with my friend that works for... um, Lucasfilm? Well, right now, he works for Lucasfilm; I suppose they will keep that name even once Disney takes over in January, because that's how they do it, so, yeah, I went to the Lucasfilm premiere of the movie with my buddy that works there. Well, two buddies, now, because one of our mutual friends now works there with him. I think he's trying to recruit everyone he knows into working there, and I want to know when it gets to be my turn, but I suppose they don't really need any writers. That's not his department anyway.
But I digress...
So I was there with my friend, and there's this scene where Q is explaining some computer something-or-other with a lot of technobabble, and my friend just starts laughing. Not LOLing or anything, just a sustained chuckle. So I know whatever he was going on about was gibberish, because my friend does the whole computer thing. I'm fairly technologically challenged (just ask my wife (also notice that I still have that same, stupid generic blogger wallpaper for my blog)), so I probably wouldn't have noticed if he hadn't been laughing; I mean, I don't know what they're going on about either way. Well, except for the part where I just sort of assume that it's all meaningless technobabble anyway.
However, as much as I enjoyed it as an individual movie, I was more than a little let down with the movie in terms of its relationship to the other Bond films. There are two main reasons for this:
1. With Casino Royale and the re-boot of the Bond franchise, they created an ongoing story line. Quantum of Solace, while not the greatest Bond film as an individual movie, was an excellent continuation of that story. It felt like they were putting things in place for something really cool, and I was intrigued by where they were going. With Skyfall, though, they just drop that whole story line and, at the moment, have no plans to go back to it. This is incredibly disappointing, and, for that reason, despite how good Skyfall is on its own, it is, itself, also disappointing.
2. Skyfall feels like even more of a re-boot than Casino. There is a grasp in this one to make this Bond the definitive Bond. The Bond. An attempt to sweep away all earlier versions, while still giving a nod to them, and actually make this 007 James Bond. I can't be more explicit than that without giving spoilers, but I just want to say that I wasn't entirely happy with this aspect of the movie in relation to the other Bond movies. Casino did a fine job of updating the franchise and setting up a new sequence of movies. There was no need to go even further back and attempt to shove all the other movies aside.
But, still, all by itself, Skyfall is well worth seeing.
Just ignore that the time frame of the opening events doesn't quite match up, and all should be well. Maybe, I shouldn't have pointed that out, though.
NOTE:
Remember that Friday, this Friday, Nov. 16, is the Oh, How I Miss You blogfest hosted by myself, Alex Cavanaugh, and Matthew McNish. If you haven't already signed up, follow one of the links and get over there and do it! Let's let some people know that we've noticed their absence. It's always good to know you're missed!
Yeah, yeah, I hear those of you out there that have already seen it saying, "But..." (and I'm not finishing that sentence, because I'm avoiding the spoiler). It seems pretty obvious to me that the title was arrived at completely separately from the movie. Something like:
"Wouldn't Skyfall be a cool title?"
"Sure, but it has nothing to do with the movie."
"Well, can't we work it in somehow?"
So, yeah, the "word" was just thrown into the movie so that it could be used as a title and has absolutely no meaning whatsoever. I felt a little bit cheated by that. But not really enough for it to take away from the movie experience overall. It's sort of like the pricker you get in your finger while picking blackberries; it's annoying, but it's not gonna keep you from enjoying the cobbler.
So for the movie itself:
The action was great. There was only one bit that I thought really strained plausibility (it had to do with a subway train), so that was pretty good. But, then, these new Bond films have been better at "keeping it real" than some of the older ones.
The acting was great. Daniel Craig is a great Bond, and, of course, Judi Dench is just great. Ralph Fiennes is also in this one, and he was surprisingly good. I say "surprisingly" because, while he can be great, he is not always great, and this seemed like the kind of role where he was more expected to look good rather than be good, but he was quite good, and I'm glad that his character is one that will (should) be returning.
The tech... well... there's a lot of computer stuff in this, hacking and all sorts of things like that, and, mostly, that was okay, but...
Well, I went to see this with my friend that works for... um, Lucasfilm? Well, right now, he works for Lucasfilm; I suppose they will keep that name even once Disney takes over in January, because that's how they do it, so, yeah, I went to the Lucasfilm premiere of the movie with my buddy that works there. Well, two buddies, now, because one of our mutual friends now works there with him. I think he's trying to recruit everyone he knows into working there, and I want to know when it gets to be my turn, but I suppose they don't really need any writers. That's not his department anyway.
But I digress...
So I was there with my friend, and there's this scene where Q is explaining some computer something-or-other with a lot of technobabble, and my friend just starts laughing. Not LOLing or anything, just a sustained chuckle. So I know whatever he was going on about was gibberish, because my friend does the whole computer thing. I'm fairly technologically challenged (just ask my wife (also notice that I still have that same, stupid generic blogger wallpaper for my blog)), so I probably wouldn't have noticed if he hadn't been laughing; I mean, I don't know what they're going on about either way. Well, except for the part where I just sort of assume that it's all meaningless technobabble anyway.
However, as much as I enjoyed it as an individual movie, I was more than a little let down with the movie in terms of its relationship to the other Bond films. There are two main reasons for this:
1. With Casino Royale and the re-boot of the Bond franchise, they created an ongoing story line. Quantum of Solace, while not the greatest Bond film as an individual movie, was an excellent continuation of that story. It felt like they were putting things in place for something really cool, and I was intrigued by where they were going. With Skyfall, though, they just drop that whole story line and, at the moment, have no plans to go back to it. This is incredibly disappointing, and, for that reason, despite how good Skyfall is on its own, it is, itself, also disappointing.
2. Skyfall feels like even more of a re-boot than Casino. There is a grasp in this one to make this Bond the definitive Bond. The Bond. An attempt to sweep away all earlier versions, while still giving a nod to them, and actually make this 007 James Bond. I can't be more explicit than that without giving spoilers, but I just want to say that I wasn't entirely happy with this aspect of the movie in relation to the other Bond movies. Casino did a fine job of updating the franchise and setting up a new sequence of movies. There was no need to go even further back and attempt to shove all the other movies aside.
But, still, all by itself, Skyfall is well worth seeing.
Just ignore that the time frame of the opening events doesn't quite match up, and all should be well. Maybe, I shouldn't have pointed that out, though.
NOTE:
Remember that Friday, this Friday, Nov. 16, is the Oh, How I Miss You blogfest hosted by myself, Alex Cavanaugh, and Matthew McNish. If you haven't already signed up, follow one of the links and get over there and do it! Let's let some people know that we've noticed their absence. It's always good to know you're missed!
Wednesday, February 8, 2012
Wherein I Review My Own Book
As part of the celebration of The House on the Corner being one year old this week, I've decided to give my book the review treatment. As much as possible, I'm going to approach my book as if it was someone else's book. However, because that's not really possible, I'm going to give you tidbits of information about different aspects of it as I go. Sort of a "how someone else might see it vs. why I did it that way" kind of thing. Also, I hope to show that I can be harsh with my own work, too.
Not that I really think I'm that harsh, but any time you don't tell someone you absolutely love what they've written, you tend to come off as harsh. In fact, if you have a preference for some earlier piece of work someone did over whatever it is s/he's currently working on, you come off as harsh. Anyway... all of that to say that this review business is tricky, so I understand why people decide to (A) not do them at all (B) only give fabulous reviews and 5 stars no matter the quality of the work. However, and I've said this before, I strongly believe in the need for reviews, especially for new authors, so I feel I need to do my part in supporting that by giving them. [Hopefully, that will work its way back around to me some day (although, so far, no such luck (which is not to say that I haven't had any reviews, but... oh, never mind)).] I also don't feel like I can be dishonest (especially with myself) by proclaiming the greatness of something that I didn't think was great. And saying a book was good when you don't really believe it doesn't help anyone, but I've already talked about that (although, I don't remember which post that was), and I digress...
I'm going to start with the grade, this time, rather than working toward it as I normally do. The House on the Corner is in the B+ to A- range. And, yes, this grade is a struggle for me. House is not A+ work. I mean, just this morning while reading in one of the classes I read in, I found a typo (chapter 14), so I haven't worked all of the bugs out of it, yet. However, on the technical merits, House is at least an A. Overall, there are very few "bugs" that still need to be worked out. Although, on this read through, I have noticed a tendency to over use the word "though," which I'm finding annoying. [So much so that I've been trying to pay attention to my actual speech to see if I use it that much when I'm talking or if it's only a writing thing.] However, in comparison to most self-published books (and some (many) professionally edited and traditionally published works) I have far fewer "oopsies" than are generally floating around out there. I think I've done a really nice job on that even if I do tend to use more commas than are strictly necessary (they are still correct, even though most people wouldn't use them (I have a whole post on commas coming up at some point in the future, too, so, really, you don't want to miss that!)).
I don't think a lot of books deserve the A+, and I don't really expect that I will ever write one. Not that I won't try. House is not it, though. So what holds it back?
It's long. Not War and Peace long, but it's long for a "kids' book." I will say, though, that the kids don't seem to have an issue with this. But, aside from being long, it has a slow start. This is a huge barrier to a lot of people. I think people that love books like The Lord of the Rings won't have an issue with the slow start, but, as amazing as it may seem, most people don't love The Lord of the Rings (even if it is considered the most significant work of fiction of the 20th century). Most people have not and will not ever read it. Why? It's too long, and it starts too slowly. If you make it through childhood and haven't read it, it's unlikely that, as an adult, you will ever read it. I'm sure there's a study out there somewhere about that. [Of course, 50% of people never read another book in their life once they finish school (and I know there are studies about that, because I've talked about that before (sorry, I don't remember which post that was, either)).]
Really, though, it's not the length that's the issue, it's the slow start. Of course, there are reasons I have the slow start. One reason is that I hate how the new conventions of "how things should be" in literature include leaving out the exposition and as much of the rising action as you can. Basically, it's all about jumping into the story as close as you can get to the climax and still have it be understandable. I hate that. Jumping into the middle of the action may seem fun and exciting, but it's really just bad story telling. I decided to not take part in bad story telling. I start at the point of conflict, the move, but it's not the middle of the action.
Another reason for the slow start, and, really, the larger reason, is that I wanted all the pieces in place for what I'll call the meta-story. The story beyond the story that's just in this one book. This is going to get a separate post, but one of the things I really hate (despise) in series fiction (and this happens a lot on TV) is when the author(s) throws something new into a story (episode) to satisfy a plot point that, really, we should have known about all along. It's contrived, and I find it annoying (and I really want to use stronger language, but I'm biting my tongue). I get that your (and I'll call it) micro-story has needs, but you should have thought of those needs ahead of time. Don't throw in a secret healing ability because you suddenly "need" it. Think of something else. Basically, if it's something we should have already known about, don't use it. Figure out a way to introduce it and make it part of the story for later use. I mean, this isn't Batman's utility belt we're talking here, and you don't have any good reason to suddenly whip out shark repellent. Other than the old, 60s Batman television series, about the only place this idea works in is James Bond movies, and it only works because the idea is that James Bond can use whatever he happens to have available to get out of the messes he's in. [You might notice, though, that the new Bond doesn't use the whole Q-effect.]
At any rate, I wanted to include as many of the elements from the meta-story as I could in this first micro-story so that it wouldn't seem like some cheap trick when they show up later. I don't want anyone to think, "Wait, why didn't we ever know about that before this?" So, when there are issues with the little stairway going to the side door, that will be important in the meta-story. The books? The books that seem to be so casually thrown in to no purpose: important in the meta-story. Even Dr. Atkinson, who may seem like an unimportant side character that could be dropped, important in the meta-story. These things, which draw out the length of this first book, will already be there when they are needed. This seems to me a more natural way of doing things... well, it will be more natural to the reader when they encounter them..., so I'm willing to make the story a bit longer than is strictly necessary to accommodate that, even if it means that it will fail to hook some readers.
The next drawback is the perspective. I chose an unusual way of telling the story, but it was a conscious choice. Even knowing that it might be difficult for some people, I chose it anyway. As with most things I do, there are multiple reasons:
1. The obvious reason: I have three kids. I was writing this book for them (which is not to say that I was not also writing it for the larger audience, but my primary concern was writing a book they would like. In doing so, I hoped to write a book that all kids would enjoy (and my experience (so far) has shown that to be pretty close to truth)). Because I was writing it for them, I decided to write it about them to a certain extent, so I decided I would give each character (Tom, Sam, and Ruth) their own perspective. This was actually the thing I was most worried about going into the book, that changing the POV between three 1st person perspectives would be too confusing for kids. Ironically, the only people who have struggled with the perspective shifts have been adults.
2. The not-so-obvious reason: The Pigman by Paul Zindel. I'm not sure if this book is really as obscure as it seems to be to me. I had to read it in middle school, and, evidently, it is still widely used in schools, but I've never ever heard mention of it again since then, so I think it must be a book that not many people have heard of. In a lot of ways, it is... unspectacular; however, it's one of the books I've thought back on frequently over the years. It probably deserves a spot on my "Of Significance..." page, and it may get one once I get the copy I just ordered and re-read it. It tells a story from two different 1st person perspectives, and I've never seen that done again since (not saying it hasn't been done since; I just haven't seen it). Until my book. It was the direct influence of The Pigman that lead to my decision to use 1st person for my three characters. I thought it would be interesting to see the story from three different sets of eyes, especially since there is occasional overlap in the story telling.
Some people have struggled with the change in perspective even though it changes by chapter, but, again, it seems to be only adults that have had issues with this. None of the kids I've dealt with around House have had any issue adapting to the changes and have figured them out almost instantly. Still, it's a barrier to some readers and drags my grade down because of it.
To sum all of that up, the first half of the book drags. [Although, I do have to say, it didn't drag for me until I was on my 5th or so read through, but, then, I prefer a slow build.] Nothing big is happening. Yes, they keep discovering new little things, but, other than squabbling amongst themselves, there's no obvious conflict happening. Well, there is the thing with the old man across the street, but that doesn't sustain itself. At any rate, action junkies will grow bored long before they get to "the good stuff." Despite the slow burn, though, I think the payout at the end is worth it.
Also, the perspective changes can be confusing. Yes, I've thought about label the perspective changes with the chapter titles, but, for some reason, I don't like that idea.
So... there's the bad, but what's good about the book?
The most obvious good is that it's set in the 80s. See, although my kids (and kids in general) are my target audience, I didn't want to write a book that was just targeted at kids. I wanted to write a book that parents could also relate to and enjoy. Part of doing that was a desire to evoke images of their own childhoods. Part of that is done through 80s pop culture, so that's a pretty narrow audience, just adults that are my age. But, hey, the 80s were fun (except for the nuclear fears), and I wanted to give my kids (and others) a bit of a taste of 80s culture, so that's where I set it. Hopefully, I have enough parent/child interaction to give all parents something to relate to, not just those of us that grew up in the 80s.
The real positive about House is that I don't follow many of the normal conventions for this kind of story. At least, I see that as a positive. One of the things my wife is always complaining about with fantasy literature (and this extends to Star Wars) is the orphan boy syndrome. [You can see this most recently in Harry Potter (and Percy Jackson).] You know, orphan boy discovers he has a previously unknown heritage (being a wizard or, um, the son of Darth Vader) and, often, is part of some prophecy and only he can defeat the ultimate evil (the ultimate evil that is usually the one responsible for the death of his parents). After coming to grips with the loss of his parents which has haunted him his whole life. This is the formula for fantasy story telling. I didn't want to do that (mostly because, if I did, my wife would ridicule me forever and ever and probably would never have read my book).
The other part of that is that the motivation for doing the right thing becomes about getting revenge, and I wanted a story about someone choosing to do the right thing for the mere sake that it is the right thing. Not because the protagonist is trying to avenge his parents' deaths or anything like that. I wanted characters that choose the right because it's the right. No other motivation than that. I think it's important that kids (especially) see that doing the right thing can be its own motivation. No revenge. No guilt. No ulterior motive. Not that there aren't struggles and mistakes, I want it to be real, but I also want the normal, average kid that lives in some sort of family to be able to identify with the kids. In other words, I wanted something closer to the Pevensies but with the parents involved in the story. I think this approach has resonated with the readers.
So...
The House on the Corner is well above average. It's not great, but it is quite good. I'm happy with quite good. It's good enough that, even though I wrote it, I'm still not tired of it or impatient with it while reading out loud in the classes I'm reading it in. I think I'm on something like my 7th time run through, too, not including my own readings of it, so it has some good staying power. I still come across things that make me laugh. Even though I wrote them. And even though I've repeated them over and over in these readings.
And there you have it. My (mostly) objective look at my own book. Sure, there are things that could be improved, but, overall, it's a lot better than the average book out there on the bookshelf. No, it's not Harry Potter. I'm not as clever or as witty as Rowling, but I do know how to tell a good story. And, honestly, I think any amount of slowness in this first one will be completely overlooked when I finish with Brother's Keeper. There's no set up involved in that one, and things are happening right from the start.
Not that I really think I'm that harsh, but any time you don't tell someone you absolutely love what they've written, you tend to come off as harsh. In fact, if you have a preference for some earlier piece of work someone did over whatever it is s/he's currently working on, you come off as harsh. Anyway... all of that to say that this review business is tricky, so I understand why people decide to (A) not do them at all (B) only give fabulous reviews and 5 stars no matter the quality of the work. However, and I've said this before, I strongly believe in the need for reviews, especially for new authors, so I feel I need to do my part in supporting that by giving them. [Hopefully, that will work its way back around to me some day (although, so far, no such luck (which is not to say that I haven't had any reviews, but... oh, never mind)).] I also don't feel like I can be dishonest (especially with myself) by proclaiming the greatness of something that I didn't think was great. And saying a book was good when you don't really believe it doesn't help anyone, but I've already talked about that (although, I don't remember which post that was), and I digress...
I'm going to start with the grade, this time, rather than working toward it as I normally do. The House on the Corner is in the B+ to A- range. And, yes, this grade is a struggle for me. House is not A+ work. I mean, just this morning while reading in one of the classes I read in, I found a typo (chapter 14), so I haven't worked all of the bugs out of it, yet. However, on the technical merits, House is at least an A. Overall, there are very few "bugs" that still need to be worked out. Although, on this read through, I have noticed a tendency to over use the word "though," which I'm finding annoying. [So much so that I've been trying to pay attention to my actual speech to see if I use it that much when I'm talking or if it's only a writing thing.] However, in comparison to most self-published books (and some (many) professionally edited and traditionally published works) I have far fewer "oopsies" than are generally floating around out there. I think I've done a really nice job on that even if I do tend to use more commas than are strictly necessary (they are still correct, even though most people wouldn't use them (I have a whole post on commas coming up at some point in the future, too, so, really, you don't want to miss that!)).
I don't think a lot of books deserve the A+, and I don't really expect that I will ever write one. Not that I won't try. House is not it, though. So what holds it back?
It's long. Not War and Peace long, but it's long for a "kids' book." I will say, though, that the kids don't seem to have an issue with this. But, aside from being long, it has a slow start. This is a huge barrier to a lot of people. I think people that love books like The Lord of the Rings won't have an issue with the slow start, but, as amazing as it may seem, most people don't love The Lord of the Rings (even if it is considered the most significant work of fiction of the 20th century). Most people have not and will not ever read it. Why? It's too long, and it starts too slowly. If you make it through childhood and haven't read it, it's unlikely that, as an adult, you will ever read it. I'm sure there's a study out there somewhere about that. [Of course, 50% of people never read another book in their life once they finish school (and I know there are studies about that, because I've talked about that before (sorry, I don't remember which post that was, either)).]
Really, though, it's not the length that's the issue, it's the slow start. Of course, there are reasons I have the slow start. One reason is that I hate how the new conventions of "how things should be" in literature include leaving out the exposition and as much of the rising action as you can. Basically, it's all about jumping into the story as close as you can get to the climax and still have it be understandable. I hate that. Jumping into the middle of the action may seem fun and exciting, but it's really just bad story telling. I decided to not take part in bad story telling. I start at the point of conflict, the move, but it's not the middle of the action.
Another reason for the slow start, and, really, the larger reason, is that I wanted all the pieces in place for what I'll call the meta-story. The story beyond the story that's just in this one book. This is going to get a separate post, but one of the things I really hate (despise) in series fiction (and this happens a lot on TV) is when the author(s) throws something new into a story (episode) to satisfy a plot point that, really, we should have known about all along. It's contrived, and I find it annoying (and I really want to use stronger language, but I'm biting my tongue). I get that your (and I'll call it) micro-story has needs, but you should have thought of those needs ahead of time. Don't throw in a secret healing ability because you suddenly "need" it. Think of something else. Basically, if it's something we should have already known about, don't use it. Figure out a way to introduce it and make it part of the story for later use. I mean, this isn't Batman's utility belt we're talking here, and you don't have any good reason to suddenly whip out shark repellent. Other than the old, 60s Batman television series, about the only place this idea works in is James Bond movies, and it only works because the idea is that James Bond can use whatever he happens to have available to get out of the messes he's in. [You might notice, though, that the new Bond doesn't use the whole Q-effect.]
At any rate, I wanted to include as many of the elements from the meta-story as I could in this first micro-story so that it wouldn't seem like some cheap trick when they show up later. I don't want anyone to think, "Wait, why didn't we ever know about that before this?" So, when there are issues with the little stairway going to the side door, that will be important in the meta-story. The books? The books that seem to be so casually thrown in to no purpose: important in the meta-story. Even Dr. Atkinson, who may seem like an unimportant side character that could be dropped, important in the meta-story. These things, which draw out the length of this first book, will already be there when they are needed. This seems to me a more natural way of doing things... well, it will be more natural to the reader when they encounter them..., so I'm willing to make the story a bit longer than is strictly necessary to accommodate that, even if it means that it will fail to hook some readers.
The next drawback is the perspective. I chose an unusual way of telling the story, but it was a conscious choice. Even knowing that it might be difficult for some people, I chose it anyway. As with most things I do, there are multiple reasons:
1. The obvious reason: I have three kids. I was writing this book for them (which is not to say that I was not also writing it for the larger audience, but my primary concern was writing a book they would like. In doing so, I hoped to write a book that all kids would enjoy (and my experience (so far) has shown that to be pretty close to truth)). Because I was writing it for them, I decided to write it about them to a certain extent, so I decided I would give each character (Tom, Sam, and Ruth) their own perspective. This was actually the thing I was most worried about going into the book, that changing the POV between three 1st person perspectives would be too confusing for kids. Ironically, the only people who have struggled with the perspective shifts have been adults.
2. The not-so-obvious reason: The Pigman by Paul Zindel. I'm not sure if this book is really as obscure as it seems to be to me. I had to read it in middle school, and, evidently, it is still widely used in schools, but I've never ever heard mention of it again since then, so I think it must be a book that not many people have heard of. In a lot of ways, it is... unspectacular; however, it's one of the books I've thought back on frequently over the years. It probably deserves a spot on my "Of Significance..." page, and it may get one once I get the copy I just ordered and re-read it. It tells a story from two different 1st person perspectives, and I've never seen that done again since (not saying it hasn't been done since; I just haven't seen it). Until my book. It was the direct influence of The Pigman that lead to my decision to use 1st person for my three characters. I thought it would be interesting to see the story from three different sets of eyes, especially since there is occasional overlap in the story telling.
Some people have struggled with the change in perspective even though it changes by chapter, but, again, it seems to be only adults that have had issues with this. None of the kids I've dealt with around House have had any issue adapting to the changes and have figured them out almost instantly. Still, it's a barrier to some readers and drags my grade down because of it.
To sum all of that up, the first half of the book drags. [Although, I do have to say, it didn't drag for me until I was on my 5th or so read through, but, then, I prefer a slow build.] Nothing big is happening. Yes, they keep discovering new little things, but, other than squabbling amongst themselves, there's no obvious conflict happening. Well, there is the thing with the old man across the street, but that doesn't sustain itself. At any rate, action junkies will grow bored long before they get to "the good stuff." Despite the slow burn, though, I think the payout at the end is worth it.
Also, the perspective changes can be confusing. Yes, I've thought about label the perspective changes with the chapter titles, but, for some reason, I don't like that idea.
So... there's the bad, but what's good about the book?
The most obvious good is that it's set in the 80s. See, although my kids (and kids in general) are my target audience, I didn't want to write a book that was just targeted at kids. I wanted to write a book that parents could also relate to and enjoy. Part of doing that was a desire to evoke images of their own childhoods. Part of that is done through 80s pop culture, so that's a pretty narrow audience, just adults that are my age. But, hey, the 80s were fun (except for the nuclear fears), and I wanted to give my kids (and others) a bit of a taste of 80s culture, so that's where I set it. Hopefully, I have enough parent/child interaction to give all parents something to relate to, not just those of us that grew up in the 80s.
The real positive about House is that I don't follow many of the normal conventions for this kind of story. At least, I see that as a positive. One of the things my wife is always complaining about with fantasy literature (and this extends to Star Wars) is the orphan boy syndrome. [You can see this most recently in Harry Potter (and Percy Jackson).] You know, orphan boy discovers he has a previously unknown heritage (being a wizard or, um, the son of Darth Vader) and, often, is part of some prophecy and only he can defeat the ultimate evil (the ultimate evil that is usually the one responsible for the death of his parents). After coming to grips with the loss of his parents which has haunted him his whole life. This is the formula for fantasy story telling. I didn't want to do that (mostly because, if I did, my wife would ridicule me forever and ever and probably would never have read my book).
The other part of that is that the motivation for doing the right thing becomes about getting revenge, and I wanted a story about someone choosing to do the right thing for the mere sake that it is the right thing. Not because the protagonist is trying to avenge his parents' deaths or anything like that. I wanted characters that choose the right because it's the right. No other motivation than that. I think it's important that kids (especially) see that doing the right thing can be its own motivation. No revenge. No guilt. No ulterior motive. Not that there aren't struggles and mistakes, I want it to be real, but I also want the normal, average kid that lives in some sort of family to be able to identify with the kids. In other words, I wanted something closer to the Pevensies but with the parents involved in the story. I think this approach has resonated with the readers.
So...
The House on the Corner is well above average. It's not great, but it is quite good. I'm happy with quite good. It's good enough that, even though I wrote it, I'm still not tired of it or impatient with it while reading out loud in the classes I'm reading it in. I think I'm on something like my 7th time run through, too, not including my own readings of it, so it has some good staying power. I still come across things that make me laugh. Even though I wrote them. And even though I've repeated them over and over in these readings.
And there you have it. My (mostly) objective look at my own book. Sure, there are things that could be improved, but, overall, it's a lot better than the average book out there on the bookshelf. No, it's not Harry Potter. I'm not as clever or as witty as Rowling, but I do know how to tell a good story. And, honestly, I think any amount of slowness in this first one will be completely overlooked when I finish with Brother's Keeper. There's no set up involved in that one, and things are happening right from the start.
Tuesday, January 31, 2012
A Game of Shadows & Stardust
Sherlock Holmes: A Game of Shadows
First, let me just say, I love the subtitle. I tend to be fond of subtitles, but A Game of Shadows is a great title or subtitle. I wish I'd thought of it. [Because, if I had, I might would use that for my Tib stories, which are still untitled.]
Second, I'm a big fan of Sherlock Holmes. I've read (and own) all of the Holmes stories, so, when I say I like Holmes, it's not just some vague notion of Holmes formed when I was a kid from watching movies and television shows about Sherlock.
Having said that, Guy Ritchie has done an excellent job of adapting the stories into movie format. There have, of course, been some changes (like with Sherlock's fastidiousness), but, overall, he kept all the fundamentals of Holmes and has made a faithful adaptation rather than just making some detective story and calling the character Sherlock as in many of the previous incarnations of Holmes.
Of course, the acting by Robert Downey, Jr. is superb. Looking at these movies through a James Bond lens, I would say that Downey is the Sean Connery of Sherlock Holmes. He's more rugged and less refined. More of a brawler than a fencer, which, actually, also holds true to the character; although, I'd be interested in seeing someone do a Roger Moore version who is more of the gentleman and fencer. This also falls within the realm of Holmes. Okay, so, maybe Pierce Brosnan for those of you out there hating on Roger (but I grew up with Moore Bond films, and I love them most). However, I can't actually think of anyone that would be better at Holmes than Downey has been.
Add Jude Law to that, and you have a pretty perfect team. I'm not a huge Jude Law fan. Not that I dislike him, but I think he often comes off the same from movie to movie. However, I think he's been the perfect pairing for Downey in these movies. Their combination is... well, they make an excellent team.
I've heard a lot of mutterings about how this one wasn't as good as the first, but I don't know that I can agree with that. Sure, they've removed the romantic element (and I was sorry to see Rachel McAdams go), but, really, the romantic element is not exactly appropriate as an ongoing thing in Sherlock Holmes. In almost all ways, Holmes is above romance. Adler was the only woman Holmes was ever interested in even remotely and that was because she bested him. They do add the tension of Watson's wife to the mix, and I think that serves adequately as a substitute for any romance for Holmes. His romance is with "the game."
Jared Harris was an excellent choice for Moriarty. He's not someone I would have thought of, but he was great. Quiet and under spoken, rather like a spider. He was quite chilling.
If you saw the first Holmes with Downey and liked it, this one is definitely worth seeing. For those of you that haven't read Sir Arthur Conan Doyle, be aware that many of the smaller details are actually from the stories and not just inventions for the movies. Those kinds of things being included made these movies a very enjoyable experience for me. If you haven't read Doyle, you should.
But don't spend a lot of time looking for Moriarty. He's really only in two of the stories and was an invention by Doyle to provide an adequate nemesis for Holmes in order to kill him off. Which he did. And, then, brought him back later because of public demand. See that thing with bowing to public pressure in writing goes back a long way.
Stardust
Stardust is another excellent title, but, then, Neil Gaiman tends to come up with some pretty excellent titles. Neverwhere and The Graveyard Book come to mind.
As I've stated previously, I've been a fan of Gaiman for quite a while. For much longer than he's been writing novels. I was introduced to The Sandman fairly early on (definitely before 1990) and often described Gaiman to friends as the best writer in comics (as opposed to Peter David (who also wrote novels) whom I described as the best writer of comic books writing novels)). I waited a long time for Gaiman to get around to the whole novel thing. And, then, sort of missed out on some because I was busy having kids. Good Omens is one of my favorite books, and I caught it right away, but Stardust and Neverwhere slipped past me, and I'm only now catching up.
But I loved the movie! Stardust is a beautiful movie, and I've been wanting to watch it again for quite a while (but it's buried in a box in the closet that still needs to be unpacked). Reading the book, finally, has only heightened that desire.
The problem here is that the movie and the book are not exactly the same thing. Rather like with Coraline. I really enjoyed reading Stardust, but I loved the movie. The book is less streamlined. It has a lot of fairy tale type elements in it, like people showing up to help at just the right moment. But, then, it is set in fairy land, so I'm sure those things are that way on purpose. They do add so amount of whimsy to the plot.
What I like most about the book is that it is unconventional in telling its love story, which is, also, unconventional. The movie makes it more of the kind of love story we expect from a movie, but the book, although containing the same love story, approaches it completely differently and doesn't really provide a happy ending. Not that it's not happy... well, you'd just have to read it to understand, because I'm not giving that away.
At any rate, if you like Gaiman, Stardust is definitely worth a read. I don't think it's as good as what he's been putting out more recently, but the same elements are there, and it's a good story with interesting characters. Be warned, though, if you're a fan of the movie, it's not quite the same.
First, let me just say, I love the subtitle. I tend to be fond of subtitles, but A Game of Shadows is a great title or subtitle. I wish I'd thought of it. [Because, if I had, I might would use that for my Tib stories, which are still untitled.]
Second, I'm a big fan of Sherlock Holmes. I've read (and own) all of the Holmes stories, so, when I say I like Holmes, it's not just some vague notion of Holmes formed when I was a kid from watching movies and television shows about Sherlock.
Having said that, Guy Ritchie has done an excellent job of adapting the stories into movie format. There have, of course, been some changes (like with Sherlock's fastidiousness), but, overall, he kept all the fundamentals of Holmes and has made a faithful adaptation rather than just making some detective story and calling the character Sherlock as in many of the previous incarnations of Holmes.
Of course, the acting by Robert Downey, Jr. is superb. Looking at these movies through a James Bond lens, I would say that Downey is the Sean Connery of Sherlock Holmes. He's more rugged and less refined. More of a brawler than a fencer, which, actually, also holds true to the character; although, I'd be interested in seeing someone do a Roger Moore version who is more of the gentleman and fencer. This also falls within the realm of Holmes. Okay, so, maybe Pierce Brosnan for those of you out there hating on Roger (but I grew up with Moore Bond films, and I love them most). However, I can't actually think of anyone that would be better at Holmes than Downey has been.
Add Jude Law to that, and you have a pretty perfect team. I'm not a huge Jude Law fan. Not that I dislike him, but I think he often comes off the same from movie to movie. However, I think he's been the perfect pairing for Downey in these movies. Their combination is... well, they make an excellent team.
I've heard a lot of mutterings about how this one wasn't as good as the first, but I don't know that I can agree with that. Sure, they've removed the romantic element (and I was sorry to see Rachel McAdams go), but, really, the romantic element is not exactly appropriate as an ongoing thing in Sherlock Holmes. In almost all ways, Holmes is above romance. Adler was the only woman Holmes was ever interested in even remotely and that was because she bested him. They do add the tension of Watson's wife to the mix, and I think that serves adequately as a substitute for any romance for Holmes. His romance is with "the game."
Jared Harris was an excellent choice for Moriarty. He's not someone I would have thought of, but he was great. Quiet and under spoken, rather like a spider. He was quite chilling.
If you saw the first Holmes with Downey and liked it, this one is definitely worth seeing. For those of you that haven't read Sir Arthur Conan Doyle, be aware that many of the smaller details are actually from the stories and not just inventions for the movies. Those kinds of things being included made these movies a very enjoyable experience for me. If you haven't read Doyle, you should.
But don't spend a lot of time looking for Moriarty. He's really only in two of the stories and was an invention by Doyle to provide an adequate nemesis for Holmes in order to kill him off. Which he did. And, then, brought him back later because of public demand. See that thing with bowing to public pressure in writing goes back a long way.
Stardust
Stardust is another excellent title, but, then, Neil Gaiman tends to come up with some pretty excellent titles. Neverwhere and The Graveyard Book come to mind.
As I've stated previously, I've been a fan of Gaiman for quite a while. For much longer than he's been writing novels. I was introduced to The Sandman fairly early on (definitely before 1990) and often described Gaiman to friends as the best writer in comics (as opposed to Peter David (who also wrote novels) whom I described as the best writer of comic books writing novels)). I waited a long time for Gaiman to get around to the whole novel thing. And, then, sort of missed out on some because I was busy having kids. Good Omens is one of my favorite books, and I caught it right away, but Stardust and Neverwhere slipped past me, and I'm only now catching up.
But I loved the movie! Stardust is a beautiful movie, and I've been wanting to watch it again for quite a while (but it's buried in a box in the closet that still needs to be unpacked). Reading the book, finally, has only heightened that desire.
The problem here is that the movie and the book are not exactly the same thing. Rather like with Coraline. I really enjoyed reading Stardust, but I loved the movie. The book is less streamlined. It has a lot of fairy tale type elements in it, like people showing up to help at just the right moment. But, then, it is set in fairy land, so I'm sure those things are that way on purpose. They do add so amount of whimsy to the plot.
What I like most about the book is that it is unconventional in telling its love story, which is, also, unconventional. The movie makes it more of the kind of love story we expect from a movie, but the book, although containing the same love story, approaches it completely differently and doesn't really provide a happy ending. Not that it's not happy... well, you'd just have to read it to understand, because I'm not giving that away.
At any rate, if you like Gaiman, Stardust is definitely worth a read. I don't think it's as good as what he's been putting out more recently, but the same elements are there, and it's a good story with interesting characters. Be warned, though, if you're a fan of the movie, it's not quite the same.
Monday, July 11, 2011
Pixar's Ironic Messenger
Pixar's newest release is slick. And when I say slick, I mean it's SLICK. In the same way that Lightning McQueen is speed, Cars 2 is slick. Shiny. Mint. The animation is... there are no actual words for what the animation is. Especially the animation on the racing locations. I sat there thinking, "I want to go there." Especially when they were racing in Italy, and, actually, I have no real desire to go to Italy, but those scenes... I would have just stepped into them if I could have.
Cars 2 embraces everything kids loved about Cars and focuses in on it and makes it Bigger. Better. Faster and more intense (to quote a famous director (well, he's not famous for being a director, but that's the phrase he's known for when directing (points for anyone that knows whom))). Throw in Michael Caine as Finn McMissle, the James Bond of the movie, and you have the perfect mix for the perfect spy spoof. And it is. If you can imagine a James Bond movie where he's accompanied by Johnny English (a Rowan Atkinson creation, if that gives you any idea). Actually, just see Cars 2, and you won't have to imagine it. Caine is suave and sophisticated while Larry the Cable Guy is, well, Mater.
In comparison to other Pixar movies, this one has been getting bad reviews. Which puts it on just about even footing with other movies. As a total aside, I find it extremely curious that the first movie that Pixar has released that attacks a particular group, in this case Big Oil, is the first of their movies to get any kind of negative reaction. In general, their movies have been about the human condition, and this one is, too, but Cars 2, specifically, makes the statement that Big Oil is bad. WALL-E has a similar theme, an environmental theme, but they don't target any particular group with that movie; they play it safe by equating their environmental message with said human condition -- humans need to "shape up" but not any specific ones. But, hey, I agree with them, Big Oil is bad. They are one of the big evils in the world, and, if Pixar wants to call them to the carpet, I'm good with that. I mean, when a Saudi prince starts talking about how they need to drive oils prices down so they can keep the US dependent on the Middle East for oil, you know something's wrong.
I'm not trying to say there's any kind of conspiracy against Cars 2 or Pixar by Big Oil, but I do find the negativity surrounding the movie to be, well, like I said, curious.
Moving past the oil thing, probably, the biggest "flaw" of the movie is its failure to meet audience expectations. Cars is about Lightning McQueen. He is the star of the movie. The trailers leading up to Cars 2 support our assumption and expectation that Lightning will, again, be the star of Cars 2. Pixar fails to prepare us for the reality, and the blame for that lies squarely with them. Or with Disney. With whoever prepared the trailers, but I'd find it hard to believe that Pixar didn't have some control over that. The truth is, though, is that Lightning is not the hero of the sequel. That distinction falls on Mater (If you doubt it, check to see who got top billing for the movie. Hint: it wasn't Owen Wilson). I think it's quite possible that adult audiences just couldn't come to grips with the comic relief from the first movie taking over in the spotlight in the second. Kids, though... well, kids love Mater, and I'm pretty sure it hasn't been an issue for them.
That's a failing I often see in reviews of movies for kids, the tendency to belittle them for no reason other than that they're for kids. Pixar, of course, has spoiled the wider audience by making their movies equally appealing to adults, so when they release a movie that is geared (no pun intended) more toward kids, adults get a little upset over it.
If Cars 2 does a have a failing, I'd say it's one of story telling. The big plot is the spy story with the message about big oil, but they needed something else to give it that emotional impact they're known for, so they tried to weave in a story about friendship and how we need to accept our friends for whom they are. Lightning is embarrassed of Mater. In fact, it is the early conflict over this that sends Mater off on his adventure. However, because the movie is focused on Mater, we never get the opportunity to make an emotional connection with Lightning over the issue, so there's no tug on our heart when we get to the pay off for that in the movie. Just an intellectual acknowledgment that, yes, we shouldn't try to make our friends be someone they're not. It's the failure of these two story lines to support each other that leaves the audience feeling that there could have been something more. Sort of like making one peanut butter sandwich and one jelly sandwich and leaving it to the audience to figure out what to do with them.
Having said that, I do feel the need to point out that this movie is still vastly superior to the average Hollywood offering. If this is the worst Pixar has to offer, and I'm not saying it is, because I actually enjoyed it a lot more than WALL-E, no one has any reason at all to complain. And it's worth saying: Big Oil is bad.
Cars 2 embraces everything kids loved about Cars and focuses in on it and makes it Bigger. Better. Faster and more intense (to quote a famous director (well, he's not famous for being a director, but that's the phrase he's known for when directing (points for anyone that knows whom))). Throw in Michael Caine as Finn McMissle, the James Bond of the movie, and you have the perfect mix for the perfect spy spoof. And it is. If you can imagine a James Bond movie where he's accompanied by Johnny English (a Rowan Atkinson creation, if that gives you any idea). Actually, just see Cars 2, and you won't have to imagine it. Caine is suave and sophisticated while Larry the Cable Guy is, well, Mater.
In comparison to other Pixar movies, this one has been getting bad reviews. Which puts it on just about even footing with other movies. As a total aside, I find it extremely curious that the first movie that Pixar has released that attacks a particular group, in this case Big Oil, is the first of their movies to get any kind of negative reaction. In general, their movies have been about the human condition, and this one is, too, but Cars 2, specifically, makes the statement that Big Oil is bad. WALL-E has a similar theme, an environmental theme, but they don't target any particular group with that movie; they play it safe by equating their environmental message with said human condition -- humans need to "shape up" but not any specific ones. But, hey, I agree with them, Big Oil is bad. They are one of the big evils in the world, and, if Pixar wants to call them to the carpet, I'm good with that. I mean, when a Saudi prince starts talking about how they need to drive oils prices down so they can keep the US dependent on the Middle East for oil, you know something's wrong.
I'm not trying to say there's any kind of conspiracy against Cars 2 or Pixar by Big Oil, but I do find the negativity surrounding the movie to be, well, like I said, curious.
Moving past the oil thing, probably, the biggest "flaw" of the movie is its failure to meet audience expectations. Cars is about Lightning McQueen. He is the star of the movie. The trailers leading up to Cars 2 support our assumption and expectation that Lightning will, again, be the star of Cars 2. Pixar fails to prepare us for the reality, and the blame for that lies squarely with them. Or with Disney. With whoever prepared the trailers, but I'd find it hard to believe that Pixar didn't have some control over that. The truth is, though, is that Lightning is not the hero of the sequel. That distinction falls on Mater (If you doubt it, check to see who got top billing for the movie. Hint: it wasn't Owen Wilson). I think it's quite possible that adult audiences just couldn't come to grips with the comic relief from the first movie taking over in the spotlight in the second. Kids, though... well, kids love Mater, and I'm pretty sure it hasn't been an issue for them.
That's a failing I often see in reviews of movies for kids, the tendency to belittle them for no reason other than that they're for kids. Pixar, of course, has spoiled the wider audience by making their movies equally appealing to adults, so when they release a movie that is geared (no pun intended) more toward kids, adults get a little upset over it.
If Cars 2 does a have a failing, I'd say it's one of story telling. The big plot is the spy story with the message about big oil, but they needed something else to give it that emotional impact they're known for, so they tried to weave in a story about friendship and how we need to accept our friends for whom they are. Lightning is embarrassed of Mater. In fact, it is the early conflict over this that sends Mater off on his adventure. However, because the movie is focused on Mater, we never get the opportunity to make an emotional connection with Lightning over the issue, so there's no tug on our heart when we get to the pay off for that in the movie. Just an intellectual acknowledgment that, yes, we shouldn't try to make our friends be someone they're not. It's the failure of these two story lines to support each other that leaves the audience feeling that there could have been something more. Sort of like making one peanut butter sandwich and one jelly sandwich and leaving it to the audience to figure out what to do with them.
Having said that, I do feel the need to point out that this movie is still vastly superior to the average Hollywood offering. If this is the worst Pixar has to offer, and I'm not saying it is, because I actually enjoyed it a lot more than WALL-E, no one has any reason at all to complain. And it's worth saying: Big Oil is bad.
Subscribe to:
Posts (Atom)