Instead of doing a cover reveal, today, for Alex Cavanaugh's new book, CassaStorm (due out this fall), I thought I'd review the second book in his trilogy seeing as how I just finished reading it. As it turns out that's going to be a bit harder than I thought it would be. Harder because I just didn't enjoy CassaFire
the way I did CassaStar (follow the link to the review).
The main reason is the time jump. I've decided that I just don't tend to like stories with huge leaps ahead in time. Like in The Dark Knight Rises. Of course, I realize that I was nearly alone in my lesser opinion of that movie, so maybe this is not a thing that bothers other people. However, it does bother me, and I had a difficult time reconciling myself to the fact that 'Fire was supposed to be nearly 20 years after 'Star. The character didn't seem any different. It was like he just stepped ahead 20 years into his future and was still wrestling with the same issues. At no point did I feel like I was reading about the cares and concerns of a 40-year-old man. He still felt like the same 20-year-old from the first book. If the story had been set, say, two years later, I don't think I would have had many of the issues that I did.
To make that issue worse, Byron seems to have not advanced in his career at all in the 20 year interim. We know that he planned to quit being a fighter pilot at the end of the first book, but, here, 20 years later, he's just flying a shuttle, and I had a hard time buying into that even if it was by choice. Again, I could see that after two years, but 20 years later was really stretching my suspension of disbelief.
There are some other issues with details about the world setting that niggled at me a lot, too, but I can't really go into most of those without the risk of giving things away, but I will say this one thing: Where are the rest of the Tgren people? They entire race seems to be totally existent within the one city of Ktren. A whole planet, but all of them live in this one city? Maybe, that's not how it is, but that is how it's presented, and it just... bothered me. In some respects, it reminded me of episodes of Star Trek or Stargate because of that, and that works in a 40 minute TV episode, but I kept waiting for some mention of the rest of the people and, other than the Bshen (who seem to be another race entirely), it never came.
In the end, I think I was looking for another 20,000 words or so to fill out the story some. I do realize that the focus of the story is Byron and his relationships, especially with the new woman in his life, and that was well done, but it felt too much as if it was being acted out upon a cardboard stage rather than a real 3-D environment.
That said, I may feel differently about this book once the next one comes out as it seems it is going to build on what was done in CassaFire. If, in retrospect, 'Fire serves as a good building block for what happens in 'Storm, I could end up with more positive feelings about it despite the sparseness of the background.
Oh, and I wouldn't be me if I didn't mention the editing. The editing in 'Fire wasn't quite as good as the editing in 'Star, and there were some repetitive errors that bugged me, which distracted me from the story. Some missing words here and there, repeated lines of text a couple of times, and misspellings. Mostly things that other people won't notice, since other people seem to have not noticed them, but there were enough this time around that it's worth noting. That said, in comparison to a lot of other things I've read, even novels published through big, traditional publishers (>cough< Snow Crash), it was pretty clean. [I mean, in Snow Crash, it was like he sneezed commas, and they just left them on the page wherever they landed.]
So, in the final analysis, I really like CassaStar. It's a good read, kind of a buddy space opera kind of book. It deals with the bonds of friendship and how important they can be. CassaFire is okay. If you really like 'Star, it's worth giving it a look, at least. It's a romance, and the romance is pretty well handled. There are themes of friendship, also, but, really, it's about the girl. Looking forward, CassaStorm has an intriguing plot and, just from the summary, a lot of world details that haven't been revealed before. I'm intrigued, so I will certainly go on to the next one. It's possible that 'Storm could make 'Fire completely worthwhile. I guess I'll find out this fall.
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 Dark Knight Rises. Show all posts
Showing posts with label Dark Knight Rises. Show all posts
Thursday, February 21, 2013
Monday, December 17, 2012
An Expected Self-Indulgence
The more I heard about The Hobbit in the lead up to its release the more trepidatious I became. The Lord of the Rings, overall, is an excellent adaptation of the book. They're great movies, but they are also great adaptations. Mostly. Except for the few places where Peter Jackson got all self-indulgent and added stuff in just because he liked it better that way. Like the elves at Helm's Deep, which still just makes my ears steam. To hear him say in an interview that he added them in there because he just wanted there to be more elves because he loves elves so much just makes me want to smack him, because what he did completely undermines Tolkien's purpose for that battle.
And let's just not even talk about King Kong, because that was three hours of the most self-indulgent crap ever.
At any rate, the more I heard about what Jackson was doing with The Hobbit, the more I worried that that was what he was doing, making a completely self-indulgent movie. But my wife kept telling me to give him the benefit of the doubt because he'd done such a good job with LotR. >sigh< It turned out I was correct. Jackson needs three movies for his version of The Hobbit because it is exactly that: his version. And his version is not a better a version. In many places, it destroys what Tolkien did just so that Jackson could shove The Hobbit into his version of Middle Earth. [And now I know why the Tolkien family has restricted Jackson from any more of Tolkien's material than he already has access to (meaning he was only allowed what was in The Hobbit and LotR and denied everything else).]
The biggest problem, though, was that, while watching the movie, it was amazing. I mean, it really was amazing! But I couldn't get immersed in it, not completely, because the back of my head kept poking at me, saying, "But it's wrong!" And the problem with that is the farther away from actually watching the movie I get, the more the wrong parts bother me. So, although I enjoyed it while I was actually watching it (most of it, anyway -- the part with domino trees was just DUMB (and took me back to the swinging dinosaurs in Kong, which was also DUMB)), the more I think about it, talk about it, read about it, the more upset about it I get and the less I like it. Which will not keep me from seeing the others and, probably, owning all of them. And that bothers me, too!
And speaking of reading about it, my first impression upon walking out of the movie was that people who have not read the books would probably find more to like in the movie, because they wouldn't have the feeling of wrongness about it that I have. However, the more reviews I look at from people that have no other exposure to Tolkien than the movies (and some that haven't even seen LotR), the more I'm finding that people that don't already like Tolkien don't like this movie. So... if you haven't read Tolkien, you won't like this movie. If you have read Tolkien... well, you might like it if you read Tolkien a long time ago and aren't really "into" it, but if you are really into Middle Earth, I'm not seeing how you can really like what Jackson's done to it.
My sons are good examples of this. My younger son is most upset about the lack of the songs, because they are mostly excluded. And he hates the inclusion of the pale orc. As does my older son. (As do I.) They both have complaints about the movie that are at war with the fact that they enjoyed watching the movie. You shouldn't come out of a movie feeling both "I loved it!" and "I hated it!" You just shouldn't. The short of that is that we are all conflicted about it. Everyone except my daughter, I suppose, because she hasn't read any Tolkien, yet, but, because she lives in a Tolkien-ish environment, she has a predilection toward it.
Or, maybe, people who are really into LotR but not The Hobbit, people that read the trilogy because of the movies but never bothered with Hobbit, will really like it, because Jackson really did everything he could to make this (series of) movie(s) as epic in scope as LotR. But, see, that's not what The Hobbit is, so the movie is continuing to just bother me.
In fact, Jackson just mapped Hobbit onto his LotR template, so it's wrong from the very beginning: the prologue. It worked in Fellowship, because there is so much back story in LotR that the prologue gave us a sense of history that lead up to the events in the trilogy, but it fails completely in An Unexpected Journey. For one thing, Bilbo doesn't all that stuff before he goes off on his journey; he finds out as he goes along, so we lose the sense of discovery that Bilbo had, because Jackson just lays it all out for us at the beginning. I squirmed in my seat during that part, but I was still reserving judgment. By the end of the movie, though, I was annoyed with it.
I was annoyed with it because Jackson uses that bit of prologue to introduce Thorin's non-existent nemesis. Non-existent in the book, I mean. This piece of plot that has been woven in is the biggest weakness of the film. I say that because every member of my family (except my daughter) came out of the movie hating the pale orc. Not necessarily for the same reason, but we all hated him being in the movie. He is so NOT needed.
But, see, the prologue is not the only way we see Jackson trying to harmonize the movies. The fight with the goblins and the Great Goblin is just like the flight through Moria with the falling stairs and all of that with the Great Goblin subbing in as the Balrog. Bilbo puts the ring on for the first time in the very same way that Frodo does. The elves come in and rescue the dwarves from a fight that doesn't even exist in the book. The stone giants... oh, well, I don't know where the heck that crap came from, but it was dumb. Having them would have been great, but having the party end up climbing around on them was ludicrous. And since when were they actually made from stone? Did I say self-indulgent? Oh, yeah, I think I did.
Having said all of that, the movie was still beautiful and wondrous to behold. The acting was... well, Martin Freeman was ohmygosh awesome. And it's a good thing, too, because Jackson gave much of Gandalf's role in the story to Bilbo in order to increase Bilbo's importance at an earlier stage in the story. (Bah!) Richard Armitage (whom I loved in BBC's Robin Hood) was dashing as Thorin and completely not what I expected but in a good way as opposed to the rest of the movie. Dwalin and Kili are the only two other dwarves that get large enough roles to actually comment on beyond the fact that they are there and they are dwarves, and both of them do just fine. If you've seen the other movies, the rest is as should be expected. Oh, the scene with Gollum was excellent in that Andy Serkis was, again, incredible.
Of course, there's Radagast... Sylvester McCoy (a previous Doctor, so I'm pre-disposed toward him already) did a great job with the part he was given; I'm just not quite sure how I feel about that part. On the one hand, I really liked it; on the other, really? Really? That's what Jackson came up with? He had the opportunity to bring Radagast, a character hardly mentioned in any of the books, to life for the first time, and that's what he came up with? Seriously? He had freaking bird poop running down his face! Of course, he had a sleigh pulled by rabbits, too, which was really cool.
I think the real problem with the whole thing is that Jackson didn't have anyone standing next to him during all of this to say, "What the heck? Is that seriously what you're doing there?"
And before anyone starts comparing this with Lucas and the prequels, there is a huge difference: Star Wars belongs to Lucas. He wasn't screwing around with something that belonged to someone else. Middle Earth and The Hobbit don't belong to Jackson, so all the screwing around he did is rather disrespectful to the source material.
Oh, and speaking of Star Wars, there were parts where I felt like I was watching that instead. The Great Goblin was so much Jabba the Hutt. And, actually, the part where the Pale Orc is demanding Thorin's head made me feel like I was at Jabba's court. And, then, there was the line by Galadriel, "The riddle of the morgul blade..." >sigh<
My general reaction to An Unexpected Journey has been much the same as my reaction to The Dark Knight Rises: I enjoyed it while I was watching it, but the more time I have to think about it the more it gets under my skin. Like a thorn. And I'm just picking at it and picking at it trying to get it out but succeeding only in working it deeper. And there are two more of these movies to go! But I really want to see Smaug!
Let's just not talk about the moose, okay. We're gonna try to forget about that altogether.
Now I want to go watch "A Room with a Moose" from Invader Zim, the only place we should have a moose, I'm sure.
And let's just not even talk about King Kong, because that was three hours of the most self-indulgent crap ever.
At any rate, the more I heard about what Jackson was doing with The Hobbit, the more I worried that that was what he was doing, making a completely self-indulgent movie. But my wife kept telling me to give him the benefit of the doubt because he'd done such a good job with LotR. >sigh< It turned out I was correct. Jackson needs three movies for his version of The Hobbit because it is exactly that: his version. And his version is not a better a version. In many places, it destroys what Tolkien did just so that Jackson could shove The Hobbit into his version of Middle Earth. [And now I know why the Tolkien family has restricted Jackson from any more of Tolkien's material than he already has access to (meaning he was only allowed what was in The Hobbit and LotR and denied everything else).]
The biggest problem, though, was that, while watching the movie, it was amazing. I mean, it really was amazing! But I couldn't get immersed in it, not completely, because the back of my head kept poking at me, saying, "But it's wrong!" And the problem with that is the farther away from actually watching the movie I get, the more the wrong parts bother me. So, although I enjoyed it while I was actually watching it (most of it, anyway -- the part with domino trees was just DUMB (and took me back to the swinging dinosaurs in Kong, which was also DUMB)), the more I think about it, talk about it, read about it, the more upset about it I get and the less I like it. Which will not keep me from seeing the others and, probably, owning all of them. And that bothers me, too!
And speaking of reading about it, my first impression upon walking out of the movie was that people who have not read the books would probably find more to like in the movie, because they wouldn't have the feeling of wrongness about it that I have. However, the more reviews I look at from people that have no other exposure to Tolkien than the movies (and some that haven't even seen LotR), the more I'm finding that people that don't already like Tolkien don't like this movie. So... if you haven't read Tolkien, you won't like this movie. If you have read Tolkien... well, you might like it if you read Tolkien a long time ago and aren't really "into" it, but if you are really into Middle Earth, I'm not seeing how you can really like what Jackson's done to it.
My sons are good examples of this. My younger son is most upset about the lack of the songs, because they are mostly excluded. And he hates the inclusion of the pale orc. As does my older son. (As do I.) They both have complaints about the movie that are at war with the fact that they enjoyed watching the movie. You shouldn't come out of a movie feeling both "I loved it!" and "I hated it!" You just shouldn't. The short of that is that we are all conflicted about it. Everyone except my daughter, I suppose, because she hasn't read any Tolkien, yet, but, because she lives in a Tolkien-ish environment, she has a predilection toward it.
Or, maybe, people who are really into LotR but not The Hobbit, people that read the trilogy because of the movies but never bothered with Hobbit, will really like it, because Jackson really did everything he could to make this (series of) movie(s) as epic in scope as LotR. But, see, that's not what The Hobbit is, so the movie is continuing to just bother me.
In fact, Jackson just mapped Hobbit onto his LotR template, so it's wrong from the very beginning: the prologue. It worked in Fellowship, because there is so much back story in LotR that the prologue gave us a sense of history that lead up to the events in the trilogy, but it fails completely in An Unexpected Journey. For one thing, Bilbo doesn't all that stuff before he goes off on his journey; he finds out as he goes along, so we lose the sense of discovery that Bilbo had, because Jackson just lays it all out for us at the beginning. I squirmed in my seat during that part, but I was still reserving judgment. By the end of the movie, though, I was annoyed with it.
I was annoyed with it because Jackson uses that bit of prologue to introduce Thorin's non-existent nemesis. Non-existent in the book, I mean. This piece of plot that has been woven in is the biggest weakness of the film. I say that because every member of my family (except my daughter) came out of the movie hating the pale orc. Not necessarily for the same reason, but we all hated him being in the movie. He is so NOT needed.
But, see, the prologue is not the only way we see Jackson trying to harmonize the movies. The fight with the goblins and the Great Goblin is just like the flight through Moria with the falling stairs and all of that with the Great Goblin subbing in as the Balrog. Bilbo puts the ring on for the first time in the very same way that Frodo does. The elves come in and rescue the dwarves from a fight that doesn't even exist in the book. The stone giants... oh, well, I don't know where the heck that crap came from, but it was dumb. Having them would have been great, but having the party end up climbing around on them was ludicrous. And since when were they actually made from stone? Did I say self-indulgent? Oh, yeah, I think I did.
Having said all of that, the movie was still beautiful and wondrous to behold. The acting was... well, Martin Freeman was ohmygosh awesome. And it's a good thing, too, because Jackson gave much of Gandalf's role in the story to Bilbo in order to increase Bilbo's importance at an earlier stage in the story. (Bah!) Richard Armitage (whom I loved in BBC's Robin Hood) was dashing as Thorin and completely not what I expected but in a good way as opposed to the rest of the movie. Dwalin and Kili are the only two other dwarves that get large enough roles to actually comment on beyond the fact that they are there and they are dwarves, and both of them do just fine. If you've seen the other movies, the rest is as should be expected. Oh, the scene with Gollum was excellent in that Andy Serkis was, again, incredible.
Of course, there's Radagast... Sylvester McCoy (a previous Doctor, so I'm pre-disposed toward him already) did a great job with the part he was given; I'm just not quite sure how I feel about that part. On the one hand, I really liked it; on the other, really? Really? That's what Jackson came up with? He had the opportunity to bring Radagast, a character hardly mentioned in any of the books, to life for the first time, and that's what he came up with? Seriously? He had freaking bird poop running down his face! Of course, he had a sleigh pulled by rabbits, too, which was really cool.
I think the real problem with the whole thing is that Jackson didn't have anyone standing next to him during all of this to say, "What the heck? Is that seriously what you're doing there?"
And before anyone starts comparing this with Lucas and the prequels, there is a huge difference: Star Wars belongs to Lucas. He wasn't screwing around with something that belonged to someone else. Middle Earth and The Hobbit don't belong to Jackson, so all the screwing around he did is rather disrespectful to the source material.
Oh, and speaking of Star Wars, there were parts where I felt like I was watching that instead. The Great Goblin was so much Jabba the Hutt. And, actually, the part where the Pale Orc is demanding Thorin's head made me feel like I was at Jabba's court. And, then, there was the line by Galadriel, "The riddle of the morgul blade..." >sigh<
My general reaction to An Unexpected Journey has been much the same as my reaction to The Dark Knight Rises: I enjoyed it while I was watching it, but the more time I have to think about it the more it gets under my skin. Like a thorn. And I'm just picking at it and picking at it trying to get it out but succeeding only in working it deeper. And there are two more of these movies to go! But I really want to see Smaug!
Let's just not talk about the moose, okay. We're gonna try to forget about that altogether.
Now I want to go watch "A Room with a Moose" from Invader Zim, the only place we should have a moose, I'm sure.
Labels:
Dark Knight Rises,
doctor,
Gandalf,
George Lucas,
Hobbit,
Invader Zim,
King Kong,
Lord of the Rings,
Martin Freeman,
Middle Earth,
Peter Jackson,
Richard Armitage,
Robin Hood,
Star Wars,
Sylvester McCoy,
Tolkien
Wednesday, July 25, 2012
Nolan Again Impresses...
...with his ability to obfuscate.
I do realize that I'm going to be in the vast minority with my stance on The Dark Knight Rises, but I'm used to that, so I'm just going to go with it.
I have one thing to say for Christopher Nolan: he's a magician when it comes to making movies. I mean that in a very literal sense. He uses flashy action to distract us from the holes he leaves behind in the story. We can't see them, because we're too busy looking in the other direction.
Or maybe it's just that Marvel has set the bar so high with their string of excellent adaptions that I'm just no longer satisfied with interpretations. Maybe if it was more explicit that these are interpretations, I'd be happier. DC/Warner Brothers could just slap their Elseworlds label on these things, and I might be more accepting of them. As it is, though, there are so many things that aren't Batman in these movies that I have a hard time dealing with it. Like in Burton's Batman when Alfred brings Vicki Vale down into the Batcave. What?
Unfortunately, Nolan has plenty of those moments himself. Like in Batman Begins when Wayne allows Lucius Fox to know that he's Batman. Whereas that was almost acceptable in that movie, those inconsistencies with the source material have continued to snowball to the point that by the time we get to Rises, I can't accept them. I mean, by the end of The Dark Knight Rises half of everyone knows that Wayne is Batman. And we're just supposed to believe that some random cop walks up to Wayne and just knows? Seriously. I get that Nolan needs that for his story, but, give me a break, he knew because he saw it in Wayne's face? At least Tim Drake did the research to figure out that Wayne is Batman. And I don't want to give spoilers, but having his actual name be Robin? It just makes me cringe.
However, the big issue for me, the thing that set the big disconnect for me, is that we're supposed to believe that this is 8 years later. That Bruce Wayne just quit being Batman and went into seclusion. I get that Nolan is trying to give us a sense of Miller's Dark Knight comics in which Batman had quit and was in seclusion, but that was because he got old. He even gives us a cane like Wayne uses in Batman Beyond, but, again, in those he got old; Nolan wants us to believe that Wayne just quit. I can't buy it. I absolutely can not buy it.
This is where I understand the difference between me, someone that grew up reading Batman comics and was heavily invested in Batman lore for...well, longer than I should have been, and the vast majority of people out there that don't have that same investment. These details aren't important to them. I get that. I also get that I am not really the target audience for the movie. I was the target audience for Batman Begins, because that one was more focused on the fans of the comic, but these last two, after hooking everyone in, have been focused on the general consumer.
Even so, the idea with Nolan's Batman is that he is set in the "real world," and, as such, I still can not accept this 8 year hiatus. He wants us to buy into too many unrealistic ideas:
1. After 8 years of no Batman, people are still talking about him. Give me a break. Culturally, we barely hold onto anything for 8 days, and Nolan expects us to believe that people are still saying, after 8 years, "is he coming back?" Not to mention the fact that he has kids, like 10-year-old kids, talking about Batman as if he's a reality to them. Or was a reality to them. Yes, all of this bothers me, because none of it's how the real world works.
If he'd made it a year after the events of Dark Knight, maybe even two, it would have been plausible.
2. There's a Harvey Dent Day and people care about it. See point 1. No one would care after 8 years. Well, they wouldn't care beyond the fact that it was a day off from work. And it's not clear that they, the common people, do get a day off from work.
3. After 8 years, Wayne just puts the suit back on, and it's like he never quit. There are so many problems with this:
If Nolan wants us to believe that this is a Batman that could be in the real world, he needs to keep him in the real world. And don't get me started on the "fusion bomb," because all of that was just bad science. I'll buy into Wayne creating a fusion reactor, but not turning it into a "time bomb" in the way it was done in the movie. They're equating it to a meltdown in a nuclear reactor, and those things just don't happen on a schedule. Not to mention the last minute save after 5 months. It just doesn't get more cliche than that.
Nolan also uses sleight-of-hand to hide facts from us. I don't have an issue with this in a general sense, but it takes away from the enjoyment of watching it again. He did this very successfully in The Prestige, because, in that one, he gave us the clues to figure out what was going on so that when the reveal happened it was your own fault for not figuring it out. I like that kind of cleverness, and doing it that way does make for good repeat viewing, because you can go back and see where the clues were that you missed (like in The Sixth Sense). I dislike, though, when not only is the information hidden but the fact that there is information hidden is hidden. Of course, then, when you do see that coming because you have more lore than the average viewer, there's no surprise, so that twist didn't throw me at all, and that made the viewing experience... less than it could have been.
Having said all of that, don't take it that I'm saying that it's a bad movie. It's not. It's a good movie, and I'm glad I saw it in the theater. The acting is good (Oldman is still great as Gordon, Hathaway was good, Gordon-Levitt is quite good), and the action and fight sequences are spectacular. But the movie, if you look beyond those things, is not great.
Here's the way I look at it:
After I saw The Avengers, I wanted, immediately, to see it again. After seeing it the second time (opening weekend), I wanted to go back and see it again. I still want to see it again. I have no desire to see Rises again.
I had the same experience with The Dark Knight when it came out alongside Iron Man. I saw Iron Man three times in the first week and still would have gone back to see it. I could barely sit through my second viewing of The Dark Knight because I got bored even though I'd been on the edge of my seat during my first viewing. After 4 years, I barely want to re-watch Dark Knight and that desire is only related to the release of Rises (in fact, I have not seen Dark Knight again since I saw it last in the theater even though I own the movie). I've seen Iron Man numerous times in the intervening years and talking about it makes me want to go put that one in right now. That, to me, is what makes a movie great, the desire to watch it over and over again. I just don't get that from Nolan.
I've said that I'm not in favor of re-boots, and I'm not, but I would certainly be in favor of a Batman re-boot. As long it's more in line with the comics. I really don't want someone coming along and trying to continue on from the point where Nolan left things. Of course, that's part of why Nolan left things the way he did (by his own admission).
I'd say that maybe I'm just getting crotchety in my old age, but that's just not it. In truth, I've always been like this. Even in high school, my friends would be upset because I'd point out inconsistencies in movies. I'd enjoy them just fine anyway, but, then, I'd pop their bubbles of the movies by pointing out the flaws, and they would lose enjoyment of them. So... I like Rises. It was a good movie, certainly big enough to be worth seeing in the theater. It just wasn't great, and it wasn't great because it lacked in the story department. Anyway, I'm not trying to make anyone else not like the movie, but I would like to peel back the whitewash of "greatness" that has been slapped onto it so that people can see past the action smokescreen.
[And, remember! I have a contest going on! Check out yesterday's post for details.]
I do realize that I'm going to be in the vast minority with my stance on The Dark Knight Rises, but I'm used to that, so I'm just going to go with it.
I have one thing to say for Christopher Nolan: he's a magician when it comes to making movies. I mean that in a very literal sense. He uses flashy action to distract us from the holes he leaves behind in the story. We can't see them, because we're too busy looking in the other direction.
Or maybe it's just that Marvel has set the bar so high with their string of excellent adaptions that I'm just no longer satisfied with interpretations. Maybe if it was more explicit that these are interpretations, I'd be happier. DC/Warner Brothers could just slap their Elseworlds label on these things, and I might be more accepting of them. As it is, though, there are so many things that aren't Batman in these movies that I have a hard time dealing with it. Like in Burton's Batman when Alfred brings Vicki Vale down into the Batcave. What?
Unfortunately, Nolan has plenty of those moments himself. Like in Batman Begins when Wayne allows Lucius Fox to know that he's Batman. Whereas that was almost acceptable in that movie, those inconsistencies with the source material have continued to snowball to the point that by the time we get to Rises, I can't accept them. I mean, by the end of The Dark Knight Rises half of everyone knows that Wayne is Batman. And we're just supposed to believe that some random cop walks up to Wayne and just knows? Seriously. I get that Nolan needs that for his story, but, give me a break, he knew because he saw it in Wayne's face? At least Tim Drake did the research to figure out that Wayne is Batman. And I don't want to give spoilers, but having his actual name be Robin? It just makes me cringe.
However, the big issue for me, the thing that set the big disconnect for me, is that we're supposed to believe that this is 8 years later. That Bruce Wayne just quit being Batman and went into seclusion. I get that Nolan is trying to give us a sense of Miller's Dark Knight comics in which Batman had quit and was in seclusion, but that was because he got old. He even gives us a cane like Wayne uses in Batman Beyond, but, again, in those he got old; Nolan wants us to believe that Wayne just quit. I can't buy it. I absolutely can not buy it.
This is where I understand the difference between me, someone that grew up reading Batman comics and was heavily invested in Batman lore for...well, longer than I should have been, and the vast majority of people out there that don't have that same investment. These details aren't important to them. I get that. I also get that I am not really the target audience for the movie. I was the target audience for Batman Begins, because that one was more focused on the fans of the comic, but these last two, after hooking everyone in, have been focused on the general consumer.
Even so, the idea with Nolan's Batman is that he is set in the "real world," and, as such, I still can not accept this 8 year hiatus. He wants us to buy into too many unrealistic ideas:
1. After 8 years of no Batman, people are still talking about him. Give me a break. Culturally, we barely hold onto anything for 8 days, and Nolan expects us to believe that people are still saying, after 8 years, "is he coming back?" Not to mention the fact that he has kids, like 10-year-old kids, talking about Batman as if he's a reality to them. Or was a reality to them. Yes, all of this bothers me, because none of it's how the real world works.
If he'd made it a year after the events of Dark Knight, maybe even two, it would have been plausible.
2. There's a Harvey Dent Day and people care about it. See point 1. No one would care after 8 years. Well, they wouldn't care beyond the fact that it was a day off from work. And it's not clear that they, the common people, do get a day off from work.
3. After 8 years, Wayne just puts the suit back on, and it's like he never quit. There are so many problems with this:
- There is an implication, a strong implication, that Wayne has been doing nothing to "stay in shape" during his seclusion (except, maybe, shooting some arrows). He's just been sulking about. Bodies deteriorate pretty quickly. After just a few months, he would have lost his edge and begun losing muscle mass. After a year, it would have taken considerable training to be able to get back into shape. After 8 years?
- Aside from the staying in shape aspect of it, Wayne has definitely not been sparring or doing any kind of combat training in those 8 years. As an example of what not sparring can do, you can look at the Foreman/Ali championship fight. Foreman was unable to spar for the entire month leading up to the bout due to an eye injury, and just that one month of not training threw his fighting off so much that he couldn't compete. (Ali won and refused to ever allow Foreman a re-match.)
- On top of all the not staying in shape and not sparring, Wayne has suffered some sort of debilitating injury that has caused him to need a cane to walk. His body is in bad shape. No, it's in horrible shape. So... 8 years of lounging in seclusion and he can't even walk under his own power, but we're supposed to believe that a high tech knee brace returns him to fighting form? Are you kidding me?
If Nolan wants us to believe that this is a Batman that could be in the real world, he needs to keep him in the real world. And don't get me started on the "fusion bomb," because all of that was just bad science. I'll buy into Wayne creating a fusion reactor, but not turning it into a "time bomb" in the way it was done in the movie. They're equating it to a meltdown in a nuclear reactor, and those things just don't happen on a schedule. Not to mention the last minute save after 5 months. It just doesn't get more cliche than that.
Nolan also uses sleight-of-hand to hide facts from us. I don't have an issue with this in a general sense, but it takes away from the enjoyment of watching it again. He did this very successfully in The Prestige, because, in that one, he gave us the clues to figure out what was going on so that when the reveal happened it was your own fault for not figuring it out. I like that kind of cleverness, and doing it that way does make for good repeat viewing, because you can go back and see where the clues were that you missed (like in The Sixth Sense). I dislike, though, when not only is the information hidden but the fact that there is information hidden is hidden. Of course, then, when you do see that coming because you have more lore than the average viewer, there's no surprise, so that twist didn't throw me at all, and that made the viewing experience... less than it could have been.
Having said all of that, don't take it that I'm saying that it's a bad movie. It's not. It's a good movie, and I'm glad I saw it in the theater. The acting is good (Oldman is still great as Gordon, Hathaway was good, Gordon-Levitt is quite good), and the action and fight sequences are spectacular. But the movie, if you look beyond those things, is not great.
Here's the way I look at it:
After I saw The Avengers, I wanted, immediately, to see it again. After seeing it the second time (opening weekend), I wanted to go back and see it again. I still want to see it again. I have no desire to see Rises again.
I had the same experience with The Dark Knight when it came out alongside Iron Man. I saw Iron Man three times in the first week and still would have gone back to see it. I could barely sit through my second viewing of The Dark Knight because I got bored even though I'd been on the edge of my seat during my first viewing. After 4 years, I barely want to re-watch Dark Knight and that desire is only related to the release of Rises (in fact, I have not seen Dark Knight again since I saw it last in the theater even though I own the movie). I've seen Iron Man numerous times in the intervening years and talking about it makes me want to go put that one in right now. That, to me, is what makes a movie great, the desire to watch it over and over again. I just don't get that from Nolan.
I've said that I'm not in favor of re-boots, and I'm not, but I would certainly be in favor of a Batman re-boot. As long it's more in line with the comics. I really don't want someone coming along and trying to continue on from the point where Nolan left things. Of course, that's part of why Nolan left things the way he did (by his own admission).
I'd say that maybe I'm just getting crotchety in my old age, but that's just not it. In truth, I've always been like this. Even in high school, my friends would be upset because I'd point out inconsistencies in movies. I'd enjoy them just fine anyway, but, then, I'd pop their bubbles of the movies by pointing out the flaws, and they would lose enjoyment of them. So... I like Rises. It was a good movie, certainly big enough to be worth seeing in the theater. It just wasn't great, and it wasn't great because it lacked in the story department. Anyway, I'm not trying to make anyone else not like the movie, but I would like to peel back the whitewash of "greatness" that has been slapped onto it so that people can see past the action smokescreen.
[And, remember! I have a contest going on! Check out yesterday's post for details.]
Labels:
Anne Hathaway,
Avengers,
Batman,
Christopher Nolan,
Dark Knight Rises,
DC,
Elseworlds,
Frank Miller,
Gary Oldman,
George Foreman,
Gordon-Levitt,
Iron Man,
Marvel,
Muhammad Ali,
Sixth Sense,
Warner Brothers
Subscribe to:
Comments (Atom)