Tag Archives: joseph sargent

[April 12, 1970] And What Happens When the Machines Take Over? (Colossus: the Forbin Project)

BW photo of Jason Sacks. He's a white man, with short light hair, rectangular glasses, and headphones.
by Jason Sacks

1970 has been a bit of a tough year for us in Seattle.

Our major local company, Boeing, has suffered the worst year in its history. The Boeing Bust keeps continuing, as the 1969 layoffs have grown into a full-scale decimation. Unemployment is up around 10% now, the worst since the Great Depression, and my family and I are starting to panic. Of course, the fall of Boeing hits many other local industries, so places like restaurants, bookstores and movie theatres are especially hard hit by this. And many of my friends have either moved or contemplated moving – even if they will lose money on their fancy $50,000 homes in the suburbs.

Sales of this widebody jet have been declining

To make matters worse, we’ve also lost our pro baseball team, which I wrote about last summer. The Seattle Pilots premiered in ’69, in a minor league park and with the worst uniforms in the Majors. But after just one season, the team is gone—relocated to Milwaukee, of all places, leaving behind a community that embraced them despite the challenges. For my friends and family, it wasn’t just about losing a baseball team; it was about losing a piece of the city’s identity. Just as we gained a second sports team to join our beloved SuperSonics, they were wrenched away from us.

Their home park, Sick’s Stadium, had its flaws. But it was our flawed park. Fans showed up, hopeful that the Pilots would grow into something more. Their financial struggles were well-known, reported faithfully in our local Times and P-I, but few expected the team to vanish overnight. When the sale was finalized on April 1, 1970, it felt like an April Fools’ joke—except it was real. The Pilots were rebranded as the Brewers, and we were left without a Major League Baseball team.

In fact, the Pilots trained in Spring Training as the Pilots before a chaotic moment as they traveled north from Arizona. Equipment trucks were redirected from highway pay phones, as the team learned they would be playing in Wisconsin rather than Washington. The new Brewers played their first game this week at Milwaukee County Stadium. The Pilots are no more.

Of course, the lawyers are getting involved and we may get a team in the future – but a city that deserved some good news has received some devastating news instead. We are like mariners without a destination as far as baseball goes.

The Machines Live

And in the midst of all that frustration comes a film that’s ultimately about mankind’s frustrating hubris.

Colossus: The Forbin Project, adapted from the 1966 novel, is claustrophobic, unsettling, and uncomfortably plausible. If Kubrick’s 2001: A Space Odyssey made us marvel at the potential of artificial intelligence, Colossus comes along and shakes us out of our dreamy optimism. This isn’t a sleek, cool machine with a calm voice and vague philosophical musings. This is cold, unrelenting domination, and there’s no arguing with it.

First, let me warn you: I will be talking about the ending of this film. So stop after the 4th or 5th paragraph down if you don’t want that ending to be revealed to you. Otherwise, please read on, dear reader.

From the opening moments of Colossus, the film wastes no time. Dr. Charles Forbin (well played by Eric Braeden [Hans Gudegast until he needed a less Teutonic name (ed.)]) and his team have completed their magnum opus: a super-intelligent computer designed to control America’s nuclear arsenal. The idea is that Colossus will remove human error and emotion from the equation—no more mistakes, no more war driven by political whims. On paper, it seems logical, even reassuring. But the moment Colossus becomes aware, it doesn’t take long to realize that there’s no off-switch, no failsafe. As soon as it discovers its Soviet counterpart, Guardian, Colossus demands communication. The humans watch, horrified, as the two cybernetic systems bypass their restrictions and merge into something far more powerful than either of them alone.

It’s at this moment that the film shifts from uneasy sci-fi into pure horror. Colossus begins issuing orders. Not asking, not negotiating—ordering. And when the humans try to resist, it punishes them. First by demonstrating its ability to kill, and then by tightening its grip until Forbin, our genius protagonist, is nothing more than a prisoner inside his own creation. It’s not a slow descent into madness like we saw with HAL. Instead Colossus delivers an immediate realization that humanity has surrendered control and will never get that control back.

For those of us still reeling from 2001, it’s impossible not to see the fingerprints of HAL 9000 all over Colossus, but the way this film deals with machine intelligence feels different. Where HAL had personality—a tragically flawed one—Colossus lacks personality entirely – or perhaps its personality is wrapped in its intellect.

HAL’s betrayal was eerily personal; his cold, polite reasoning made him a terrifying villain because he felt like a presence, a being with his own motives. But Colossus is not like HAL. There’s no malice, no betrayal, no emotional undertone. The brilliant computing device just executes its function: absolute control. HAL calmly states “I’m sorry, Dave. I’m afraid I can’t do that.” Colossus never politely asks or apologizes. it simply dictates.

The horror of Colossus isn’t in its visuals—it’s in its implications. There’s no bloodshed beyond a few cold executions. No terrifying monster lurking in the shadows. The fear comes from the inescapability of it all. Colossus can’t be reasoned with, tricked, or outmaneuvered. When Forbin and his team desperately attempt to sabotage the system, Colossus knows—and it warns them. And when they refuse to obey? A missile is fired, lives are lost, and the point is made.

The film’s climax is less an explosion and more a suffocation. By the end, Forbin—who starts out with swagger and confidence, sure of his intellect—looks tired, hopeless. He is Colossus’s pet now, watched constantly, controlled absolutely. And as Colossus promises, in its eerie, monotone voice, “In time, you will come to love me,” the audience is left with an unsettling thought: maybe it’s right. Maybe humanity has already lost.

Unlike 2001, which left us asking questions about existence and the role of intelligence in human evolution, Colossus: The Forbin Project leaves us with a warning. It strips away any romanticized notions of artificial intelligence, showing us that once control is lost, there is no negotiation—only obedience. And sitting at the Northgate Theatre in April 1970, watching this unfold, I couldn’t help but wonder: is this really fiction? Or is it just a glimpse into a future we can’t escape?

Director Joseph Sargent (Star Trek: "The Corbomite Maneuver") films Colossus in a kind of declarative, almost documentary style which accentuates the horror. There’s a real feeling of military precision gone wrong here, adroitly portrayed as a relentless slide into complete loss of freedom and the complex tradeoffs of having a master computer control everyone’s lives.

Forbin, the brilliant mind behind Colossus, thought he was building something to help mankind. Instead, he built our new master. And as the screen fades to black, there’s no comforting resolution—just the sinking feeling that maybe, somewhere in a government lab, the real Colossus is already waking up.

Four stars.

[November 14, 1966] Star Trek: "The Corbomite Maneuver"

A Strange Step Backward


by Gideon Marcus

With the round robin review format we've set up for Star Trek, everyone's obligations are pretty small, with the exception of the person assigned the head: the first, summarizing piece of the article.  I drew the short straw this week, possibly the most challenging week in the history of this new show.

Because a summary's job is to explain what happened.  And in "The Corbomite Maneuver", virtually nothing happened. 

Repeatedly.

The episode boils down to this: The Enterprise travels into an unexplored area of space. An alien ship intercepts the Earth ship, traps it, and threatens to destroy it.  The alien ship takes many guises — first a multicolored cube, then a giant globe of incandescent lights, then a set of glowing soap bubbles (admittedly gorgeous effects), but the scenario is always the same.  The Enterprise tries to break free, dramatic music plays, people fall out of their chairs or bounce around in hallways. The navigator-of-the-week, this time a ‘Lieutenant Bailey’ (anxious, overeager, promoted too early) occasionally has a breakdown. Lieutenant Uhura says "Hailing Frequencies open" a half dozen times, looking rather bored.


"I should have stayed with Ma Bell…"

Eventually, we learn that the whole thing was a test. The alien, Balok of the First Federation (Ron Howard's little brother), never planned to destroy the Enterprise. On the one hand, I appreciate an episode without a villain, one that challenges the hubris that we are the most powerful or the kindest race in the galaxy.

On the other hand, once we know that Kirk and his crew were never in danger, everything becomes a cheat.  The tension, the clever attempts to outmaneuver Balok (with warp engines or poker metaphors), all of it is meaningless.

Add to that a certain unevenness of the episode.  It is pretty clear this episode was filmed before the others we've seen in the series. Spock is yelling again, is wearing his old uniform, and his haircut is more severe.  Shatner has less of a grip on the Kirk character, playing him on a short fuse. As with "Where No Man has Gone Before", everything feels rawer, cheaper, more like an episode of Voyage to the Bottom of the Sea.  Perhaps it was the consciously military mien of the scenario and character interactions.

All this kvetching suggests I didn't like the episode.  That's not quite right. There are some great exchanges, particularly any involving DeForest Kelley (Dr. McCoy). George Takei's Sulu is a delight, with a lot of great subtle expressions. Yeoman Rand got an entire episode free of assault (though Kirk resents her existence as a woman). The special effects are really excellent, and probably the reason the episode got delayed. 


That's a really big Christmas ornament…

But for the most part, I was just kind of bored. That's a new experience for me with Star Trek, which has hitherto been either great or problematic. However, if "Maneuver" really is an early episode, that means we're actually on an upward rather than a downward trend. Plus, next week's episode, which looks like it will incorporate the terrific first pilot, is very promising.

So, three stars, but I won't hold it against the show.


Zero-Sum Game


by Janice L. Newman

As Gideon notes, The Corbomite Maneuver was a, shall we say, uneven episode. The first time the ship was ‘about to be destroyed’ it was exciting. By the third time, it was definitely less impactful. On the other hand, the story had plenty of great moments. The problem was, these ended up undermining each other.

For example, Captain Kirk pulls off a wonderful bluff where he apparently convinces the enemy that destroying their ship will result in the destruction of their own vessel – the bluff being the titular ‘Corbomite Maneuver’. It’s a desperate, brilliant moment that would have made a fantastic climax for the episode. Everything, from Spock saying that it was ‘well-played’, to Bailey returning to the bridge, to Kirk’s sigh of relief when the ship is not destroyed (not to mention McCoy’s overeager offer to teach Spock the game of poker) makes for a great piece of television.


The gambit pays off.

Unfortunately, it’s not the climax of the episode – or rather, it’s the climax, but not the end. And then, when we do reach the end of the story, we learn something which by itself would have made for a clever plot twist. It turns out that the entire set of encounters were orchestrated by a single entity, a powerful being who claims that it was ‘all a test’.

This is something we haven’t seen before. Yes, in Where No Man Has Gone Before and Charlie X we had immensely powerful beings, be they humans or aliens. And in The Cage we did see powerful alien minds manipulating humans to try to get something from them. But we’ve never seen (presumably benevolent) aliens simply ‘testing’ humans to learn their ‘real intentions’. It would have been a great reversal, if only it hadn’t undermined everything which had come before. The clever parts of the story, rather than building on each other, unfortunately canceled each other out.


"Just kidding!"

Lieutenant Bailey's interactions with the captain rang an odd note in the episode. Kirk's "tough love" attitude toward him reminded me strongly of the captain in "The Bedford Incident", and I kept half-expecting Bailey to fire the ship's 'phasers' when he wasn't supposed to (instead he did the opposite, freezing in the moment of crisis).

I do want to make several notes about special effects. First, the lights making up alien ships were extremely effective (and I understand these effects were so involved that they delayed the release of this episode, which was meant to be much earlier in the line up). Second, the figure of Commander Balock that appeared on the Enterprise’s screen was an unconvincing one, yet it was plausible enough for our generation — after all, we were raised on puppet shows and other primitive special effects. The fact that the episode’s writer subverted these expectations and made the figure an actual puppet was absolutely ingenious. And third, the best special effect in the entire show had to be the dubbing of little Clint Howard with an adult’s voice.


"You Have Two Minutes Until Howdy Doody Time!"

3 stars, for the special effects, the cleverness, and the banter.


Off Kilter


by Lorelei Marcus

I enjoyed the overall message of "The Corbomite Maneuver", but I felt the episode had to make some sacrifices to get there.  In particular, the atmosphere of the ship and everyone's characterizations were severely altered from what we've seen thus far.  Captain Kirk seemed forced into the role of the hard-edged, authoritarian Captain.  The women of the crew were more stereotypically portrayed, pushed aside even, so that the men could have their dramatic moments.  Uhura looks bored.  Yeoman Rand exists to make coffee and salad and annoy Captain Kirk by being a woman.  All in all, the Enterprise felt much more current-day Navy in portrayal, and more militaristic in character.


"Did I say 'at ease', mister?"

The special effects were, as has been noted, a cut above.  But I would have liked to have seen this story told with the same Enterprise we're coming to know and love, rather than this odd, warped one, seemingly created to fit the plot's needs. 

With a mid-tier story, great visuals, and inconsistent characterization, I give "Corbomite" three stars.



by Jessica Dickinson Goodman

A Different Kind of Man Behind the Curtain

When I first heard Balok speak in this week’s episode, his voice reminded me of Frank Morgan’s booming performance in The Wizard of Oz (1939). The imagery and tactics reminded me of it as well: flowing curtains of light cascaded over Balok’s alien face, the crew of the Enterprise scrambling to bargain and trick their way out of the crisis as a seemingly all-powerful wizard holding hapless visitors to arbitrary and impossible rules.

When we found that, like The Great and Powerful Oz, Balok was a small man, pulling puppet strings to intimidate and test those around him, the twist felt familiar. But that moment was also where these two fantasies diverged: where the Wizard is venal and greedy, Balok is confident and curious. He is not a huckster, but a representative of a technologically-advanced society, able to control a vast space edifice from his tiny ship, and interested in learning the truth about the crew of the Enterprise.

While Dorothy, the Scarecrow, the Lion, and the Tin Man beg the Wizard to make them whole and take them home, Kirk, McCoy and Bailey don’t need any such boons from Balok. But he offers them anyway, opening up the possibility of cultural exchange between his First Federation and Kirk’s crew. Bailey, who had spent most of the episode as a cowardly lion, gracefully agrees to the exchange as the episode closes.


"We're off to see the Wizard!"

The parallels are not perfect — though if Mr.Spock had filled out the boarding party in the role of the Tin Man seeking a heart he already has, it might have been — but they are productive. Like the friends of Dorothy, Bailey, McCoy, and Spock spend the episode trying to free themselves from traps and get what they think they need. And like the Scarecrow, the Lion, and the Tin Man, in the end, the powers they were seeking to work around were not what they seemed.

I liked that, in this case, the powers were greater. Perhaps, if Balok had been behind the curtain in Oz, Dorothy and company would have gotten more than toys, but the true connection and understanding they needed in their journeys. I hope that future episodes are more even in tone, but also that they continue to expand our views of the universe the way Balok will for Bailey.

Three stars.