Monday, July 24, 2017

First Hurt, now Heard

I don't know about you, but whenever I heard the names John Heard or John Hurt, I always had to
pause for a moment to remember which was which. One was an American appearing mostly in comedies and one was a Brit appearing mostly in dramas, so we wouldn't have mistaken them for one another based on their bodies of work. But their names, their similar ages and their similar times of coming to prominence (at least with me as a young viewer) made them forever interlinked.

That interlinking may continue in perpetuity, as we have now lost both of them in 2017.

John Heard was found dead in his hotel room in Palo Alto on Friday morning, where he was recovering from what was deemed minor back surgery. John Hurt lost his struggle with cancer back in January.

Although I always liked John Heard, his death may not have risen to the level of post-worthy on my blog if it didn't also give me the chance to pay delayed tribute to John Hurt.

But first, Heard.

John Heard was a staple of my 1980s comedy upbringing, sometimes as a villain (Big) but sometimes as a sympathetic character -- even if a forgetful one (Home Alone). To say he appeared "mostly" in comedies seems a bit inaccurate, as scanning his filmography on IMDB reveals far more dramas and thrillers than I would have guessed. But he became famous in films that tickled our funny bones, so I have come to associate him with that. And though he brought a definite smarm factor, which was why he was cast the way he was in Big, Home Alone also showed his capacity for warmth.

Of note: At the top of his page on wikipedia, it says "Not to be confused with John Hurt."

John Hurt has a bit bigger hit list, with classic features like Alien, The Elephant Man, A Man for All Seasons and Contact to his name, as well as a number of Harry Potter movies. But one of his most important functions for me was providing the narration in a personal favorite, Perfume: The Story of a Murderer -- his distinctly musical tones make it one of those rare examples of narration that seems indispensable. He had a certain craggy wisdom to him even when he was a younger man, and he feels like an extension of that great wing of elder British actors that included the likes of Alec Guiness, Ralph Richardson and Peter O'Toole.

Of note: At the top of his page on wikipedia, it says "Not to be confused with John Heard."

They were both in their 70s -- Heard early, Hurt late -- so their remaining contributions to cinema did not figure to be voluminous. But both were working straight up to their deaths, though Hurt had the luxury/burden of being aware the end was coming, while Heard presumably did not. We'll find out more about how Heard died in the coming days.

Goodbye, John H. and John H. You will be missed, and my memory of each of you will be distinct.

Sunday, July 23, 2017

Thou shalt watch movies

I'm not sure if The Ten Commandments will actually be one of the movies I watch in the upcoming personal "film festival" I'm about to tell you about. It would suck up two nights all by itself, which is problematic. And though it was one of the original films up for contention, I now have 25 other films on my custom list on Letterboxd, and only ten nights of available viewing time. (Plus one long stretch on a Saturday afternoon, which may really be the time to do it.)

What is this I'm talking about? Why, I'll tell you.

A delegation from my family will be making a trip to the United States this week, but that delegation will not include me. In fact, it will be composed entirely of my wife. She's coming to a conference in Orlando for her work, and will be out of the country for a total of ten days.

While she's gone, I will watch movies.

Oh, I'll also go to work, do all the shopping, do all the cleaning, be a single dad to my two boys and all that that entails, and sleep.

But when I'm not doing those things, I will watch movies.

I pretty much do that anyway, of course, which is the only way to keep a pace of five to six viewings a week. The difference about the upcoming period is that I can start these movies just after my kids go to bed, not an hour later after my wife and I have watched some appointment TV together. (We're just wrapping up The Handmaid's Tale.) And that means I can tackle longer movies when I'm still fresh enough to watch the whole thing without falling asleep. Maybe not as long as The Ten Commandments -- not in one sitting, anyway -- but a 150-minute movie should be no problem on a given weeknight.

What makes it a "film festival," as such, is that I have been curating the films over recent weeks, in terms of library rentals, iTunes rentals and titles available on our streaming services. I'm not going to program which movie plays on which night in advance -- I'd like to leave it a bit more subject to my own whims and moods -- but I will indeed draw from this available list of titles on Letterboxd. (It's a private list, so don't bothering trying to check it out -- as if you would do that.)

And as in a real film festival, there will be no nights off. Each night between this Tuesday night and the following Thursday night will feature at least one movie, with themed double features hoped for on other nights. (Just a taste of that: The Shining paired with Room 237 and Trainspotting paired with T2: Trainspotting, the latter of which I have not seen in both cases.)

The Saturday viewing slot comes courtesy of my sister-in-law. She has agreed to take both my kids on a sleepover at her house the Saturday night my wife is gone, allowing me to remain home and lie around in my own filth for a day. (Not that kind of filth -- just the general mess that I like to leave when I'm home alone, for no other reason than that I can.) As I do when I have mini film festivals on an overnight hotel stay, I will try to fit four movies into Saturday (depending on when she picks them up) and one more Sunday morning before they return.

And yeah, I could use that afternoon slot to swallow The Ten Commandments whole, but who knows if that mood will strike me when I'm actually in that position. I've already got a perfect four other titles lined up for that day -- again, mood pending.

Of course, now I've gotten carried away and short-listed entirely too many movies, leading to inevitable disappointment. But, we shouldn't spend too much time worrying about things that are inevitable.

I will do my best to document all this viewing -- much of which will be revisiting -- on my blog. And because I like catchy titles, I will label these blog posts "Cat's Away," and then whatever title I consider appropriate following the colon. (Either the movie title or a little pithy comment about the viewing experience.)

It's not that I really am a mouse playing while my cat's away, since my cat basically lets me watch whatever I want, as long as I'm infringing on nothing other than my own sleep. But there is indeed a "mouse playing" mentality when you suddenly gain complete dominion over the television for a period of time, and I will undoubtedly watch some things that would require explanation to my wife -- not even necessarily because they involve sordid subject matter (though there will be some of those), but just because any time you watch something, another person in your house might ask "Why are you watching this?" And you feel like you have to give some answer that makes sense.

I also like this festival as a symbolic baton passing between the two distinct halves of my viewing year. As I have said elsewhere on this blog, I like to break my viewing patterns down into six-month chunks. From February to July, I focus on old releases and rewatches, with new releases sprinkled in. From August to January, I focus on films from the current release year, with old releases and rewatches sprinkled in. It's about to become August, so this festival will operate as a last binge of old releases and rewatches, probably with an emphasis on the latter.

Then the baton gets passed to a real film festival, which symbolizes my shift to focusing on new releases. The very day my wife returns, the Melbourne International Film Festival begins, kicking off another viewing orgy devoted to new releases. I'll be going to about nine films during those 17 days, though for the first time this year, that also includes one old release (but more on that when the time rolls around).

Will this intense viewing period over the next month exhaust me? Well, have you met me?

Here's to the start of a bunch of exciting film watching ... whether it involves Charlton Heston and stone tablets or not.

Saturday, July 22, 2017

Christopher Nolan bombs, and other Dunkirk thoughts

There are plenty of times I have been out of sync with the Metascore for a movie. That probably goes without saying. I'll come home, go to the site, and think "Huh." Baby Driver is one very recent example, as 86 seems extraordinarily generous for a film that is entertaining but quite flawed. Then again, I knew its Metascore before I even entered the theater.

I can't remember a time feeling as shocked by this disconnect, though, as when I came home from Dunkirk last night.

Dunkirk has a 94 on Metacritic. I think it deserves less than half that.

In fact, the one score of 38 on there -- and I sighed in relief that at least one person agrees with me -- might even be too generous.

I ended up giving the movie two stars on Letterboxd, but I wanted to give it 1.5.

What's wrong with Dunkirk? Where to start. This is one of the most dramatically inert films in recent memory. For all the somber energy invested in meticulously recreating a famous World War II battle -- is it even a battle? -- Nolan couldn't give a whip about character development or even mounting tension. Hans Zimmer's bludgeoning score -- seriously, it's even worse than the one for Interstellar -- tells us that every moment is overloaded with dread, but otherwise we'd have no idea that anything was at stake. Images are disconnected from consequences, things are happening for apparently no reason, and the little character arcs that are meant to occur make no impression whatsoever. Oh, it's not that Nolan disregards the notion of human drama altogether in opting for something more abstract and expressionistic -- it's that the dramas he chooses are utterly uncompelling.

What went so wrong? Nothing, according to most of you. When I went on Letterboxd to log my two-star rating, I saw a five-star rating from a person I trust on the landing page. Of the film's 50 positive reviews on Metacritic, 29 are grades of a perfect 100, including three critics whose opinions I've held dear throughout my career: Joe Morgenstern, Dana Stevens and Richard Roeper, all three of whom I've spoken to, and the last two of whom I've had my picture taken with (including Dana Stevens just in May).

Why did I see such a different movie than most of these people? It's hard to say. When you are in the minority on a film, the inclination is of course to view it as a "you problem." You figure you must lack some essential component of your critical faculties that allows you to appreciate what the film is doing. Or, you demand a film to fit into a certain conventional box, the inability to fit into that box being what makes it great. Maybe that is indeed the case with me and Dunkirk.

But I don't think so. This film is a fucking bore. Christopher Nolan is so impressed with his ability to film fighter planes moving in space -- an undeniable strength of the film -- that he doesn't seem to care whether he gave us any characters to relate to. I don't mind that we don't know their names, as there are some great films out there where we never learn any names. I mind the fact that they don't have names or personalities. They are just pawns in Nolan's desire to mount a moving Life magazine photograph. And that's all he's done.

And that's not enough.

I look forward to engaging with other people on this, figuring out the deficits in my character that led me to have so totally missed the boat, so to speak, on this film. But I can't do that for now. In fact, I can't even read Dunkirk's one mixed review -- thank you, Rex Reed -- or Dunkirk's one negative review -- thank you, Jake Cole -- for now. The reason for this is that I'm recording a podcast about this tomorrow night, and I want my bile to be untainted by the bile a few others have already spewed on the topic.

A very few others.


On this podcast, my fellow podcaster will insist that the reason I didn't like it was that I was drunk when I saw it. And the reason he will say this is that I told him I was drunk in a text message about 20 minutes before the movie started. And the reason I know he liked it, even though we don't usually share our opinions on the films before we meet for the recording, is because he pleaded with me to go the next day to an IMAX screening when I was sober, rather than seeing it on Friday night with four glasses of wine in me, at a theater that has no really big screens.

The four glasses of wine -- and a beer -- were courtesy of a volunteer thank you party for my contributions to the Human Rights Arts & Film Festival (HRAFF) earlier this year (though mostly last year, when most of the heavy screening occurred). I had expected this to be a tame little affair that I could quickly skip out of -- it had been held in the organization's tiny office the year before -- and I planned to stay no longer than 30 minutes, leaving in time to watch a 6:40 showing of The Beguiled before my 9:20 Dunkirk.

But this year the party was held in a private room at a pretty cool bar, and when 6:30 rolled around and I was still enjoying myself, I gave Sofia Coppola's film with the middling reviews (at least among my friends) a pass. And got into one of those rambling, animated cinephile discussions with two women about films we love and hate, using the thinnest of connective tissue to jump from one film to the next -- the kind of discussions that are especially well lubricated by wine. I became so engrossed that I nearly didn't leave in time for Dunkirk.

Given my thoughts on the film, I am immensely glad I did not sacrifice that experience for the movie, and also that I did not shift around a Saturday with my family in order to see Dunkirk on IMAX (and pay for it out of my own pocket, something I wasn't having to do on Friday night on the smaller screen).

But the question is, did being "drunk" -- how far along on that spectrum I was is debatable -- impact my enjoyment of the film?

As I am biased here and predisposed to endorse my own decision making, I'm going to say "no." But I guess I can't really say for sure, because I can't see it for the first time sober as a point of comparison.

What I can say is that falling asleep was not a problem as I watched the film, which I always figure to be the biggest danger in a film starting at 9:20, whether you're drunk or not. As I said, I was bored, but it was not because the alcohol was making me distractable. It's because Christopher Nolan made a boring film.

I don't even think IMAX would have helped. I was able to appreciate this film's visual accomplishments just fine on the screen where I saw it, and I honestly don't think this is a case where those accomplishments, given a proper showcase, would have rendered some of the film's shortcomings less important. In fact, even in a state of somewhat compromised perceptions, I was glad to feel clear-headed enough not to be swayed by the sweet persuasions of impressive visuals. A film needs to either have a compelling story to be a success, or if not that, then just be a straight art film with no story whatsoever. Nolan's middle ground in Dunkirk is a bad place to be.

July 20th -- again

Methinks Christopher Nolan needs to concentrate more on making a good movie and less on making sure that movie comes out on July 20th.

And incidentally, how can July 20th fall on a Friday every single year?

July 20th was of course a Thursday this year, but movies get released on Thursdays in Australia, so the 20th was its release date indeed.

It may be a Warner Brothers thing, but Nolan's movies have long been perceived as a late-summer sort of counterprogramming, or maybe just a delayed infusion of prestige to a season that has already included its share of Pirates of the Caribbeans and Transformerses.

The July 20th trend got started in 2008 -- on July 18th. That's when The Dark Knight hit theaters. Its predecessor, Batman Begins, was a June release, but I guess The Dark Knight felt right in late July.

So right, in fact, that they duplicated the release strategy for Inception in 2010. It being two years later and without the benefit of any leap years in between, Inception could not land exactly on July 20th either. So July 16th was the chosen release date.

We finally get to an exact July 20th release date, with the benefit of a leap year, two years later for The Dark Knight Rises in 2012. That date may of course be etched into your memory for being the night of the horrific theater shooting in Aurora, Colorado.

Warner Brothers deviated from the strategy with a November 2014 release for Interstellar, but it's back with Dunkirk -- a film whose awards aspirations might have more logically dictated a November release date than Interstellar. Though I suppose some of these things have to do with when a film is actually ready to go to print.

What relationship does the release date have to the quality of the film?

None, of course. And I'm sure my criticisms of Dunkirk don't seem very substantive, since I haven't delved in to why I dislike it so much.

I could. Believe me, I could. But I guess I already feel like enough of a grinch for raining on the parades of readers who may have already bought their tickets for a screening at some point later in the weekend, but happened to do their Friday check-in with my blog before then.

But as a wise friend told me last night when I texted him my initial reactions and then apologized for shitting on a movie he was excited to see, "Maybe I will love it, maybe not. It will have nothing to do with you. When any movie comes out, there will be people who don't like it."

In the case of Dunkirk, just not very many of us.

Friday, July 21, 2017

Saoirse Ronan is a grownup

There's a scene near the start of Brooklyn, which I just saw on Wednesday night, where Saoirse Ronan's Ellis (pronounced Eye-lish) watches a friend walk off with a cute boy at a dance in her small Irish town. Her expression toward her departing comrade, who looks back to smile and giggle, is at first one of supportive encouragement. As the girl recedes into her dance, the expression becomes by degrees more hollow, slackening into disenchantment, then dissatisfaction, then disillusionment, then discomfort, then awareness of discomfort, then a resolve that it's time to walk away and do something else. In this one 20-second shot, Ronan has given us a mini master class on acting.

This is not how a 20-year-old acts. This is how a grownup acts.

In fact, when principal photography on Brooklyn began on the first day of April in 2014, Ronan was not even 20 yet. She was 11 days shy of that birthday.

Actors who show absolute command of the craft at a young age are not total anomalies. One family, the Fannings, even has two such actresses, with Elle possibly being even better than Dokata. But there is something so prepossessed about Saoirse Ronan that it seems to put her in a different category. She was an adult even when she was a child.

I remember my first experience with her in Atonement, which it's hard to believe was nearly ten years ago now. She would have been only 11 or 12 at the time that was filmed, and though she was playing a child making bad decisions -- fatal decisions, in fact -- she was making them in adult ways. Making them with a kind of prepossessed shrewdness, which made them seem calculated rather than careless. There was something old and wise about the look in her eyes, something that indicated she'd be better off tried as an adult than a child in a court of law.

Recognizing the unmistakable presence she brought to her work, Hollywood of course targeted her for a number of familiar type teenage roles in movies aimed squarely at that demographic, things like City of Ember and The Host. But many of her roles were in projects that were a bit more challenging, making a bit more unusual use of a girl in her teenage years, like The Lovely Bones, Hanna, Byzantium and How I Live Now. I haven't seen all of these movies and some I am judging on a vague perception only, but all of them, in their way, seem to require someone with a certain maturity and sophistication. A maturity and sophistication Ronan had long before she had any business having it.

In some of those roles, there is an explicit sense of adulthood to her character. In Hanna, for example, she has been raised as a lethal weapon, a fighter who can incapacitate an adult despite her tender age. In How I Live Now, she's a surrogate mother looking after younger siblings in a post-apocalyptic England. In Byzantium she's, well, a vampire. The oldest of the old -- eventually if not now.

In Brooklyn it feels hard to imagine her as anything other than a fully grown, fully blossomed human being. Ellis the character is no older than Ronan is, but she travels on her own to New York to start up a new life. Both the decision to go and the going by oneself are signs of adulthood, but it's the stolid way she handles everything that comes her way that truly distinguishes her as a grownup. This is not to say she doesn't succumb to the occasional bouts of overwhelming homesickness, which crack her professional facade at her job. But there's nothing childish about her homesickness -- it's the mature pangs of guilt and fondness over a sister and mother she left behind in the old country. When she begins a courtship with a handsome young Italian plumber (Emory Cohen), and begins progressing with him at a rate that might seem impetuous, she's making pragmatic choices here too. Even though she feels swoony, she behaves practically, at one point even telling him that she will commit to two movie dates with him -- "even if the first one goes terribly, I'll give it another go." Sensibility incarnate.

An argument might be made that the best young actors show us what it's truly like to be a child, remaining in close contact with the turbulent emotions of that age. There'll be time enough later for them to show us how grown up they can be. Hailee Steinfeld is an actress who excels at that type of thing.

But an actress like Saoirse Ronan reminds us, refreshingly, that young people are just adults who are not yet fully formed -- or sometimes, are fully formed. The truth in her performance is that she plays characters with a kind of preternatural wisdom -- a wisdom that we believe because it can be just as true to life as characters who are changeable and petulant.

It'll be interesting to see what she's capable of when she really is a grownup.

Thursday, July 20, 2017

The temptation to scold Edgar Wright

Rightly or wrongly, a director who leaves a movie before its completion can assume a certain "holier than thou" aspect. Sometimes directors get kicked off movies, which is no fault of their own. However, sometimes they cite the ever-popular "creative differences" and depart a movie on their own terms, and rightly or wrongly, this opens them up to scorn.

Warning: The following argument comes dangerously close to taking the side of The Man. But hear me out.

Certainly, you'd think that if Edgar Wright left Ant-Man, it was because Marvel Studios wanted to control him and fit him into a tiny artistic box that he didn't want to occupy. He had sprawling, rambling ideas that consisted of a type of genius that didn't jibe with their conception of the movie. Fine. Leave the movie, Peyton Reed will finish what you started with something halfway watchable (but pretty bland compared to what you would have done), the movie will be reasonably warmly received and everyone will go their merry way.

But I'd be lying if a small part of me didn't say "What, too good for Ant-Man, Edgar Wright?" Rightly or wrongly.

Because it's a bit inevitable to perceive someone who leaves a movie -- leaves, not gets fired from -- as having a bit of an inflated sense of their own self worth. Some would argue that this is a very reasonable estimation of their own worth, as any person should stand up for themselves and not just accept being the puppet of some studio. But there's a certain element of standing up for yourself that seems like rocking the boat. Movies are made by people who become inextricably linked with one another despite inevitable compromises in how they imagined things going, and if you're a good soldier you just grin and bear it.

Wright wasn't a good solder, and some people would celebrate him for that.

I did, sort of, while also wondering what terrific use of his talents he was saving himself for. What thing would be worth not sullying his name or reputation by having a credit on an imperfect realization of his vision for Ant-Man.

The answer is: He was saving himself for Baby Driver.

Which makes it all the more disappointing.

I don't dislike Baby Driver, but let's say that in just 24 hours since I finished watching it, I have already rounded my 3.5-star rating down to three stars and am thinking of going lower. The movie doesn't stand up to even a little bit of scrutiny, and it's not even all that great when you don't scrutinize it.

But I don't want to litigate the strengths and weaknesses of Baby Driver in this post, though I could go on at length with nits to pick and parts that annoyed me, especially in the last 30 minutes. (And for a guy who prizes his own vision for a film, he felt awfully like he was channeling Quentin Tarantino in this movie, didn't he?)

Instead I'd like to concentrate on how Baby Driver is burdened by being an alternative choice to Ant-Man, though in reality, it likely would have been his next movie with or without the MCU film in his filmography.

If Baby Driver had just followed on the heels of The World's End, the 2013 Wright movie that I like even less than Baby Driver, it might have concerned me as a sign that a once-sharp filmmaker who made at least two bracingly original films (Shaun of the Dead and Scott Pilgrim vs. the World) was on a wayward path. But as is, it's what he's offering the world as proof of what he's capable of -- when someone isn't trying to pull his strings. With Baby Driver, Wright says to the world, "My shackles are off. Now watch me fly."

Or maybe, crash land.

In Wright's defense, he has established himself -- through no fault of his own, or to put it another way, "rightly or wrongly" -- as a creative talent from whom a lot is expected. He has a passionate cult of followers who worship his films. There's a lot of pressure on a person like that, a pressure to continually outdo yourself and be greater than you were last time. Even if only two of his now five features have actually earned him that kind of devotion.

So my under-appreciation of Baby Driver could just be a manifestation of my own frustrated expectations for the man's next work.

But I don't think so. I think I have had a love-hate relationship with Edgar Wright that is equally happy to be pushed in either direction. I look forward to his next film either because it will confirm he's great or confirm he's a hack, and I kind of don't care which. I can argue either narrative. (If you're wondering where the one film I haven't mentioned, Hot Fuzz, falls on the love-hate spectrum -- which is really a spectrum of "love" to "don't love that much" -- it's pretty much in the middle. I like it, but not overly.)

And I guess something about the Ant-Man debacle has kind of rubbed me the wrong way. Am I an apologist for a gigantic movie studio like Marvel, or to step out one level greater, like Disney? I don't think I am, but if I generally trust the things a company does -- and that's the case with Disney -- I do extend them a certain loyalty. I do think that someone should think of it sort of as an honor to be entrusted with a Disney product, and if they don't properly appreciate that opportunity, it's a them problem.

But still, had Baby Driver seemed like the inevitable next chapter in the cinematic universe inside Edgar Wright's brain, I would have been happy to argue his genius.

Instead, I'm yielding to that temptation to scold him.

Wednesday, July 19, 2017

The last scraps of 2016

If you can believe it, there's still one more movie with a 2016 U.S. release date that has yet to come out in Australia. It doesn't even come out until next Thursday, the 27th, actually.

Fortunately, due to the magic of press screenings, you can already read my review here.

I'm not sure why J.A. Bayona's A Monster Calls had such a slow progression to the Australian cinemas, but perhaps they just wanted to wait until it was the dead of winter and the movie could not depress us any further. (It's actually not "depressing" in the pejorative sense that one would usually use if describing a movie; it just happens to be about sad things.)

I do have a bit of mixed emotions about reviewing a movie like this, if only because I've mentally moved on by late July and feel like I want to be spending time on movies that count toward my 2017 list. I see 2016 movies at home, but in the theater it feels a bit weird. (Even the private critics screening room where I saw it.)

Then again, I love hearing myself talk, so if someone wants me to talk about a movie that had even its wide release more than six months ago in the U.S., I'm your man.

And though U.S. readers will have likely had the option to rent this for a good four months, Australian readers are advised to check it out in the cinema. It's worth the big screen.

Saturday, July 15, 2017

Not this year's Jupiter Ascending - or so I hope

After Jupiter Ascending came out two years ago, I didn’t know if there would ever be another Jupiter Ascending again.

I mean, I didn’t want another Jupiter Ascending, per se, because that movie was awful. No sequels necessary. But I did want another “Jupiter Ascending.”

The difference indicated by those quotation marks is as follows: I wanted another movie that took the same risks as Jupiter Ascending, in a genre in which only sure bets are usually green lit. I wanted it still to be possible to have movies that fit that small cinematic niche of “big, imaginative science fiction movie with fantasy worlds and no established characters.” I didn’t want studios only to gamble on Star Wars movies, though that’s obviously no gamble at all. I wanted them to gamble on what might become the next Star Wars.

But after several recent major flops in this arena – Ascending, but more catastrophically, John Carter – it seemed less and less likely that we would see many, or even any, more of these. One cautionary tale is enough for most studios – two, and you have serious cinematic leprosy on your hands. No one wants to go anywhere near it.

So I guess the pressure is really, really on Valerian and the City of a Thousand Planets.

When I was at the movies on Wednesday, I watched enough of the trailer for Luc Besson’s new movie to know that I didn’t want to watch any more of it. In a good way. I start avoiding a trailer once I get to that point where I say “Yep, I’m hooked, now leave the rest of it as a surprise.”

“Hooked” may be the wrong word for Valerian, because there are a million ways a movie like this could go wrong and only a scarce quantity of ways to do it right. So just because it looks nice – like really, really nice – doesn’t mean that it’s got anything going for it.

But if it’s great, I want to experience its greatness unspoiled.

And if it’s not great … well, we definitely won’t see another Valerian and the City of a Thousand Planets.

Friday, July 14, 2017

Cirque du Soleil: the one ideal incarnation for Avatar

While at the movies Wednesday night I saw an advertisement for Toruk, the upcoming Cirque du Soleil show inspired by Avatar. Whether it fits into the narrative of Avatar, or even has any narrative to speak of, is not certain. What is certain is that the acrobats are dressed up like Na’avi, and they do their leaps, twirls and somersaults through a stage manifestation of the Pandora forest.

What’s also certain is that this is a great way to use the world of Avatar.

In less than five seconds of this ad, I went from rolling my eyes about the concept (which I’d heard of only a few days before) to saying “Hell yeah, what a good idea.” I’d probably see Toruk, and not only because I’m overdue for my first Cirque show since the early 2000s, when I saw two in fairly close succession. One of those was the Las Vegas show called O, which involves a swimming pool built into the stage floor. It left an impression on me, and I still have a soft spot for the troupe despite the persistent suspicion that they might be sort of lame.

What’s also certain is that this is a far better way to use the world of Avatar than to have 11 more sequels coming out by the year 2030.

That’s only a slight exaggeration of how many more Avatar movies are on the horizon. Officially, it’s four. One would certainly hope James Cameron will have said everything he needs to say about this world after four more, but if the fourth still makes good money, who knows how much longer it could go.

And if the fourth still makes good money, I suppose we won’t have a problem. But that’s what I’m considering highly unlikely at this point.

You might logically say that Cameron had said everything that needed to be said after one Avatar movie. Some would argue that everything that needed to be said about Avatar had been said in Dances with Wolves or Pocahontas, calling into question the need for even a single Avatar. Though since the movie became the biggest box office hit of all time and stayed that way for six years (until Star Wars: The Force Awakens), it’s reasonable to conclude that there was a legitimate hunger for Avatar’s offerings, at least at some point.

But as I may have discussed on this blog before – and if not, I’m overdue – Avatar has endured poorly in our popular consciousness. Many of us (including me) only saw it that one time, and even those who loved it at the time do not really go to bat for it these days. You don’t hear anyone with an obsessive ongoing relationship with Avatar, like they have with something like Star Wars, for example. And while that’s an impossible standard for anything, it seems reasonable that a film that had made more money than any other movie, and has four sequels planned, would be one of the most capable of meeting it. In fact, would need to come close to meeting it to justify the expenditure on four more expensive sequels.

Part of the reason no one talks much about Avatar could be that the Na’avi themselves seem like a short-sighted creation. There are a couple reasons for this. One is the unfortunate white savior/exotic savage dynamic that’s intrinsic to their conception, with Cameron trying to cast Jake Sully (or himself) as the outsider who can come in and rescue a bunch of noble natives who are being abused by big corporations/military institutions. Even if it’s the good fight from a liberal perspective, it has bad optics. Then there’s the idea that the Na’avi just seem goofy, with their blue skin and big eyes. Maybe we got into bed with them only because they were part of a mind-blowing, sumptuous 3D experience, and we always would have preferred characters who were a bit less like humanoid lizards with mystical tendencies.

But what makes “us” want to disassociate ourselves with the Na’avi also makes them perfect for Cirque du Soleil. When we go to the circus, or the ballet, or any other art form that celebrates the physical movements of the human body, we want a world that’s a bit mystical and fanciful, where blue skin and lizard-like movements are a help rather than a hindrance. We want to see majesty on display, and we’re a little less beholden to the narrative utility of the majesty we’re seeing. It’s not important that the characters seem adaptable to other environments, as, for example, the Star Wars characters have been repurposed for umpteen other uses that have enabled the ubiquity that supports umpteen sequels.

So while I’m not at all sure the Avatar sequels will make their money back, I feel fairly confident Cirque du Soleil will do just fine. And they may be smart with their timing as well. It’s still a few years before we get Avatar 2, so in one sense this seems to be coming out of nowhere (out of the blue, har har). But it might be better now than after the movies come out, because it’s very possible we’ll become saturated with Avatar and may not respond well to that. There definitely won’t be any hunger for a Cirque du Soleil incarnation of Avatar if we’ve roundly rejected the cinematic version.

I like Avatar enough that I want it to endure as an institution, something that maintains a certain level of cultural cache rather than being consigned to the dustbin of cinematic history. But the way to do this is not by sequeling us to death, by releasing a bunch of merchandise of blue Na’avis who look enough like each other that we can’t really tell the difference between the girl one or the boy one, and our kids don’t want to play with either of them. The best way to do it is through something like Cirque du Soleil, which will encapsulate some of the things we liked about Avatar while excising some of its more problematic elements.

But there aren’t billions of dollars bound up in a traveling circus show, so fat chance of that. 

Thursday, July 13, 2017

A return to Spider-Man

Of all the major superhero movies, I've seen the smallest percentage of ones featuring Spider-Man. Until last night, it was just half of the movies that fit that description, and only that many because the character makes an appearance in Captain America: Civil War. If you include only movies with Spider-Man's name in the title, it was only two of the existing five. The number of years since I'd seen a movie devoted to Spider-Man is an even more astonishing figure: 13. That's right, 2004's Spider-Man 2 was the last I'd deigned to see.

To give you some idea how unusual this is, I'm missing no more than one of any other movie featuring any other superhero of any note. In fact, the only significant examples I can really think of are the second Thor movie and the third Iron Man movie, and ten years ago neither of these guys had even one movie to their respective names.

What's more, of the superheroes I have designated as "the big five," I've not missed a single of their movies -- no, not even the Incredible Hulk. The other four being Superman, Batman, Wonder Woman (only very recently a cinematic entity) and, yes, Spider-Man.

So why the Spider-Man drought?

It didn't feel intentional. I'd always expected to see Spider-Man 3, despite liking the first two movies only about 75% as much as most people did. But I heard it was bad and, well, perhaps that was a particularly busy summer for me. Then when The Amazing Spider-Man came around, I'm sure I intended to see that as well. But I passively participated in an unspoken boycott of it, probably because I thought it was too soon to reboot the character (and, well, I heard that one wasn't great either, and maybe I had a busy summer that summer too.) The Amazing Spider-Man 2? Well, if I hadn't seen the first one, why start now?

What finally brought me back was when Spider-Man was brought back home to Marvel -- and not until I was sitting in the theater did it occur to me the secondary meaning of the word "Homecoming" in the title.

Even the generally good taste of Marvel might not have been enough if I hadn't seen him in Civil War, where he combined with another character that I'd come to consider sort of a dubious property (Ant-Man) to comprise possibly the two most fun things about that movie. Civil War showed me Spider-Man could be done right -- even if I hadn't personally witnessed any of the examples of him being done wrong.

And it was a pretty happy homecoming for me, as it turns out. I didn't love Homecoming, but it's got some funny moments and some exciting moments, and it rests comfortably in the upper half of Marvel movies I've seen.

Interestingly, though, the reasons it worked for me were more or less the reasons Ant-Man didn't totally work for me, and that has everything to do with timing.

If you remember this Ant-Man rant, my biggest gripe about that movie was the awkward way it introduced the MCU. If memory serves, little to no mention is made of any other superheroes until about halfway through the movie, when Scott Lang says something along the lines of "The first thing we should do is contact the Avengers."

The who? Suddenly the spell of being in a world where Ant-Man was the center of the superhero universe had been shattered. I wanted that universe to last a bit longer before he was just another face in the MCU crowd. It left a sour taste in my mouth and started spoiling a movie that was only really all that interesting in the parts that Edgar Wright obviously contributed before he left the movie.

Spider-Man: Homecoming doesn't suffer from the same problem. The Avengers are in this movie from the very first moments on screen, when a child's drawing of Iron Man, Hulk, Thor, Cap et al is rescued from the debris of the battle that mostly leveled New York at the end of The Avengers. Not only do we get a visual reminder of those characters (only some of whom we will actually see in the ensuing movie), but we're immediately reminded of a major plot point from their first movie. This is an Avenger world, and Spider-Man is only part of it.

And that's okay, if you do it right. In fact, it's probably inevitable, and again it's a function of that timing. Timing not only in terms of getting to other parts of the MCU straight away, but timing also because we've already seen Spider-Man in the context of the Avengers. We hadn't seen Ant-Man that way until after his solo movie, and that seems to have made all the difference.

I also dug Michael Keaton as the villain, who gives a fairly direct shout-out to his character in Birdman in terms of wearing a winged creature suit. (In fact, at first I wondered if he was supposed to be Anthony Mackie's Falcon ... until I saw him doing, you know, bad things. Especially since Falcon was the main link to the Avengers in Ant-Man.)

I don't know if I'll need a lot more solo Spider-Man movies, though if they're making a third Thor movie, I'm sure we'll get at least a couple more. I also don't know if I'll be inclined to circle back and catch up with the Spider-Man movies I missed the first time around.

But I'm glad to have Spider-Man back in my life -- back as a presence I'll be making excuses to see, rather than not to see.

Wednesday, July 12, 2017

You can't have it both ways, Daniel

News has come out that Daniel Craig is coming back for a fifth Bond movie.

This after his comments about returning can be summarized as "not on your life, you asshole."

It might not have been quite an example of biting the hand that feeds him, but it's pretty darn close. While I'm not looking up particular quotations right now, his perspective on the subject seemed to be that he would sooner play the little orphan in the next remake of Annie than play James Bond again. (Just looked up an actual quotation. He said he'd "rather slit his wrists.")

Well, he's playing James Bond again.

Money would obviously be a motivating factor, though it would seem that Craig has plenty of that. Not only has he made those four Bond movies, but he's made plenty of other movies during the same period, remaining quite active throughout.

Dwindling relevance? I suppose that could be a factor too. Craig turns 50 next March, so no time like the present for a midlife crisis.

I wouldn't ordinarily fault an actor type or other Hollywood type for taking another job after saying he or she definitely, absolutely was not going to. Athletes do it all the time. Are you retiring or aren't you? It's something we live with in every sphere of entertainment. How many bands have promised this is definitely, absolutely, positively their final tour?

But something about Craig's attitude has made him a bit of a different case. It's kind of seemed like Craig has felt that Bond was "holding him back" for some time now, and that even returning two movies ago for Skyfall involved a lot of arm twisting.

Few people have evinced as much desire to leave Bond behind them, saving perhaps only George Lazenby, who made good on his promise and walked away after one movie. Bond has clearly been a stepping stone for Craig -- he'd be a successful actor without the role, but not a household name. Yet he's been eager to push that stepping stone down to the bottom of the pond and never look back on it, or so it has appeared.

Yet with this fifth movie, he will be becoming the longest running Bond behind only Roger Moore and Sean Connery. He's currently tied with Pierce Brosnan's four, so this would be putting him ahead of the erstwhile Remington Steele.

Is that an important consideration for Craig? Probably not.

What is his most salient consideration? Hard to say. The articles don't say anything about it.

All I know is, next time he says he's done, he better be done.

And, it might be nice to display a bit of gratitude toward this franchise that has thrust him into such international prominence.

Personally, I'm a bit disappointed. Only one of Craig's films is one I'm reasonably fond of (Skyfall), and I definitely thought it was time for some new blood. And I definitely though that new blood could be of a different race or even gender. That would have been a Bond film I'd like to see.

Craig's next, and presumably final?

Not so much.

Tuesday, July 11, 2017

John Denver is having a moment

Ben Wheatley and Bong Joon-ho were undoubtedly making their respective 2017 releases, Free Fire and Okja, at approximately the same time.

So only a certain random felicitnousness could have led them both to use John Denver's "Annie's Song" in virtually the same context in their movies.

If you don't know the song -- and I didn't before I saw Free Fire -- it's the one that goes:

You fill up my senses
Like a night in a forest
Like the mountains in springtime

etc. etc. etc.

In both movies, this soaringly sentimental ballad is used as an ironic counterpoint to something going on on screen, and kind of a similar thing in both cases.

In Free Fire, it's playing on the 8-track player of a van that's making its way through the impromptu war zone that's popped up in a warehouse where an arms deal went south. If memory serves, the driver may have been shot, leaving the vehicle to roll to a stop of its own accord while the music blares.

In Okja, it plays directly over a scene of chaos, as police try to subdue animal rights activists in an underground convenience store after a super pig has plunged through it, knocking cosmetics and cold medications hither and yon. They shoot tranquilizer darts at the activists and the super pig, and the activists elegantly defend themselves by deploying umbrellas in the direction of the blasts -- which, indeed, are quite effective in stopping this particular form of attack.

The only fundamental difference in the way the song is used in the two movies is that the moment in Free Fire is quiet, by that movie's standards, as the Denver song is the only absurd interruption to a scene where everyone is on tenterhooks to see who will expose himself next or fire the next shot. In Okja, it directly scores an action sequence, similarly absurd for the combatants and some of the details of the scene, and similarly operating as a counterpoint to what's going on on screen. The action being in slow motion and devoid of its diegetic sounds means that it's also sort of "quiet" in the same way that it is in Free Fire.

Now, if a third 2017 movie also uses this song in even a remotely similar context, that will be really weird.

And if a 2018 or beyond movie uses it, that will be a ripoff.

Monday, July 10, 2017

Not the curmudgeon he thinks he is

I've been getting more and more examples over time that my nearly seven-year-old does not hate "baby movies," even though he professes to. But Sunday was the coup de grace.

First a little background.

We recently got The Lion King out from the library, I think at my instigation. However, unlike other recent animated classics I've successfully pushed on my kids, this wasn't one of those where I'd planned to sit down with them and watch it. That's in part because The Lion King has never been a personal favorite. I didn't see it until more than a year after its release, and I've only seen it that one time. (I remember the exact timing of my viewing, October 1995, because I watched it with a girl I was dating at the time.)

My own partisanship or lack thereof was not a decisive factor in it making its way into our DVD player, probably because the younger one (age 3) still loves anything with animals in it. He's as much of a stereotype for his age as the older one is with his love of Pokemon and anything where someone has a gun. But the older one watched and like The Lion King too.

At some point we also acquired The Lion King 2: Simba's Pride from the library, which I have not seen and would have not played a role in selecting, since I've got a bit of a bias against straight-to-video sequels, whatever they may be. It turns out my wife was responsible for this one, not because of any interest or experience with it (she never even saw the original) but probably because my younger one found it in her presence and she added it to the stack. I wasn't even aware it was among our 30 or so library videos (they let you take out 50 at once!) until the younger one said he wanted to see it. "There is no Lion King 2," I even said when he said he wanted to watch it, forgetting for a moment about Simba's Pride and thinking that the fact we didn't have it was sufficient enough to negate its existence entirely. He proved me wrong on both counts.

It didn't get watched the day he originally talked about watching it, but he did select it as "his choose" for Sunday morning TV time. Usually in this scenario, the older one suffers through 20 minutes of the movie (at most) before declaring it now time for "his choose," which is fair enough, as you shouldn't have to suffer through an entire movie you don't want to watch.

But this time it wasn't a problem. This time, in fact, the older one never even took a choose. This time, in fact, the younger one stopped paying attention to Simba's Pride while the older one sat there, rapt, watching it to its completion.

I still would have written this post if that were all that happened. But it gets better.

When Simba's Pride finished, the older one said "I want to watch it again."

With a bit of a laugh, I clicked the back chapter button until he was at the beginning again.

Now normally, I wouldn't really want my children to watch two entire features' worth of screens before we got going on our day. That's a bit too indulgent. But when it comes to movies, I like to encourage their interest, and besides, I was handing over to my wife around 9:30 so a friend could come over to watch baseball with me on his computer. (Yes, I have an Australian friend who not only likes baseball, he even pays for the baseball package.) Consequently, I don't know how much of his second viewing he actually got through, but the fact of it at all was what interested me.

I'm crazy for movies, and I can only think of two definite times I've watched the same movie twice in the same day, and only one of those instances can be described as roughly consecutive. Now, kids are a bit more obsessive in this regard than adults, but it's certainly something he's never done before in a good four years of watching movies.

I still would have written this post if that were all that happened. But it gets better.

This morning, when I was getting ready for work, Simba's Pride came on again. It's school holidays, so we're letting them watch TV on weekday mornings as well. I was escorted out of the house with that pretty beautiful song "He Lives in You" that plays over the opening credits.

I still would have written this post if yada yada yada.

When I got home from work today, the kids were having "quiet time," which is code for "mummy and daddy are exhausted from a full day of entertaining you and now you must watch TV." Again, it's an allowance on a weekday made possible by school holidays.

Guess what was playing?

So this is clearly the most obsessive behavior my son has ever displayed toward a movie. Even the ones he says he loves he probably wouldn't watch more than twice in a week, and not likely on consecutive days in any case.

So now I simply must see this movie myself.

Since we have both the original and the sequel -- at least until our renewals run out -- I talked about making it a double feature one night when my wife is out of town at the end of this month. I planned to do it on my own to further my cinematic education (a refresher on The Lion King is always useful), and to be able to relate to my son on a topic he loves. But when I mentioned I might do that, he said, "Can I watch it with you?"

That might keep him up until 11 o'clock at night, but how can I refuse an offer like that?