Monthly Archives: March 2018

Red Sparrow

I want to talk about the fact that the last three movies I’ve seen theatrically[1] have touched on the action genre and had female leads, but I’m not certain Red Sparrow is the movie best suited as a capstone to that rare achievement. Because Jennifer Lawrence’s dancer[2] turned honeypot spy is explicitly free of any kind of agency. I mean, that is what the film is about, start to finish.

Please don’t take that as spoilers; it’s theme. (It’s not even revealed theme, it has been hammered home before the end of the first act.) Within that framework is a taut spy thriller full of head fakes and direction changes that could as easily be set in 1988 as 2018, save only some pieces of technology that indicate one direction over another.

So if you like that kind of movie, it’s a fine example of the genre, and I enjoyed the roller coaster; plus it’s nice that it doesn’t feel too modern, considering Russian spycraft and its effect on modernity. If you don’t like this kind of movie, it does not rise above its type. But that’s okay! It fills a niche I hadn’t visited in quite a while, and fills it well.

Also: if you want to pretend that the character’s name is Natasha Romanov, I do not believe that hurts the film one whit, so go to town. But it is guaranteed that Marvel could never have made this movie.

[1] without going out of my way to make it happen, is a key aspect of why that matters.
[2] A thing that impressed me is, they took an entire other take on the psychological thriller genre and compressed it down into ten minutes when it would easily have supported an entire move all on its own. This is a dense one!

Tomb Raider

The single biggest problem with Tomb Raider as a movie is that it’s based on a video game. I mean, it’s based on the truly outstanding reboot of the original series, and that helps a lot. But it’s a really solid modern take on the 1930s pulp adventures serials, in much the same way that Raiders of the Lost Ark was a really solid modern take on those same serials when it came out in 1981, but this is nearly two generations later and so the modernism is taken up a few notches, is all. (Also, it’s not set in the 1930s, which, good call.) And to the extent that it was rushed and messy, that extent is because it was following the broad script of a game that you play for twenty plus hours, and yet was given only two hours to tell that story.

The story is this: Lara Croft is a wealthy young heiress to a fortune about which she cares nothing; her only interest is in finding her missing father, who she refuses to accept is dead even though his estate is about to dry up from underneath her since nobody is in charge of it due to his years’ long absence. And she goes looking for him, but it’s one of those “goes looking for” kinds of stories where the person you really find is yourself. Will Lara Croft, rebellious twenty-something who spends her time kickboxing and racing bicycles become Lara Croft, globe-trotting, er, tomb raider? I mean, duh, but not in this movie. This movie is how she finds out those things about herself, while in the midst of drive-in movie mayhem. I wish I’d realized soon enough to keep up the drive-in totals, Joe Bob style, but I can assure you that there is a body count, faces melt, dicks get punched, the whole shebang.

But since she starts off as a novice and ends up far from that space, two hours is maybe not enough time to really buy into her ability to survive on her own, take down an army of mercenaries, and solve archaeological and literal puzzles along the way. To be fair, that’s not entirely what the movie is about the way the game was, but it’s a little close for comfort. My prediction is that the sequel I’m hoping for will do better, since it won’t have to spend any time establishing her credentials, and since it maybe won’t be based on a different game (that I have yet to play, but maybe this year?).

My point is, there’s a great series here, and if they realize it, it will be better than the pretty good movie I watched last night.

The Walking Dead: Lines We Cross

I find that Walking Dead graphic novels come out at the right pace. Twice a year, six issues each (which okay, that’s a pretty obvious rate if you pause to think about it), and whenever I get one in the mail it’s just about exactly the time that I think it’s been a little while since I read the last one. I wonder if I would itch for them more, if the show wasn’t also coming out on about that schedule (eight episodes instead of six, and closer to the turn of the year than an even split, but nonetheless) to fill in any extra itchings.

Sometimes I can tell what they were going for from the title, and other times (like now), not so much. I mean, Lines We Cross is a rich mine for the entire series, certainly, and most of the individual characters have a lot of story dedicated to that question. But this specific book? Nah, not seeing it.

That said, it is an introspective, quiet, rebuilding book, in which people have time to take stock of lines they have maybe already crossed, regrets they have, relationships lost and found. And I will never get tired of the parallel story arcs between two characters that would be very spoilery[1] to call out. But if introspection is not your thing, there’s a new hilarious character (right on the cover!) and the promise of a brand new storyline springing from the culmination of the radio conversations that built throughout the Whisperers arc. So, Kirkman’s definitely not out of ideas yet. And, at least for now, I’m not tired of hearing them yet.

[1] For a lot of reasons

Aftermath: Empire’s End

If you are looking for a book that explains why there’s wreckage all over Jakku in The Force Awakens, then Empire’s End is the book for you! If, however, you are looking for information on where Leader Snoke and the First Order came from, well, you’ll hear somewhere between one to five percent of that story, tops. (Which to be fair, at least until the trilogy of movies is over, you had to know that nobody would be allowed too close to direct backstory, in case the writers wanted to do it on film instead. I mean, you had to know that, right?)

On the bright side, I’m still very much enamored of the characters in this trilogy, and it’s nice to see someone telling a full-sized story in the Star Wars universe where Skywalkers are relegated to a side role at best. (There have been other such stories prior to 2015, but really not very many.)

Just in case there’s confusion, I should note that the book does a lot more than explain Jakku wreckage. But it’s the third book of a trilogy, so why go crazy with spoilers? It continues to do well what the other books also did well: present a living, breathing galaxy reacting to Palpatine’s demise and the birth of a new Republic, while telling a personal story about several people on both sides of the lingering conflict. In other words, if you care about Star Wars, this has star warsy stuff worth caring about.