Backlot Gossip
Search
Saturday
May182013

Star Trek: Into Darkness (2013)

Kick the Khan

I don't think these kids can steer.

--Captain James T. Kirk, Star Trek 2: The Wrath of Khan

In my review of the 2009 Star Trek remake, I said it was unfair of geeks to label J.J. Abrams' vision of their beloved franchise as "not Star Trek". Nostalgia, I argued, had clouded their ability to see that a nearly fifty-year-old series needed to be shaken up and modernized a bit in order to stay viable. I love that movie, despite its flaws, and waited anxiously for four years to find out what the new versions of Kirk, Spock, and the Enterprise crew would do next.

After having seen Star Trek: Into Darkness, I'm willing to give the cacophony of nerd rage a closer listen. I still think what Abrams and writers Roberto Orci, Alex Kurtzman, and Damon Lindelof have served up this time out is Star Trek, but it's pretty terrible Star Trek.

I'm talking Final Frontier-level awful.

The myriad problems boil down to the creators' fundamental misreading of the alternate-universe timeline they've created--and, possibly, too much booze in the writers' room. Seriously, as soon as we get past the Paramount and Bad Robot titles, Into Darkness becomes a two-hour film studies course in "What's Wrong with This Picture" moviemaking. From shoddy storytelling that makes zero sense within the context of any given scene (let alone the series' own canon--more on that later), to visuals that are often a cocktail of flashy incoherence and Gatsby-level tedium, everyone involved seems desperate to cover up their lack of anything new or relevant to say with shiny objects and sloppy call-backs to The Wrath of Khan.

Let's get this out of the way: Benedict Cumberbatch plays Khan. Really, how could he not? Though the Paramount marketing team and Abrams' own cadre of Fan Fuckery Fanatics have worked tirelessly to cultivate their own sub-industry of mystery buzz, you'd have to have either been a complete dupe or the victim (beneficiary?) of a total media blackout to not put this together. Khan is the villain this time out.

Or is he?

If you're a Trekkie, of course you know that Khan (as played to homicidal, hammy perfection by Ricardo Montalban in the original series and 1982 film sequel) was a genetically engineered evil mastermind in the late 1990s. He and seventy-two minions were exiled into deep space somehow, and later reanimated by Kirk and the Enterprise crew during the "Space Seed" episode.*

In the Abramsverse, Khan Noonien Singh is still a super-man frozen and entombed with his followers. But there's a key problem with this version of his origin:

He's white. Look, as a child of mixed marriage, I understand that one can come from a blended heritage and not look it, but according to the rules Abrams et al set up in the last film, the Trek timeline didn't diverge until several hundred years after Khan was exiled--meaning he should still look like a Mexican playing an East Indian. Here, he's a pale, thin British guy who trades hissing passages from classic literature for droning on about revenge and family and God knows what else--all with the flair and engagement of an Accounts Payable clerk reading Downton Abbey's end credits.

The original Star Trek mythos took great pains to establish Khan's back story. In his day, he was a charismatic, ruthless leader who controlled a quarter of the Earth's population. Into Darkness finds him a super-powered lunatic "criminal" who is really good at kicking ass. Khan wasn't Kirk's greatest foe because he looked cool while killing people--his most powerful weapon was a calculating mind that gave him the ability to charm almost anyone while slipping a dagger between their ribs. This came with an ego that also proved his undoing on two big occasions--but that's a level of detail the writers can't be bothered to acknowledge here.

Cumberbatch is the British Actor Du Jour, so it's only natural that Paramount would want to have him anchor their big summer movie. But he's far above the material and acts like he knows it. Except for one pretty great freak-out moment, the actor just looks bored here, and if you have, by chance, never heard of him before seeing this film, you'll likely leave the theatre wondering why in the world he was cast.

I've spent a lot of time talking about Khan because, frankly, he's the only interesting part of the movie. The 2009 Star Trek film also had a weak villain, but its purpose was to introduce us to characters who would go on to do great things. Of course, if you leave characters out in the sun too long, they will begin to wither, and by not giving them anything of sense or consequence to do this time out, Orci, Kurtzman, and Lindelof make them utter non-entities--and, in some cases, blatantly unlikable.

It's as if the creators took the nuance and potential of Kirk (Chris Pine) and Spock's (Zachary Quinto) personalities that they'd established and threw them out in favor of their Elevator Pitch descriptions: Kirk's brash, and hates authority. Spock follows the rules right up to the zero hour. These features are exaggerated to the point where Spock is a cold, rules-quoting prick and Kirk so disregards authority that it's hard for even the audience to be on his side. Hadn't we moved past this by the end of the last movie?

There's the rub. At the end of Into Darkness, after another threat to Earth has been foiled, the Enterprise finally gets their assignment for a five-year mission. Kirk takes the bridge, and Abrams gives us another sweeping shot of everyone in their places making warm, quippy remarks before warping off into the unknown. We then cut to credits over a planetary backdrop. It's literally the last two minutes of the 2009 version--meaning we'll need to wait another three or four years for Kirk and crew to begin exploring outer space.

Where did this all go so horribly wrong? One word: fandom. The studio and filmmakers faced a crucial junction at the end of their wildly successful first movie. They could have acknowledged the timeline rift and pressed on, establishing that this new iteration of the crew was now definitive and free to have their own unique adventures--or they could have used this as a chance to "tweak" plots from old episodes and not work their imagination muscles too much.

Sadly, they went with option "B". This isn't inherently a crime, because in the lead-up to the film's release, I read a lot of truly great fan speculation as to how Khan might be introduced into this new timeline. But fans didn't write this movie. The folks behind Transformers and Prometheus did. These are people who think that randomly shoe-horning characters and situations from Wrath of Khan into their story qualifies as exemplary craftwork. It's really just catnip for fans with low self-esteem ("Oooh! They referenced Harry Mudd! These guys really get me!").**

Caught up in cleverness, the filmmakers apparently didn't bother to proof-read their script for logic problems. I'll let things slide on a cool roller coaster of a movie, but Into Darkness was built on tracks made of bubble-gum and push-pins. Why, for example, is the audio/video signal between two starships all warbly when Kirk can have a crystal-clear communicator chat with Scotty (Simon Pegg) that reaches from the bridge of the Enterprise to a bar in London? Why is there no aerial or personnel security during a high-level conference with the heads of Starfleet--whose very purpose is to discuss the capture of an escaped terrorist bomber? Why does Dr. McCoy (Karl Urban) need Spock to capture Khan in order to get a blood sample when there are seventy-two unconscious specimens right down the hall from sick bay?

If you go into Star Trek: Into Darkness with your brain working at even half capacity, it will likely feel more like an intelligence test than a movie--which is a shame. I didn't believe (and still don't) the critics of the first film who claimed it was all flash and no substance. It had weight to spare, at least on an emotional level. But the handful of detractors are on the money with this one, and I have no faith that the next chapter will be anything to write home about, either. The darkness is upon us, friends, and there's not a light switch to be found.

*Sorry, this information is redundant to those of you who read my Wrath of Khan review the other day, but I don't want to leave anyone behind.

**Why is Carol Marcus (Alice Eve) on board the Enterprise? Seriously, why?

Thursday
May162013

Star Trek (2009)

Flare and Balanced

For years, a debate has raged on in the geek community as to whether or not J.J. Abrams' big-screen re-launch of the Star Trek franchise qualifies as "Genuine Trek". Many fans of the 1960s television series, its feature-film incarnations, and the myriad TV reboots from the 80s and 90s can't wrap their heads around Abrams' flashy, snarky, guns-a-blazin' adaptation, and claim to know for a fact that series creator Gene Roddenberry wouldn't approve.

I understand where the dissenters are coming from, but I disagree. True, Abrams and writers Alex Kurtzman and Roberto Orci have taken the classic Enterprise crew in a ballsy new direction that hasn't yet aligned with our idea of what these stories "should" be. But they explain themselves quite well, and then set about the business of entertaining a broad audience (broadience?) for two-plus hours.

That may upset the purists, but think of how stunted our collective pop cultural growth would have been if the Internet had been around in 1981:

"How dare John Carpenter destroy Howard Hawks' vision of The Thing From Another World by defiling it with blood and guts! And why did the suits have to go and shorten the title? Must be to appease the stupid masses!"

And on and on.

The essential Star Trek elements are all here. In the twenty-third century, mankind has joined with a number of alien races to form the United Federation of Planets. Starships search the galaxy to discover life forms and find new places to boldly go. The most famous vessel, the Enterprise, is helmed by Captain Kirk and his close-knit crew of big personalities. Abrams' movie begins in the hours just prior to Kirk's birth, during which a cosmic storm ushers in a massive Romulan mining ship from the future.

Kirks' father, George (Chris Hemsworth), sacrifices himself by ramming the ship he's just inherited into the dangerous craft--thus altering the course of history by making the future pioneer an orphan. Steering the Romulan time-jumper is Nero (Eric Bana), a thug with a vendetta against the version of Kirk's first officer, Mr. Spock (Leonard Nimoy), from his timeline.

Got that? Good. 

This disruption allows Abrams, Orci, and Kurtzman to play around with nearly fifty years of established canon. And thank God for that. In the Abramsverse, Kirk (Chris Pine) is a snotty scrapper who hasn't yet mastered the art of not getting punched repeatedly in the face. Spock (Zachary Quinto) and Lieutenant Uhura (Zoe Saldana) are a burgeoning couple, and the planet Vulcan...well, what happens there just plain sucks.

Despite nerd rage over "Dawson's Trek", I love the new series' direction. Abrams balances tear-jerking melodrama (the film's opener gets me every time) with cheeseball comedy that's, frankly, far less eye-rolling than some of the older Trek material (space hippies, anyone?). Not all of it works from a reaction standpoint, but narratively, the gags and gut-punches are mostly solid. Sure, seeing Kirk's hands swell up to cartoonish proportions after receiving a vaccine is ridiculous--as is the swollen-tongue Jar Jar moment he has a moment later--but there's a perfectly good reason for these things.

Abrams and company understand that building a show or a film around space exploration is going to necessitate weird situations that audiences inherently won't appreciate in the same way the characters will. For example, Nero is a really weak villain. Unless you read IDW Publishing's multi-part prequel comic-book series (and, really, why wouldn't you have?), you have every reason to be skeptical about his motivations. He comes across as grumpy, arrogant, and really dumb, but to the Enterprise crew, he's the maniac skipping across the universe in a nigh-invincible ship and wielding a weapon of mass destruction.

Fortunately, we don't spend too much time with him--because he's not the point of the movie. This film's job is to get Kirk and Spock on board the Enterprise and on board with each other. Everything else is superfluous. So, yeah, Scotty's (Simon Pegg) water-park ride through Engineering; the light-hearted rigging of the famous Kobayashi Maru test; and all the fly-throughs of CGI space wreckage are filler in service of giving our heroes something to react against while working out their complicated feelings towards each other.

The one bit of crap I'll give Abrams is the lens flare thing. I honestly didn't notice his over-use of bright, probing lights until recently, and thought the Internet had simply created another reason to hate on the director out of whole cloth. Nope. Turns out, if you even half-notice one, you won't be able to not see dozens more. It's really annoying, but I imagine you could make one hell of a drinking game out of spotting the flare-ups.

Other than that, I don't think one could have asked for a better re-introduction to characters who, to the majority of Americans, were recognizable but also wholly irrelevant. And, no, I don't think Star Trek was dumbed down to play to legions of drooling idiots. It's not 2001: A Space Odyssey, but neither is Star Wars. This is a fun, fierce re-imagining with a lot of heart and style to spare.

If you can't abide Abrams' vision for the series, you're well within your right to cling to the TV shows and movies of yesteryear. But don't ever badger me about the "spirit of Star Trek". To quote The Next Generation's Captain Jean-Luc Picard, "Our mission is to go forward."

Wednesday
May152013

Star Trek 2: The Wrath of Khan (1982)

Age: The Final Frontier

Up front, the moral of this review is, "Don't watch Star Trek 2: The Wrath of Khan when you're tired (especially if you haven't seen it in awhile)." For geeks of a certain age, Nicholas Meyer's 1982 movie isn't just a franchise sequel, it's a pop cornerstone and one of the high watermarks of sci-fi filmmaking. But I put it on the other night and quit after fifteen minutes that I hadn't recalled being so painfully dull.

In fairness, I was really sleepy before pressing "Play".

Last night, I resumed watching it and had an entirely different experience. Perhaps I've become so accustomed to mega-budget, computer-graphics-driven extravaganzas in the last decade-plus (including J.J. Abrams' reboot of this very series) that I'd forgotten about space adventures that took their time--be they for creative reasons, or because technology had not yet advanced to the point where absolutely everything in a writer/director's head could be realized on-screen. Whatever the case, I found Wrath of Khan to be lovely, moving, and headier than it had any right to be.

The movie isn't so much a follow-up to the poorly received Star Trek: The Motion Picture as it is to an episode of the 1960s TV series, "Space Seed". On the show, the USS Enterprise stumbles upon a vessel in deep space containing contains the cryogenically frozen bodies of a race of villainous super-humans. They were exiled from Earth in the late 1990s, at the height of a genetic engineering craze. The crew doesn't discover this until the passengers are reanimated and walking around the ship, of course, and they end up nearly being destroyed by the mutineers' leader, Khan (Ricardo Montalban). Luckily, Captain Kirk (William Shatner) is handy at foiling plots and has a big heart: he deposits Khan and the gang on a lush, green planet where they can start anew--and not spread to other parts of the galaxy.

Fifteen years later, Khan remerges with a vendetta against Kirk and a starship to help him realize his sick dreams. He also gets his hands on a planet-seeding missile known as the Genesis probe, which he plans to...do something with (even Khan's loyal crew don't know what the plan is beyond "Get Kirk!"). Ostensibly, The Wrath of Khan is a protracted game of hide-and-seek between two guys on rival spaceships. I'd forgotten that they never confront each other in person: all of their interactions are over view screens. I don't know if this was an intentional cue on the part of Meyer and writer Jack B. Sowards, but it underscores several of their movie's themes.

The Wrath of Khan's catalyst isn't the madman's revenge fantasy; it's Kirk's birthday. He turns an undetermined age and laments the fact that, with his promotion to Admiral, he has lost the ability to have adventures in space. He's been relegated to inspecting starships. When called upon to take his precious Enterprise on a training mission, he emotes something like nostalgia mixed with boredom. Many of his former crewmembers retain their child-like enthusiasm for exploration, but Kirk is a sarcastic mope who feels trapped by the prestige of his life choices.

Later in the film, he's reunited with an old flame named Carol Marcus (Bibi Besch), who also happens to be the lead scientist behind Genesis. In another nod to the creators' vision for this Trek's focus on maturity and consequence, we learn that Carol's son, David (Merritt Butrick), is also Kirk's kid--whom he'd left years ago to gallivant through space. In what has to be one of the worst long weekends in star date history, our hero finds himself at one point marooned deep inside a rock with his ex and their spiteful, illegitimate kid, while an age-old enemy circles overhead, waiting to kill more of his friends.

Montalban has rightfully become an iconic big-screen villain. His Khan is as close as we're going to get to a legitimate snake-person until human/animal hybrids become a real thing. He's a bit over-the-top in places, especially when bragging about his "genetically engineered intellect", but that's not out of line with the original Trek's style. More important than the man, though, is what he represents: the relentless, crushing pursuit of time.

Kirk has spent his entire career cheating death, screwing people over (and just plain screwing them), and growing his ego into a Gamma Quadrant-sized problem. Khan is a reminder that the past is a living thing that must be reconciled with before one can enjoy the present or appreciate the possibilities of the future. Montalban's a hammy performance, sure, but it's also a pitch-perfect embodiment of the inner, overly anxious voice of regret that has at one point threatened to bury each of us alive.

Denial is a cancer, the film argues, and ignoring it only increases its damaging effects. Kirk learns this the hard way when he loses his best friend, Mr. Spock (Leonard Nimoy), to a radiation meltdown caused by Khan's ship. Fans of the series know that the follow-up movie is called "The Search for Spock", but I still wept like a losing Idol contestant when a frail Spock pressed his hand against Kirk's while making the Vulcan peace sign. By finally coming to grips with death's very real presence in his life, Kirk finds a way to lighten up and enjoy the wonders of his job again.

Speaking of wonders, the effects in this film are simply amazing. The Wrath of Khan's digitally restored blu-ray highlights the practical-effects genius at play in this production. From the animated disintegration of phaser victims' bodies to the submarine-standoff-in-space between Kirk and Khan that takes place in a purple, stormy nebula, everything about this film's visuals shows thought, painstaking care, and real ingenuity.

Many argue that computer animation is hard work. I've come to disagree. It's long work. It's tedious work. But at its core, it still involves sitting in front of computers for hours on end, and maybe, occasionally, having meetings in which more people look into monitors together. The practical effects pioneers of yore sweat over miniatures and destroyed models and sets that would require days (at least) of re-hand-crafting and re-rigging if something went wrong. With rare exceptions, CGI extravaganzas do absolutely nothing for me now, because I know they're packed with essentially risk-free animation. I was filled with more wonder and respect watching the Enterprise leave its docking station than during the entirety of The Avengers.

Geez! Now who's getting old and cranky, huh? The long and short of it is, Star Trek 2: The Wrath of Khan is a legitimately great movie. It worked for me when I was five ("Cool! mind-controlling, armored slugs!") and it means even more to me as an adult ("Maybe I should work harder at keeping up with old friends"). A film with ideas that are bigger and prettier than its imagery is a rare treat, indeed, and if you're paying attention, your heart and mind may boldly go where you never imagined they'd go before. 

Sunday
May122013

The Great Gatsby (2013)

A Pose By Any Other Name

Baz Luhrman is ridiculous. I've long admired him as a visionary director of movies I can't stand, and his latest--a gaudy, parodic 3D adaptation of The Great Gatsby--did nothing to change my mind. Employing the same clown-school mania as Moulin Rouge!, while simultaneously not being a musical, the film also manages to drain all subtext from F. Scott Fitzgerald's seminal American novel while beating us over the head with pseudo-social-messages that only a crack-head would derive from the source material. I read half the book in high school; based on these results, I suspect Luhrman listened to half the Cliff's Notes on Audible while perusing Art Deco Magazine.

I'm all for creative license, but when your framing device hinges on Tobey Maguire as a disillusioned old man in a mental institution--narrating his descent from space cadet to sad space cadet--there's not enough helium on the planet to suspend my disbelief. Maguire plays the novel's narrator, Nick Carraway, as such a squeaky-voiced non-presence that I kept having to remind myself he's A) allegedly a full-grown man, and B) not a corporate prototype for human wallpaper, and C) the doorway to an interesting story.

It's 1922, and Carraway has just moved to New York City (adjacent) to make it big in the booming world of finance. He buys a small house just across the river from his cousin, Daisy (Carrey Mulligan), and her crazy-rich husband, Tom Buchanan (Joel Edgerton). His neighbor is a skulking Bruce Wayne prototype named Jay Gatsby (Leonardo DiCaprio), an impossibly wealthy recluse whose fortunes are as elusive as his presence at his manor's lavish weekend parties. When Gatsby finally reveals himself--after a really, really, really, really, really* long series of extravagant, get-to-the-point tertiary character introductions, he turns out to be a bit of a kook.

Thankfully, DiCaprio makes him a compelling kook. Suave, funny, and guardedly earnest, the actor goes a long way in selling the charms of a character we'll soon come to loathe (if, of course, "we" have any good sense, unlike Mr. Carraway). It turns out Daisy and Gatsby were once a thing, but Gatsby returned from World War I without a penny to his name and felt unworthy of asking his beautiful, old-money princess to marry him. Five years later, aided by a fortune built on bootlegging and market rigging, Gatsby has set up shop across the way from his beloved (he's also modern literature's prototypical stalker, it turns out), and is intent to use Carraway as his opening salvo against Tom Buchanan's marriage.

Luhrman's The Great Gatsby has two major problems, one of which is, I guess, fundamental to the book, and the other draws unhelpful and unintended scrutiny to that fatal flaw. From a storytelling perspective, there's not a sympathetic or interesting character anywhere in sight. This is blasphemy, I know--especially coming from someone who couldn't be bothered to complete or revisit the novel--but everyone in Fitzgerald's world is a fool (if Luhrman's interpretation of it is to be believed, which I don't know that it should be).

Carraway believes Gatsby to be the embodiment of hope and virtue, even as he's stealing brides, operating an empire of illegal booze and fraudulent investments, and covering up vehicular manslaughter. The object of his affection, Daisy, is a vacuous, blubbering, wad of pale taffy that any objective man with standards would just as soon leave stuck to the floor. In fact, the only reasonably sympathetic character here is Tom, who at least acknowledges his vices. Sure, he  may be a cheating, boozing, out-of-touch son of privilege, but when Gatsby forces Daisy to tell her husband that she never loved him (in a silly, drawn-out moment that's sure to net at Gatsby least two Razzies), the look of heartbreak on Edgerton's face sold me on his being the real star of this movie.

I think I've spoken enough about Carraway, and Maguire's "Psst! I'm over here" performance.

There's no denying the sweeping romance of The Great Gatsby, but it's the same idiot love triangle one might find week after week on COPS--which makes Luhrman's telling of it so puzzling. I imagine it will be very difficult for young audiences (let's face it, this thing was made for children) to connect with the bizarre motives, sloppy pining, and dumb decisions made by every character at every turn. Why not be bold with the material, then, and spruce up Fitzgerald a bit? Give Jay and the gang problems that are relatable in any era?

Too difficult, I guess. Yes, it's much easier to just throw digital cheese and a Remedial English student's ideas about what "The Roaring 20's" looked like up on the big screen. Though not as gaudy as Moulin Rouge!, The Great Gatsby is equally sinister in hiding its lack of substance behind noise, flash, and elaborate sets and costumes. Worse yet, everyone speaks in the hyper-corny, old-Hollywood patois that comedians like Patton Oswalt use to ridicule old movies.

In a bizarre twist, many early scenes play out against a hip-hop soundtrack. Ah, yes, there's nothing like listening to Jay-Z rap about empowerment and luxury while watching somber black men serve white fat-cats lunch.

I highly recommend skipping this movie and checking out one of 2011's overlooked gems, The Rum Diary, starring Johnny Depp. Fans of Hunter S. Thompson know that he was a huge fan of Fitzgerald's Gatsby (one of his earliest writing exercises was to type out the entire book to get a feel for the author's rhythms). The Rum Diary is Thompson's Gatsby: the early work sat in a drawer for decades and features a similar, troubled trio fighting for love and purpose in 1950s San Juan. It's got substance, heart, beautiful (natural) locations, and a protagonist who won't make you want to chug a Red Bull.

Wrapping up the review at hand, The Great Gatsby is like George Lucas' Star Wars prequels: technologically amazing (I guess), well-acted (enough), and brimming with the illusion of time worthiness. But there's nothing here that warrants spending two-and-a-half hours with these moneyed morons in a theatre. You'd be better off with the book--or so I've read.

*Sorry, I just had a flashback to my Great Gatsby book report.

Friday
May102013

Something in the Air (2012)

The Air That I Breathe

Yesterday, I worked thirteen-and-a-half hours at my day-job. Artist by trade, film critic by night, mine is a life the eighteen-year-old version of me would have probably loved--unless I were to map out the gruelling realities of making it in the professional (i.e. corporate) world.

Long ago, I traded acrylic-paints for e-mails, and day-long ink-drawing sessions for meetings about projects I won't remember next month--let alone on my death bed. I'd never share this information with him/me, if given the chance, because he/I probably would jump in front of a city bus mid-discussion.

There's nothing romantic or world-changing about what I do every day, unless you want to get all Dr. Phil on me about little differences amounting to big things. I suppose that's true, but it's little comfort when I stumble home, exhausted, five minutes after my son goes to sleep.

What does any of this have to do with Something in the Air? Everything. Olivier Assayas' casually moving, beautiful film about French high school students/revolutionaries in 1971 breathes the fire of creative youth. Gilles (Clement Metayer), a sullen, shaggy-haired artist, falls in with the activist kids in his class. His ideals aren't so much political as they are expressive: by raging against Communism, Fascism, and every other vague "ism" that his more bookish compatriots think will look sufficiently menacing on the front of their mimeographed underground paper, Gilles finds the inspiration to paint wild pictures and bed social-conscience groupies.

The movie opens with a protest that descends quickly into a horrifying episode of police brutality. The police don't just warn the teens to disperse. They run each of them down, doling out gleefully savage beatings with big, black clubs. Gilles and his friends Alain (Felix Armand) and Christine (Lola Creton), escape the mayhem, but conspire to pull off a grand act of vandalism in retaliation. The next evening, they deface the front of their school before being run off. On returning for yet another round of graffiti art, one of their pursuers is accidentally knocked on the head and lapses into a coma.

Another student takes the blame, but the three friends decide to lay low in Italy over the summer. Christine runs off with the head of a documentary film crew; Alain falls for spaced-out American hippie Leslie (India Menuez); and Gilles grapples with a romantic interest in Christine, a lingering love of his druggie ex, Laure (Carole Combes), and conflicted feelings about going to work for his TV-producer father after graduation. These events comprise Something in the Air, but I hesitate to call them "plot elements".

Assayas isn't interested in forward momentum here. In this way, his film is a perfect metaphor for the uncertainty most of us faced when transitioning from childhood to adulthood. Gilles and his friends find no easy answers to their problems; their Earth-shattering ideals are of little use in the real world. That's to say, it's far easier to dedicate hours to feeding starving children when your own needs are taken care of through no effort of your own. Adulthood is the necessary evil these characters must reconcile with, and they are in no hurry to do so.

Please don't mistake this for a heavy European art film. I mean, it kind of is, in theme. But in execution, Assayas captures the easygoing luxury of long afternoons spent painting, screwing, and listening to great music--all the while knowing that lively conversation and beautiful French countryside views are just a window-crack away. He punctuates this with moments of great drama and consequence: the riot, an exploding car, and one of the greatest mind-fuck house fires I've ever seen. These jarring scenes create empathy with the characters, who just want to escape the noise the real world keeps blasting at them.

Had Something in the Air not made me question a number of decisions I've made in my own journey from wide-eyed world-conqueror-in-training to a manager of artists, I'd probably proclaim my love for it. But the movie depressed me a great deal, precisely because it's so spiritually uplifting. Yes, Gilles and his friends wind up tiptoeing into adulthood (and it's unclear how many of their ambitions and creative ideals will survive the long haul) but Assayas leaves us with hope for them and for ourselves.

Our passions, the writer/director argues, may flicker, fade, or even change color. Sometimes, they'll swell beyond our ability to control them. It's a refreshing message. And despite these long, hard, seemingly unrewarding days, I'll never stop tending my fire.

Hey, Chicagoans! If you'd like to experience the mood and magnificence of Assayas' film on the big screen, head on out to The Music Box Theatre on Southport this week, where Something in the Air opens today!