Monday, 28 January 2019

Fantastic Beasts: The Crimes of Grindelwald

From a film-making perspective it's bad - drab and unexciting in all the ways that instantly mark it as a David Yates movie - but from a Harry Potter perspective it's downright insulting, inserting clearly made up on the spot backstory where none is needed and (seemingly) altering established facts about this world and its characters on a whim. It's fan fiction-y and pandering in all the worst ways, and it ends with a reveal so deeply unearned by the film itself and totally at odds with the larger Harry Potter canon around it that I have to assume that the characters involved are either mistaken or simply lying, less my brain be turned to mush trying to figure out just what the hell J.K. Rowling was thinking. Making a film "just for fans" is easy - making a film that's "just for fans" that even the fans are going to hate is bloody hard, yet it's the one thing that Fantastic Beasts: The Crimes of Grindelwald unequivocally succeeds at.

If I sound exasperated, well, that's because I am. Even ignoring the way that much of the film is effectively just unneeded backstory about characters you don't really care about, from a purely storytelling level, Fantastic Beasts: The Crimes of Grindelwald is fundamentally dysfunctional, consistently failing to give the audience the information they need to be engaged in the movie that they're watching. Like almost all of J.K. Rowling's other writings, it's ultimately a mystery story at heart - but here, the mysteries that are central to the story are so poorly seeded by the film itself that there are multiple instances of the audience not knowing what the question even is until the answer is on-screen in front of them. Worse, even if these mysteries had've been set up better, the answers themselves only either raise more questions, or ultimately have very little impact on anything of importance.


Which means that for the vast majority of it's running time, Fantastic Beasts: The Crimes of Grindelwald is downright directionless, never really feeling like it's started in earnest because it's either unable or unwilling to give you any indication of what this film is ultimately about or where it might be headed until far too late. With the benefit of hindsight, it's clear that at least part of Fantastic Beasts: The Crimes of Grindelwald is Rowling's attempt to reckon with the return of fascism as a political force in the West and the rise of the alt-right, how the disenfranchised can so easily be seduced by a charismatic leader who offers supposedly simple, ideologically driven solutions to complex problems, and that's a noble goal - but frankly, Rowling isn't anywhere near as good a screenwriter as she is an author, and the resulting product can't help but feel flimsy and spineless (and maybe even naive) in comparison to what I imagine it could've been had it been fleshed out in novel form.

But the biggest problem with all this is that it's so easy to imagine what this franchise could've been in the right hands, so easy to see the potential that a prequel series about a young Albus Dumbledore and Newt Scamander travelling around the world doing wizard stuff (that eventually - not yet, but eventually - sees them moving against Grindelwald). I like Eddie Redmayne's Newt Scamander and Dan Fogler's Jacob Kowalski; I like Katherine Waterston's Tina Goldstein (even if she has almost nothing to do here); I like Jude Law as a young Albus Dumbledore; and much as it pains me to say, I even think that Johnny Depp isn't bad as Grindelwald. There is value here, entertainment to be found if you look hard enough. With a better sense of direction and someone who isn't David Yates at the helm, I do think that these films could've been an interesting entry into the Harry Potter canon.

No comments:

Post a Comment