There are myths in modern Hollywood, stories that get passed around that you want to be true, but you kind of know they’re almost too cool to be accurate. One of those involves James Cameron, the iconic filmmaker behind The Terminator and Titanic, who also took on the unenviable task of creating a sequel to Sir Ridley Scott’s own masterpiece, Alien. The way that the story goes, Cameron – brimming with confidence and his signature brand of swagger – took a meeting in front of a room full of corporate suits. He wrote the word “Alien” on a board. Then he pluralized it, making it “Aliens” and insinuating he was about to up the ante on this planned sequel. Finally, he drew two lines through the S he had added, turning it onto a dollar sign.
We had a chance to sit down and interview James Cameron on behalf of a new book he has coming out titled Tech Noir: The Art of James Cameron. In the collection, we get an historical representation of Cameron’s hand-drawn storyboards, covering everything from his early Avatar ideas to his work on Aliens. And during the conversation, we had to ask him, is that Aliens story real? To which Cameron replied to CinemaBlend:
James Cameron got a kick out of reliving that moment, knowing the hubris that it took to pitch a sequel to Ridley Scott’s movie and all but guarantee another blockbuster success. Cameron’s wiser now, and as he elaborated to CinemaBlend:
As Jim Cameron says, it worked. Aliens is a different beast than Alien, but those two opening chapters remain the best in that franchise, and helped catapult Cameron to stardom. The director, in addition to promoting the fantastic book Tech Noir, is hard at work on his next Avatar movies. It’s a shame part two isn’t titled Avatar$.
Managing Director at CinemaBlend. ReelBlend cohost. A movie junkie who's Infatuated with comic-book films. Helped get the Snyder Cut released, then wrote a book about it.
Your Daily Blend of Entertainment News
Thank you for signing up to CinemaBlend. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.