A general rule with “Star Trek” shows is that they get off to a rough start, and it often isn’t until around the third season that they hit their stride. There’s the odd exception like the original series or “Strange New Worlds,” but the rule held true for ‘The Next Generation,’ ‘Deep Space...
www.darkhorizons.com
A general rule with “Star Trek” shows is that they get off to a rough start, and it often isn’t until around the third season that they hit their stride.
There’s the odd exception like the original series or “Strange New Worlds,” but the rule held true for ‘The Next Generation,’ ‘Deep Space Nine,’ ‘Voyager,’ ‘Enterprise,’ ‘Discovery’ and ‘Picard’. The result is a first two seasons that are usually a mixed bag.
“Star Trek: The Next Generation”, for example, had some great ones, including “Conspiracy,” “The Measure of a Man,” and “Q Who”. It also had some cringe-inducing duds like the clip show “Shades of Gray” which came at the end of a season that was a victim of that year’s writer’s strike.
Almost on par with both that episode and the final season’s legendarily terrible “Sub Rosa,” is the third episode of the show’s first season – “Code of Honor”. The episode sees Lt. Tasha Yar fighting for her life after the ruler of Ligon II wants to take her as his new bride (by having Tasha kill his current wife and inherit her holdings).
Multiple confusing creative choices led to an episode chock full of racial stereotypes that were badly dated even back then, along with incredibly misogynist and sexist language (the original plan was rumored to have been a reptilian race with a samurai-style influence). The cast has discussed the episode in the past in a negative light, including franchise mainstay Jonathan Frakes who said back in 2007 he hoped to see the episode struck from reruns and home video.
Sixteen years later, at a time when numerous shows have pulled controversial episodes from their streaming libraries due to derogatory content within, Frakes is repeating that call.
Speaking with
TrekMovie this week, he said it was surprising that the episode hadn’t been removed from rotation already. When told the episode was still up on services like Paramount+ and Hulu, he reportedly was a little shocked:
When the interviewer suggested the episode remain but with a disclaimer warning, Frakes was said to have only partly agreed.
variety.com
movieweb.com
news.bbc.co.uk
redshirtsalwaysdie.com
