Captain Marvel (a movie review post)

 

MCU #21

You can see my original review of this movie here. 

For reasons I can't really fathom, Captain Marvel is one of the most disliked of the MCU movies. It has only a 45% audience rating on Rotten Tomatoes and not much better anywhere else. It's not that I don't understand that there are supposed reasons, but I don't get it. Captain Marvel is a wonderful movie, and Larson is excellent in the role.

That said, Captain Marvel is not a character I have much experience with in the comics. My experience of her was her in a coma because Rogue absorbed her powers and memories, and that's the way it was for much of my active comic reading experience. Monica Rambeau, on the other hand, a later Captain Marvel in the comics, I have much more experience with and that character just so happens to be introduced in this movie. Rambeau also appears in WandaVision, and we should be seeing more of her soon. I think it's pretty cool the way she is introduced in this movie.

I have no idea of the origin story for Captain Marvel in the comics, the past or the current origin, and I don't care one way or the other about the relation of this origin to what might or might not be in the comics. I got over clinging to the comic origin a long time ago. As I've said before, the MCU is its own beast and should be judged on its own merits.

And the merits of this movie are good. I love the 90s setting. The crash through the roof of the Blockbuster is classic. I love that the Skrull posing as Colson gets found out because Colson calls Fury while he's with the imposter and that you don't know ahead of time that that has happened. Okay, well, now you do, if you haven't seen it, but that's on you. You've had time. I love the flerken. And the Tesseract, what a little cube of mischief! Always getting around and powering people's weapons and engines and... superpowers. That things gets around! Of course, it is the space gem, so I guess it's appropriate.

There is one argument that could be made against the movie that is valid: It is a touch of retconning to toss Captain Marvel into the mix right in the middle of the whole Infinity saga. BUT! They wanted the cause to seem hopeless. Because it was hopeless. Thanos won. He beat the heroes. Hands down. There were two opportunities to have beaten him, the first ruined by Quill and the second because Thor didn't go for the head. If we had known going into all of that that Captain Marvel was still out there, the situation wouldn't have seemed quite hopeless. I'm reminded of the scene in Empire when ghostBen says, "That boy is our last hope." And we don't have a Yoda to say, "No, there is another." (Okay, there is the post-credit scene with Fury using the call device, but we don't know what that means, yet, right?) So putting us in the situation where there is no hope left and then introducing the character works well, I think. But I can see the argument there; I just don't agree with it.

Marvel is a really solid movie with powerful characters and performances. And, as I said in the previous review, I do think Larson and Law have great chemistry together, which makes their final confrontation very... satisfying. To say the least.
What a condescending ass.
Of course, that is the character that Jude Law plays best.

So let's get this one ranked. I say that knowing that people will disagree with my placement on this one, but, hey, this is my ranking and this how I feel about it.

1. Captain America: Civil War

2. The Avengers
3. Captain America: The First Avenger

4. Avengers: Infinity War

5. Spider-Man: Homecoming
6. Captain America: The Winter Soldier
7. Iron Man

8. Captain Marvel

9. Black Panther

10. Doctor Strange

11. Ant-Man

12. Thor: Ragnarok
13. Thor: The Dark World
14. Thor

15. Guardians of the Galaxy

16. Ant-Man and the Wasp

17. Avengers: Age of Ultron

18. Guardians of the Galaxy Vol. 2
19. Iron Man 3
20. Iron Man 2
21. Incredible Hulk (Edward Norton's ego could never be a shape-shifting Skrull. He's incapable of disguising that thing.)

CassaStorm (a book review post)

If you would like to see my review of CassaStar, go here.
If you would like to see my review of CassaFire, go here.

The first and most obvious thing to be said about CassaStorm is that it's an obvious effort by the author, Alex Cavanaugh, to expand the universe he established in the previous two books. We find out that Tgren does, indeed, have more than one city on it and even get a peek at the other races only hinted at previously. And the end provides an explanation for some of the things that haven't made the most sense in the series overall, like the significantly low populations of the races.

There are ways the explanation creates more questions, but that's okay. Leaving questions unanswered is not something I necessarily have a problem with.

'Storm also rounds out the relationship progression of the other two books. 'Star deals with friendship, 'Fire deals with romance, and 'Storm deals with parenthood. As with the other two books, Byron has to figure out how it's supposed to work. The only issue with this idea in 'Storm is how it contrasts to the other two books. Both of the other books deal with Byron and initial meetings (first with Bassa, then with Athee) and 'Storm, in many ways, follows that pattern. The problem is that his son, Bassan, is already 10, and there are parts where it's like Byron has no idea of how to interact with his son in the same way as with someone you are just meeting.

This is both a strength and a weakness in the book, because in actuality Byron doesn't have any idea who his son is. It's clear that he's one of those who father's from a distance, and he is, in fact, learning who his son is. The problem is that there don't seem to be any clearly established patterns in their relationship as is usually the case. Neither the son nor the father ever seem like they know what to expect from the other.

There are a few interesting wrinkles in this book, like the introduction of the Rogue, which I didn't see coming. That's a big positive for me, because most books fall into established patterns making it difficult for me to find books that aren't fairly predictable. Possibly, the biggest issue I had with 'Fire is that I knew what was going to happen throughout the book; nothing was surprising. However, with 'Storm, every time I thought I had what was going to happen figured out, there would be some new wrinkle. It made the book a worthwhile read just to figure out where he was going with the story.

Basically, if you read the previous two books and liked them, you should definitely read this one. I can't see how it could be a disappointment. It's even possible that this book could be read as a stand alone, because any background information needed is provided. Sure, the other two provide a bigger picture, but I don't think they're necessary.

Look, this isn't deep or philosophical. It's pretty straightforward space opera in a Star Trek kind of vein. It deals as much with relationships as it does with space battles, but that serves to strengthen the book in overall sense, not weaken it. Hmm... Still, if you want space battles, CassaStar is probably the book for you if you haven't already read it. Not that there aren't space battles in 'Storm, but it's, ultimately, a different kind of story.

The Wolverine and a Bowl of Pop Culture

Does everyone have a bowl? Yes, you have to bring your own; I just don't have enough. And a spoon, too. No chopsticks, because we don't want to leave them standing upright in our pop culture, right? It's bad luck. Evidently. Anyway, get your bowls and your spoons, and pour yourself a heaping bowl of pop culture. But no milk; Wolvie doesn't like it.

I wanted very badly to not want to go see The Wolverine in the theater. Why pay for another movie I was just going to be disappointed in, right? I mean, this year has been particularly good for disappointing movies. And that doesn't even take into account the other Wolverine movie, one of the worst super hero movies made so far (and all because of the ending). [It's amazing how a botched ending can ruin an otherwise decent movie.] But Wolverine has been in my top three favorite heroes since... oh, well, a long time, and Hugh Jackman just nails that role, so I couldn't convince myself to wait. I'm actually glad that I didn't; some times, it's good to go into something with, basically, no expectations.

As it turned out, The Wolverine was much better than I expected it to be, and I actually enjoyed most of it. It has its issues, but, at least, they weren't really bad story-telling issues. The story, amazingly enough, was pretty solid and managed to not go off the cliff that the origin movie did. Of course, the story is only "pretty solid" if you look at it within the context of the X-Men movies. This movie has nothing to do with the comics other than that they pull some familiar characters from the Wolverine mythos to use in the movie. If you were hoping for anything resembling an adaptation of the Frank Miller/Chris Claremont Wolverine mini-series from the early '80s, you're not going to find that here. Okay, you'll get something vaguely resembling it. Very vaguely. He does fight some Hand ninjas. Except their not called that. So we're back to that "vaguely" again.

The thing to know about The Wolverine is that it's not about what it's about it. Within the context of the X-Men movies, the story is here to bridge the gap between X-Men: The Last Stand and the forthcoming X-Men: Days of Future Past and deal with the ramifications of how Last Stand ended. Basically, it's to get Logan to let go of the death of Jean and his part in it. With that goal in mind, The Wolverine actually accomplished its purpose and in a way that made sense. The micro-plot of just this one movie wasn't too bad either, even if it did have more than its share of "what the heck?" moments.

Spoiler alert:
The biggest issue with the movie is the sleight-of-hand they play with Logan's healing power. The dying old guy wants Logan's ability, and the best the writers could come up with is that the old dude is going to "steal" it. Not duplicate it, steal it. Which sounds like they're going to do some kind of thing like when Rogue absorbs other mutants' powers, but, no, the old guy is just going to drill into Logan's bone marrow and transfer the power to himself, which doesn't make any sense, but I'll give it a pass on the handwavium principle. Except that they also "suppress" his healing power using a little "Matrix" bug that gets on Wolvie's heart, and they don't explain that, either, especially after making it seem as if this is some other mutant thing before we find out it's a device. Really, you can only get a pass on one of these things in the movie. The deal with the tiny robot is that they want Wolverine to rip his own heart out to get rid of the thing, so I can see that they're going for the "cool factor" with that, but, then, they don't show it, so they lose out on that, anyway. And it leaves all kinds of questions: does the little robot bug suppress all mutant abilities or just Logan's? Or just Logan's healing factor? It's hard to tell, because he really doesn't use any of his heightened senses in the movie at all, so we don't know if he still has those or not. Of course, there's also the argument that Logan's healing power should have just expelled the little robot bug to begin with, but the movie Wolverine isn't quite as powerful as the comic book Wolverine.

And neither is adamantium, evidently, because we again have a "bullet piercing adamantium" situation in that the old guy cuts off Wolverine's claws to get at his bone marrow. It's slightly more believable than the bullet being fired into Logan's head but not by much.

At any rate, those things are just issues with story points not the story itself, and we have to deal with those all the time. Like people surviving explosions by jumping into water or standing behind a wall or whatever. So, whereas there are some... stupid? silly? okay, stupid... things within the story, the plot of The Wolverine holds up both on the level of there being a villain intent upon stealing Logan's healing powers and as a vehicle for Logan to get over have killed Jean.

Having said all of that, The Wolverine is not a movie you have to see in the theater. It's not like Pacific Rim or Man of Steel (although I think it's a better movie than both of those) that really need to be seen on the big screen to get the full effect of the scope of the action. You can just as easily wait for the DVD for this one, and, honestly, I doubt there's anything necessary in this movie for the overall X-Men story line. If you like Wolverine, it's probably worth seeing it, but you're not going to feel like you missed anything if you give this one a pass on the way to Days of Future Past.