Unless you happen to be stumbling across this blog for the first time (and if you are, welcome!), you know how I revere Stephen King. I’ve written before about how much of his earlier work shaped me into the rather odd duck I am today. To this day I regret not going to the reading he did here in Wichita a few years ago. He is one of the only people I can think of that would leave me utterly starstruck.
Still, he’s not perfect. Any prolific artist is bound to have some misfires—he’s cranked out some notoriously bad books in his career. There’s also been a longstanding problem with filmmakers adapting his work in a way that works. Many directors can’t seem to figure out how to make a King story translate from the page to the screen (Frank Darabont and Mike Flanagan being the notable exceptions). So, with that said, and as someone who hasn’t read the Stephen King/Joe Hill co-written novella upon which it’s based, it’s hard to know why Netflix’s new film adaptation of In the Tall Grass doesn’t work—whether it’s merely another poor adaptation of the master’s work or it was based on subpar source material and therefore doomed from the start. One thing is for sure, though: In the Tall Grass doesn’t work.
The premise sounds silly on its face: a horror story about some sort of malevolent grass that traps people with no hope for escape. Throw in some bizarre time travel aspects and an all-knowing, all-seeing rock, and it all sounds absolutely ludicrous. But here’s the funny part—for the first thirty minutes or so, it’s actually pretty compelling.
I was completely on board as siblings Cal and Becky stopped on their trek to San Diego so the expecting Becky could puke on the side of the road. Soon after, they hear a boy in the roadside field of tall grass calling for help. He tells them he’s lost and asks if they can help him. The pair decide to help, and enter the grass to their (obvious to us) peril. Things quickly grow confusing as the pair get separated and can’t seem to find each other no matter what they do. The confusion grows as the boy’s mother is heard yelling at him to stop asking for help, and dead animals are found among the grass. Becky ends up encountering the boy’s father, then things begin to go a little sideways.
I won’t spoil anything in case anyone wants to actually give the movie a shot, but In the Tall Grass goes from sixty to zero alarmingly fast. In the span of maybe 20 minutes, I went from fully engaged to completely uninterested. I started checking my phone, leaving the room without pausing it, and then I did something I almost never do: with about 25 minutes left in the movie, I started fast-forwarding to just get the godforsaken movie over with. I was invested enough to want to know how it ended, but not invested enough to actually watch it to find out.
The highlight of the movie is Patrick Wilson’s (The Conjuring) performance as Ross, the father who may or may not be who he seems. He gives it his all, but he can’t save this dud. If you’ve read the book and are genuinely curious I can understand wanting to check it out, but there are far better scary movies out there to be checking out this October, so my advice is to skip it and don’t waste your precious time.