“True Detective” thoughts, Season Two, Episode Two: “Night Finds You”

Let’s get a little Rust Cohle-ish for a second: There’s a theory among physicists that any event with multiple possible outcomes is essentially a root from which parallel universes grow. If you’re reading this recap, for example, you probably decided to watch True Detective tonight — instead of, say, playing World of Warcraft, or writing to your congressional representative about the cancellation of Hannibal. But according to the “many-worlds interpretation” of quantum mechanics, the timelines in which you leveled up your orc mage or explained the twisted relationship between Dr. Lecter and Special Agent Will Graham to a member of the House Ways and Means Committee are just as real as this one.

Tonight, True Detective 2.0 itself reached a multiversal branch point. Either it killed off its top-billed main character in its second episode, thus crafting the quickest course correction in TV history, or it didn’t, creating one of the most obnoxious bait-and-switch cliffhangers ever. This makes Colin Farrell the TV-antihero version of Schrödinger’s cat — simultaneously alive and dead, at least until next week. Time may be a flat circle, but it’s sure-as-shit better to be on one side of the interdimensional disc than the other.

Did True Detective just do what it looked like it did? And does it matter? I tried to answer these questions for Rolling Stone.

Tags: , , , ,