Why 'Drunk History' Will Never Get High

By Max Godnick

Don't expect Comedy Central's "Drunk History" to capitalize on the cannabis legalization movement.

"I wanted the show to be a half hour, not three hours," said Derek Waters, host and creator of the Emmy Award-winning comedy, in an interview with Cheddar.

The series returns Tuesday night for the second half of its fifth season with more celebrities drunkenly recounting historic events. Waters said making the new season took sixty three weeks, with months of research and hours of drinking ultimately resulting in a series of five-minute segments.

Waters said he's thought about the idea of a marijuana-themed installment of the show, but "Drunk History" won't be getting high anytime soon.

"My fear with marijuana would be, it would all be theories," Waters said.

"Drunk History" started as a web series in 2007 and has spawned over fifty episodes and specials since. Waters has developed a good sense of what types of alcohol lead to different storytelling styles.

"Beer makes you talk about stuff that happened to you personally ten years ago that doesn't matter," he said, adding that wine puts people to sleep and tequila makes people crazy. Waters's favorite spirit is bourbon, because it makes people feel like they're the smartest person in the room, something he says leads to the best episodes.

Something that might not make for a good episode? The current administration.

Take, for example, President Donald Trump's recent summit with North Korean leader Kim Jong Un. While cable news was quick to label the meeting as "historic" even before either man set foot in Singapore, Waters said the event wouldn't fit his show.

"It's too real, I like stuff that's from a long time ago," he said. "It's easier to laugh at."

Waters did say there's one factor that could change his mind on the issue, noting he'd be open to Trump-themed episodes, "as long as there's an ending."

For the full interview, click here.

close
We use cookies and similar technologies on this site to collect identifiers, such as IP address, and cookie and device IDs as described in our Privacy Policy.