Cranky T-Rex's Blog

Anyone who has followed me for a while knows I'm not exactly a big fan of Christopher Nolan, and yet I was pretty interested in his new film, Dunkirk . I'm not sure why since Nolan has a track record of failing to live up to the hype, such as with  Interstellar.   Interstellar got me super psyched since it was such a cool concept and I'm a space geek, but the movie itself is just straight up laughable when it isn't boring as hell.  So you'd think I would've learned by now. I guess it's just because Dunkirk is about one of history's greatest turning points. 300,000 mostly British soldiers stranded on a beach with the full might of the Nazi war machine closing in on them. The fate of the entire Western world hinged on whether or not they could cross a body of water so small they could practically see home from the shore. Their saviors? Ordinary British civilians who got in their little boats and sailed across the channel to rescue their countrymen, go

Well  Spider-Man: Homecoming  was certainly one of my most anticipated movies of the year. Sony finally returned Spider-Man to the Marvel Cinematic Universe for an epic cameo in Civil War , and now we were going to get a full on standalone story for this new Tom Holland version of the wall crawler done MCU-style.  Add in Michael Keaton playing the villain, and you've got plenty of reasons to be hyped. That of course made me super nervous going in.  I wanted this to be an Independence Day -level movie, the kind that I'd want to turn around and walk right back in for another viewing, and it's tough for a movie to live up to that kind of hype.  Not to mention it had to follow the few fantastic comic book movies we've already had this year and there have been serious concerns that the trailers may have spoiled the entire movie. Alas Independence Day it was not, but as I've said before, even the less than stellar Marvel movies tend to be worth the price of admission