Showing posts with label star trek iv the voyage home. Show all posts
Showing posts with label star trek iv the voyage home. Show all posts

Wednesday, February 11, 2026

The single point of genesis of my two favorite Star Trek movies

And the word "genesis" is chosen intentionally, as you will see.

But first some background on why I just read a book about one of the most beloved epsiodes of television of all time, why there's an incredible controversy about it, and why it fits appropriately as a post in my movie blog.

You may recall I told you last year that I wanted to read more about films. Sure, reading is a time I cherish for specifically not doing movie-related things. But reading about films is also part of deepening your love for/knowledge of the movies. So last year I vowed, at least in the short run, to read a book about movies or filmmaking as every second book I read, starting with Quentin Tarantino's Cinema Speculation, which I read in November and December and wrote about several times on the blog.

So after reading Haruki Murakami's The Wind-Up Bird Chronicles in January, I turned my attentions in February to a project I'd been putting off.

Last year, an old friend sent me the book you see above, as well as a graphic novel depiction of the same controversial Harlan Ellison episode of the original Star Trek series, "The City on the Edge of Forever." He also sent me a Red Sox t-shirt that is in my regular rotation, since he's a lot more Star Trek than Red Sox. 

All three items were appreciated, but the two Star Trek ones seemed like they could cause me a headache. 

See, a few months ago I started to read the book you see above, and it starts with Ellison basically in the middle of a diatribe whose beginning I had not heard. Ellison, you see, was not only a legendary science fiction writer, but he was also legendary for his belligerance and argumentatitve nature. This did not just make him a boor; it appears that his friends cherished him, and he had many professional relationships that were cordial. But he didn't suffer fools and he rarely kept quiet about something that bothered him, or at least, not "forever." (He was sitting on his "City on the Edge of Forever" gripes for something like 30 years before spewing them all here.) Anyway, the tone of the rage-filled rant, which eviscerates people like Gene Roddenberry and which had not (initially) provided me the sort of background context I'm trying to provide you here, caused me to set down the book and save it for another day. 

The basic background here is that Ellison submitted a script for the 28th episode of the first season of Star Trek that, according to Gene Roddenberry, could not be filmed. Having read the teleplay, I'm inclined to agree. There's so much plot in this one episode that it was better suited to being a feature film, not a single 48-minute episode of television. 

Did Roddenberry et al make gutless decisions in rewriting the teleplay so it would fit into their standard allotment of screen minutes and their standard budget? I'm sure they did. And I'm sure everyone who took a pass at the script -- which seems to have been about 13 people -- was a less talented writer than Ellison. But then they took more credit for it than Ellison thought they should, especially as they sprinkled their discourse about it with disparaging comments about him. 

Well, the episode was a success in two very specific ways, or three, if you consider its legacy. In the moment, the episode won an award both for the televised version, and the teleplay that Ellison submitted for consideration -- even though those two things were quite different. Its legacy? "The City on the Edge of Forever" edges out "The Trouble with Tribbles" to be considered the favorite episode of the original series, any time a vote is taken about this sort of thing.

The plot? I'll give you that as well. Kirk and Spock must go back in time to the U.S. of 1930, following a troubled Enterprise crewman who is escaping the rest of the crew and whose presence in 1930 is going to alter the course of the future beyond all recognition. While there, Kirk falls in love with a woman who, in space-time terms, is a focal point of this point in history, and who must die in order for the future to proceed as it has. Ironically, it's the troubled crewman who is trying to save this woman, while Kirk must let her die.

Heady stuff. Much headier in Ellison's script than the pallid facsimile we get in the TV show, though of course, this also became the favorite episode of the entire series, so they had to be doing something right. They couldn't have known, at the time, how much better the episode would have been with more of Ellison's original ideas intact, but then again, that would have been twice the length. (When the graphic novel version of it was made, it was made into five separate comic books, which tells you a little something about its length.) 

I'm writing this post for two reasons: 1) I need to get something up on my blog after leaving you with a rant about racism at the movies three days ago, and 2) I want my friend to read this as my reaction to reading the book and the graphic novel, and then finishing it off with my first-ever viewing of "The City on the Edge of Tomorrow," which I did last night after buying it on AppleTV. So I may at this point shift to not clarifying everything I'm talking about as I address my comments more to him, though we'll see how that goes. The journalist in me demands to provide context at every juncture. 

So yes, it's quite clear that Ellison wrote a very thoughtful treatment in which the bad seed on the episode is a drug-dealing Enterprise crewman (not a poisoned Dr. McCoy, as he turned out to be on TV) and there's a lot more of interest in the scenes of Earth of 1930, which take place in an unspecified American city. His vision of the planet with the time portal, which gives the episode its title, is undeniably more grand, but that's where the budgetary restrictions of a show with a weekly production schedule come more into play. In any case, the graphic novel is a glorious realization of Ellison's every hope for the episode, and on this occasion he is inclined to offer plenty of praise, as he says he was "over the moon" for how they conceived of his words in the artwork. 

And it's true that very little of that survives on the show. In fact, there are points where it feels like they could have used some of Ellison's original turns of phrase or other dialogue, because the stories are similar enough, but they deviated from those words more out of spite than actual necessity. So that gives credence to some of Ellison's charges that Roddenberry and others were acting in bad faith, though I suppose it also gives credence to the idea that Roddenberry and others bore a greater responsibility for what was actually on screen -- and this is the notion that perturbs Ellison the most. 

I do think it's funny that there is such a controversy over this episode, because often controversies, especially those resulting from tampering with the creative process, are the result of something that failed spectacularly. "The City on the Edge of Forever" was a spectacular success, by any measure. So I think that's what initially struck me as obtuse about Ellison's complaints. Can't everyone just be happy that a really good Star Trek episode resulted from this? They all get dragged down by the "success has many fathers" nature of the controversy. Just be glad it was a success, I think.

But watching the episode, especially after already reading four treatments of Ellison's material across the two books, it does seem very puny by comparison to what Ellison wrote. Surely it needed to be streamlined, but within that, you can see the lack of courage in the decisions. Ellison wanted Kirk to approach doing the wrong thing, or actually not be able to do the right in the moment and need to be saved by Spock. In the completed version, Kirk does do the right thing, and we don't even really see any emotional aftermath of it. 

The thing that I find really interesting about this whole thing, though, is that fans had to already love the episode to even get to this point of there being a controversy and there existing an unexpurgated version of this story. My friend introduced this to me as the episode that made him love Star Trek, which is funny, because I am coming at it from the angle that the episode is pretty weak compared to what Ellison wrote. Then again, this is just part of my theory that you like the first version of something you encounter the best, a theory that usually applies to songs. For example, if you hear the remixed version of a song first and fall in love with it, you will not like the original, even though without the original the remix would not exist.

I wonder if I would have felt differently about it if I'd watched the episode first, and maybe my friend assumed I was already familiar with it. Maybe then I would have been attached to the decisions on the show and found Ellison's choices perverse. Then again, I suspect most people who love Ellison's take had already seen (and loved) the televised version, yet still had a place in their heart for his original version. Me, I'm a Star Trek fan, have been since The Wrath of Khan. But interestingly, I've only seen a couple of the original episodes all the way through. I just didn't watch the show at the time -- obviously, I wasn't alive yet -- and never went back to it over the years, even though I love these characters and the movies they're in, and even though reruns were surely available on television stations I had access to as a kid. 

Although I have a clear preference for Ellison's version, I do want to acknowledge something that I thought the episode got right that Ellison got wrong. And here we get into the stereotypical Trekkie complaints, the kind William Shatner lampooned when he was on Saturday Night Live, that get way too into the weeds. But they're weeds that I think Ellison would respect.

In Ellison's version of the story, the time disruption caused by the drug-dealing crewman Beckwith, when he goes back in time, results in significant changes to this version of the universe. But not so significant there is not still a ship sitting at the exact coordinates of where the Enterprise was when the crew beamed down to the planet, and is, in fact, actually the Enterprise itself -- just manned by a pirate crew. It would be reasonable to argue that if Beckwith had caused a permanent rift in time, not only would the Enterprise not be in that exact space at that exact time, it might not exist at all. (Ellison would probably have an explanation for this, maybe that the renegade crew/pirates constitute a visual representation of an altered universe, containing the ring of truth if not actual plausible scientific truth.)

In the TV show, the Enterprise is, in fact, gone. The crew that are with Kirk and Spock -- which includes Uhura, who utters the cringe-worthy line of dialogue "Captain, I'm scared" -- are stranded on the planet, rather than stranded on the Enterprise with a crew of renegades. At least the Trekkies who thrive on pushing their glasses up the bridges of their noses can appreciate this more believable outcome. (Of course, if we were going full Back to the Future, then probably they would all just vanish from existence -- but then you wouldn't have an episode.)

Because he didn't tell me, I'm not sure exactly why my friend was convinced of his love for Star Trek by "The City on the Edge of Forever," but I can tell you why it would have convinced me, even if I have to retrofit an explanation that might not have made sense if I'd first encountered the episode years ago. And here now we finally get to the two movies I referenced in the subject of this post.

"The City on the Edge of Forever" features primary components of both Star Trek II: The Wrath of Khan and Star Trek IV: The Voyage Home, far and away the best of the original six Star Trek movies. And those two components nourish two different parts of the brain of the devoted Star Trek fan. 

Let's start with the fun one.

There's a decent argument to suggest that without "City on the Edge of Forever," Star Trek IV would not exist, or not in its current form. Talk about time-related causalities. 

The Voyage Home involves a return by the Enterprise crew (though not the Enterprise itself) to present-day San Francisco of 1986, the year the film was released, in order to acquire a humpback whale to prevent future Earth from being desiccated by an alien craft trying to make contact with the (now extinct) whales. As notably the only movie in the series where "comedy" is an appropriate genre, the film relies heavily on the rapport between Kirk and Spock as they try to blend in with the San Franciscans, much of it very funny. The rest of the crew are there, on different missions and also blending in, but Kirk and Spock -- and a present-day love interest for Kirk -- are sequestered on their own mission. 

That this features the essential fundamental dynamics from "City" is no accident, though it should be noted, the Voyage Home version of Kirk and Spock do not appear to remember their previous trip to 20th century America. I think we're meant to take this as similar to the James Bond movies, where we don't really believe that this James Bond has had all the experiences of the previous James Bonds -- though the fact that Kirk and Spock are played by the same actors does make this problematic.

For me, this movie came along at the perfect time, as I was still high off of wrestling with the time travel conundrums presented to us in Back to the Future the year before. And while there are not quite so many "if you change this, then this" moments in The Voyage Home -- no one is fading in and out of existence, for example -- it still delves deep into the problems of being in an earlier time period, including the fact that things you need to get back home haven't been invented yet. That's also a plot point in "City," I should mention, as well as Back to the Future. Although Ellison says The Voyage Home was one of about four Trek movies he was approached to write, he didn't write it -- though his fingerprints are all over it. This is certainly the more "Roddenberry accessible" version of a thing Ellison might have written, especially since it gives Kirk a happy ending with the girl.

And this is just the "fun" part of Star Trek. Sling-shotting around the sun in order to travel back in time. Building a tank on a Klingon vessel (remember, the Enterprise blew up in the last movie) in order to transport a whale. Scotty trying to talk into a mouse to address the computer. It's great stuff and I get a grin on my face just thinking about it.

But "City" also has the much more serious theme at the heart of The Wrath of Khan, not to mention its band of renegades, Khan's crew, who were first envisioned by Ellison in his version of the "City" teleplay.

I don't suppose I need to give a spoiler alert for The Wrath of Khan, seeing as how it turns 44 years old this year, and seeing as how I didn't avoid spoiling that Kirk gets the girl at the end of The Voyage Home. But here is your Star Trek II SPOILER ALERT anyway.

So you know that after a ripping yarn about a mano-a-mano space battle between Kirk and Khan, during which Kirk is also grappling with his own mortality and the surprise of being in close contact with his estranged son, we get the gut punch of the death of Spock. It's not a permanent death, of course -- you already know, because I've told you, that he was in Star Trek IV. We have the Genesis planet to thank for that, and now you see why I included that word in the subject of this post. A weapon of either ultimate creation or ultimate destruction gets fired at a nearby barren planet, which quickly becomes verdant and teeming with life -- and which is where Spock is ultimately "reborn," a saga that continues throughout Star Trek III, which is of course subtitled The Search for Spock. (And one of the reasons The Search for Spock conforms to the Trek rule of thumb that the odd-numbered movies are not so good, is that the regrowth of Spock into an adult is never not weird and is always wobbly in its execution.)

But at the time Khan came out, we couldn't know for sure that this was not the end of Spock. Maybe Leonard Nimoy wanted out of his contract or something.

Anyway, Spock must expose himself to untold amounts of radiation to help save the Enterprise crew, which he does, knowing it will be the end of him. His death scene, one of the more emotional out there, contains this famous line: "The needs of the few outweigh the needs of the many ... or the one."

Which is pretty much the thesis of the sacrifice of Edith Keeler in "City."

Kirk has the chance to save her, but he knows that it will mean either the loss of the Enterprise entirely (on TV) or the loss of the crew to a band of renegades (in the teleplay), which amount to the same thing, for all intents and purposes. And though in the show we don't know if this version of the universe is worse -- we just know the Enterprise is no longer there -- in the teleplay we know that renegades run amok in the galaxy, avoiding punishment and spreading evil.

And so yes, the needs of the many outweighed the needs of the one. Outweighed the needs of Edith Keeler, but also outweighed the needs of James Kirk.

So yes I'm glad to have spent this time with "The City on the Edge of Forever," even if Harlan Ellison created a very difficult entry point at first with his spewing of bile at the already dead Gene Roddenberry. (And to be fair, he did castigate himself every time he did this because you're not supposed to speak ill of the dead.)

I am convinced that his version of the story is better, but both versions contribute wonderful things to our culture, and both versions helped make my friend a Star Trek fan. So I'm glad both versions exist.

And as a last comment, seeing the teleplay and then seeing the TV show give me a great glimpse into the creative process, which is what makes this another invaluable part of my project of reading about film. Any script undergoes great changes before it ends up on screen, whether it's a TV script or a movie script -- and this exercise gave me a greater appreciation of just how complicated that process can be. 

Monday, September 6, 2021

An artificial intelligence echo

I watched four movies on a projector in my garage yesterday for Australian Father's Day, and I may be able to get two posts out of it. Actually three now that I think of it. Which is good, because I've been in a bit of a creative slump lately when it comes to this blog.

The first one has to do with a coincidence, and it's a lot more interesting of a coincidence than the coincidences I usually waste your time with.

How about a full half of the four movies containing a computer that asks someone how they feel?

The first one might not surprise you: John Badham's 1983 classic WarGames, which is currently #32 on my Flickchart. An obvious all-timer for me.

The second wouldn't have been something I even thought of until the moment in question actually occurred in the movie. That's Star Trek IV: The Voyage Home, another top 100 film on Flickchart (#85) that I hadn't seen in way too long.

When David Lightman (Matthew Broderick) first finds the back door password to log into the WOPR, otherwise known as Joshua, the interaction begins with the question "How are you feeling today?"

It surprises Jennifer (Ally Sheedy), who asks how a computer can ask that. "It'll ask you whatever it's programmed to ask you," David offers helpfully.

The echo in Star Trek IV was kind of astounding. You may recall that before he leaves Vulcan following his rapid regrowth on the Genesis planet (events covered in Star Trek III), Spock (Leonard Nimoy) undergoes a computer assessment of his mental acuity. He nails the answers to such rapid-fire questions as "What is the molecular formula of yomium sulfide crystals?" and "What is the electronic configuration of gadolinium?", but this one stops him dead in his tracks:

"How do you feel?"

And then, because he doesn't respond:

"How do you feel? How do you feel?"

His (human) mother comes in to try to contextualize this part of the assessment that Spock cannot compute, and it leads to a discussion of how his crewmates acted in opposition to their own collective interests when they risked so much to retrieve him from Genesis. 

"Humans make illogical decisions," says Spock.

"They do indeed," says his mother.

The reason I include that last part is that it is also an echo of WarGames. When Joshua asks David, who has logged in under the profile of Stephen Falken, to offer an explanation for the reports it received that Falken was dead, David types in:

"People sometimes make mistakes."

Joshua, in his perfectly creepy synthetic voice, responds "Yes they do."

I'm glad to report that the viewings firmly reinforced these films' entrenched position in my top 100 of all time.

The movies shared some more minor things in common, like both involving U.S.-Russian relations regarding nuclear material, both ending on scenes of cheering control rooms, and even both featuring scenes involving spilled garbage cans. But I won't bore you with those today.

More on my Father's Day mini-marathon tomorrow.

Tuesday, March 24, 2015

Picking over the bones of another video store


When I first arrived in Australia, I described it to a friend back home as "kind of like the U.S. in the 1990s."

This is not to say that most things are backward or particularly behind here. In fact, certain things -- like the ease of paying for goods, where you can sometimes just tap your card against a screen -- are a bit ahead of the U.S. Rather, what's old-fashioned is the quaint ongoing viability of certain things that have long since fallen by the wayside in the U.S.

Pay telephones, for example. It's easy to find a pay telephone here in Melbourne. They are few and far between in the U.S., but they are still plentiful here, still a resource that provides a useful service to the public.

Book stores? Don't get me started. You can't go a city block in almost any part of the city without tripping over a book store. And the price people will pay for books -- even used books -- is absurd. I'm sure people have their kindles and their iPads, but by and large, they still love reading a good old paperback or hardcover book.

And video stores?

Well, it looks like the times are finally catching up with Australia in some respects.

Until recently, I had two video stores that were equidistant from my house. The one I regularly frequented -- well, on $2 new release Tuesdays, anyway -- was called Video Ezy, and then Network Video. The other I've never even set foot inside, because a phone called told me they didn't have any equivalent to $2 Tuesdays.

Well, I'm going to have to learn what deals they do have, because Video Ezy/Network Video is no more.

My wife broke the news to me about a week back. She'd received a text, apparently, that they were going out of business and that everything was on sale. Why I didn't receive this same text, I don't know -- they texted me once when they thought I didn't return a movie on time, which turned out to be their error. Since then, they must have lost my number.

So I planned to go there on Wednesday, to pay my last respects.

Except it was closed on Wednesday. From now until April 2nd, when it shutters for good, it will only be open Thursday through Sunday. Which I can certainly understand, since they're not renting anything anymore, only clearing out the remaining unsold inventory.

I made sure to return this past Saturday, this time with only the older of my two sons in tow.

And I guess my purpose was not so much to thank Video Ezy for all the good times -- it had always been a pretty lame video store, if I'm being honest -- but rather, to figure out which movies I could buy on the cheap.

So though I do still recognize the passing of each remaining video store that closes with a bit of sadness, now the inevitability of the event has adjusted my perspective. This new version of me doesn't dwell on the sadness. Instead, apparently, this new me tries to dig in and find deals.

I instinctively avoided the new release wall, because a) those movies were selling for $7 instead of $3, and b) I don't necessarily want to buy movies that have just come out on video, since they aren't the kind of old favorites I typically add to my collection. (The good titles had been picked pretty clean by Saturday, anyway.)

It's an interesting challenge, to choose titles from a whole video store that's separated out by genre, and know that pretty much everything is affordable. There were still a couple thousand titles available, so it wasn't like I was down to just the dregs. My idea was to look extra hard at the comedies, because those tend to be the ones with the most repeat watchability (and the ones my wife is most likely to repeat watch with me). I gave cursory looks at the other sections as well, but came away with more comedies than anything else.

Having not bought a movie in more than year, I thought I could go a little hog wild. So after circling the store for about 20 minutes, coming up with an initial pile of purchases about twice this size, and driving my son to the brink of boredom-inspired insanity, I came away with the following seven titles:

Seen this twice, but the second viewing was probably four years ago. My wife likes it too, so we'll probably throw it in within six months.


Really liked this one and have only seen it once. Also, I don't know if my wife has seen it yet, and it's right up her alley.


Comments for Cedar Rapids are pretty much ditto for this.


I've already seen this twice, but it's been more than three years since my last viewing. My wife doesn't like this as much as I do. Then again, I don't think anyone likes this as much as I do.

Okay, leaving the comedies behind now ...


Did I say "leaving the comedies behind"? I should have waited one more movie before saying that. The funniest Star Trek is in my top 100 of all time, and I haven't seen it in forever.


My favorite movie of 2005. I may not have a burning desire to see this again, having seen it again about five years ago, but I couldn't pass up the opportunity to own one of my #1 ranked movies. This was the last to make the cut.

And finally ...


I've seen this movie three times already and it only came out in 2013. Obviously I love this movie and need to own it.

Some that didn't make the final cut: Private Parts, Go, Headhunters, Philadelphia, a few others I can't remember. These are movies I like or in some cases love, but I just couldn't quite pull the trigger, either for repeat watchability reasons (Philadelphia) or having just seen them recently reasons (again, Philadelphia). Besides, that was $21 worth of movies, and I still had to pay another $10 for two videos my son wanted -- which were priced at $5 apiece because they were brand new.

So while I'm sad that another chapter is closing in the way we watch movies, at least I can salve my wounds with seven nice new additions to my video collection.