- 6 hours ago
It's true that you can't always please everyone, but these scenes left no one happy.
Category
📺
TVTranscript
00:00Much as we absolutely love Star Trek, there is no questioning the fact that some moments leave us
00:04scratching our heads, or shouting to the sky, or in a situation where my mum has said I'm not
00:09allowed to watch it around the house anymore because I get a bit involved. The original
00:14article that this video was based on was written by the wonderful Marcus Fry. I, however, am Sean
00:19Ferrick for Trek Culture, and here are 10 more frustrating Star Trek moments.
00:25Number 10. Voyager skipping past Borg space.
00:27After Voyager was flung into the Delta Quadrant, it was only a matter of time before they ran into
00:31the Borg, whose territory was known to be located directly between them and Earth. Unfortunately
00:36for fans of the show, Voyager's stay in the heart of Borg space was much more brief than
00:40they originally predicted. Kess went Super Saiyan and launched the ship all the way to
00:43the other side of the territory in The Gift, one episode after Voyager first entered it
00:47in Scorpion. Voyager went on to encounter the Borg several more times throughout the series,
00:51but the writers having them skip past the most difficult part of their journey so easily
00:54wastes so much story potential. We could have had a season-long arc of the Voyager struggling
00:59desperately to make it through the home of one of the most terrifying empires in Trek. It would
01:03have been the perfect opportunity to give the show a bit of a darker tone and raise the stakes.
01:07Maybe one of the crew being assimilated. Having Kess launch the ship to safety with their
01:11telepathic powers was a good idea, but it definitely would have been nice to see more than two episodes
01:16inside of Borg territory. Number 9. Kirk's revival in Into Darkness
01:20Star Trek Into Darkness gets a lot of criticism for mostly just being a bit of a rip-off of The
01:24Wrath of Khan, really. Some, however, like to think of it as more of an homage film, especially when it
01:29comes to the ending when Kirk sacrificed himself to save the ship, just like Spock did in the original.
01:34Look, Kirk's death scene was great, but the frustrating part is just how they brought him back.
01:38In The Search for Spock, Spock was resurrected using the Genesis planet and his catcher in a really
01:42creative way that tied into the previous film brilliantly, but in Into Darkness, McCoy basically
01:47just invented an immortality serum using Khan's blood. This method of bringing him back to life
01:51was pretty uninspired and came out of nowhere, but worse than that, it basically meant that people
01:55could be resurrected at any time the plot required, provided they produced more augmented blood in a lab.
02:01It only removed the stakes in a way that Spock's revival didn't, given that Project Genesis ended and
02:06the planet degraded over time. Number 8. The Return of the Ferengi
02:10Some fans were pretty upset with the redesign of the Klingons in Season 1 of Star Trek Discovery.
02:14They were now hairless for some reason, had giant elongated heads, and looked more like
02:18generic reptilian aliens from another TV show. Some of these changes were rolled back a bit into
02:23the second season, like for example, their hair came back and it was explained that Klingon
02:27warriors sometimes shaved their heads in times of war, something that strangely didn't see much
02:30of during the Dominion War, but no, it's neither here nor there. Star Trek Discovery then made
02:35another change that got people up in arms. Season 4 of Discovery gave us a few scenes with the Ferengi
02:41that looked much closer to Andrew Probert's original design of the Ferengi. Whereas the Ferengi we were
02:47used to seeing on screen had smoother features and skin, apart from the oldest ones like Zek,
02:51these ones had a more spiked ear and were a bit more lined. Again, the fandom was a little bit up in
02:58arms. Some liked it, some hated it, some were like, oh, you're changing things for the sake of changing
03:03things. Others were like, yeah, but that's in the very first sketch. Really, it's just one of those
03:08watershed moments in Star Trek that, once again, people get really frustrated about or love,
03:14depending on the day of the week. Number 7, The Alternate Kirk's Promotion.
03:18Something odd that you might have noticed about 2009 Star Trek and the other alternate universe
03:22films is that all of the main cast came aboard the Enterprise at way younger ages than their prime
03:26timeline counterparts from the original series. Kirk was particularly quick to move through the ranks.
03:31He went from a cadet to captain of the Federation's flagship, all because of his work defeating Nero
03:35and saving the Earth at the end of the 2009 film. Problem is that plenty of other characters in the
03:40film, like Spock and Scotty, helped just as much or more than Kirk, but got way less credit. Beyond
03:45that, we've seen characters get promotions for exceptional work, but now it goes straight from
03:49a cadet to a captain, which would normally take a decade or two of service.
03:52Number 6, Seeing Inside the Q Continuum. Ever since the Enterprise first met Q in the first episode
03:57of The Next Generation, fans have been wondering about the true nature of his species. The Q
04:01Continuum, as he called it, was always spoken about vaguely as some sort of realm where all
04:05the Q reside, occasionally leading to interfere with less advanced lifeforms. Finally, in the
04:10Voyager episode Deathwish, we got to see inside of the Continuum when the Q, known as Quinn,
04:15brought them there to show how miserable life for the Q has gotten. Unfortunately, their visit
04:20was a little bit anticlimactic. According to Q, the Continuum existed in a dimension so far beyond
04:25human comprehension that, in order for the crew to visit it, anything was physically translated
04:30into illusions that could be understood by lower lifeforms. What this basically meant was
04:34that, rather than a trippy visual spectacle unlike anything we've ever seen, the Continuum
04:38was presented as an old desert road, and the Q were presented as ordinary humans. Later,
04:42the crew visited the Continuum again in the episode The Q in the Grey, and it was portrayed
04:46as a battlefield in the American Civil War. It makes sense that the domain of the Q would
04:50be beyond the understanding of humans, but the fact that we can't possibly ever know what
04:54life is truly like in the Continuum, it's a bit of a bummer, really.
04:57Number 5. Riker being confused about gender-neutral language in the 24th century.
05:01The Next Generation episode The Outcast was frustrating for a lot of Shrekies,
05:05mostly because it tried to tell a story in support of gay pride for the first time in
05:09the franchise's history, but it totally missed the mark on a lot of stuff and ended up dealing
05:13with gender far more than sexuality. The Enterprise-D was introduced to the Genii, a species with only
05:18one sex, and Riker started to form a relationship with one of them named Sauron, who he found out
05:23was actually identifying as female. The whole episode then focused on her struggle to be
05:27accepted as a woman by her society. There are a number of problems with The Outcast,
05:31but there's one scene that seems particularly short-sighted. While speaking with Riker about
05:35her sexless species, Riker was extremely confused on what pronouns to use for them. When the episode
05:40was made, they, them, theirs was not very popular singular pronouns in America, even though they
05:45were popular for describing someone of unknown gender in the past. So Sauron told Riker that the Genii used
05:50a gender-neutral pronoun that had no equivalent in English. Watching this scene back today is
05:54particularly frustrating for non-binary folks. Fortunately, Discovery seemed to retcon this by
05:59giving us our first non-binary human character, Adira Tal, who used they, them, theirs, showing
06:04that there's not just aliens who can exist outside of male and female expectations.
06:08Number 4. Icheb's Death
06:09A lot of old Trekkies can criticise New Trek for being too dark and depressing, specifically Discovery
06:14or Picard. Some take this too far and decide to write these shows off entirely, which is a bit of an overreaction,
06:20but there are times when even the biggest supporters of the new Trek era have to see where the haters
06:24are coming from. Specifically, Icheb's death scene from Star Trek Picard was one of the most brutal
06:29and abrupt deaths of a major character in Trek history. Icheb was the only one of the bored children
06:34recovered by Voyager who came back to Earth with the rest of the crew. He was an extremely intelligent
06:38young man with a passion for helping others and a bright future ahead of him. Then, after decades of
06:43wondering what happened to him after reaching the Alpha Quadrant, we were given a scene of him
06:46screaming in agony as someone ripped out his eyeball to harvest his Borg implants for sale.
06:51To make this even more awful, Seven of Nine discovered him and decided to end his suffering.
06:55The scene was meant to show how Seven had changed into an emotionally broken vigilante,
06:59but Icheb's death just came as such a surprise. It was definitely a good way to give Seven more
07:03of an edge, but it would have been nice to have had some build up to the death scene. It just feels
07:06like the writers threw away his character for Seven's sake. Number 3. Michael Burnham's Mutiny
07:11Michael Burnham was given a pretty bad introduction in the first episode of Discovery,
07:14the Vulcan Hello. The episode ended with a assaulting Captain Georgiou with a Vulcan nerve
07:18pinch to fire preemptively on the Klingons against her wishes. This act of mutiny is what initially
07:23gave Burnham such an awful reputation with the rest of Starfleet, as well as the fans. She argued
07:27that the Klingons would respect the Federation if the Shenzhou beat them to the first punch,
07:31but this idea went against everything that the Federation is supposed to stand for, and it
07:35possibly would have just made the Klingons angrier. Later, she nearly redeemed herself by travelling to the
07:39lead Klingon ship to catch her Takuvma. Unfortunately, that didn't work, as Takuvma ended up killed after
07:45killing Georgiou in a brutal assault. While the Klingon Empire was always going to go to war anyway,
07:52lots of people took this to be Burnham's fault, and that gave her such a bad reputation with the
07:57rest of Starfleet that her name was mud by the time she was discovered by Captain Lorca and the USS Discovery.
08:04Number 2. Scotty forgetting about Kirk's death. Fans were pleasantly surprised to see the return of
08:09Scotty from the original series in the Next Generation episode Relics. After a ship was damaged,
08:13he saved himself by sending his body through the transporter, but didn't direct it to anywhere,
08:17so he was stuck unconscious in the pattern buffer for over 70 years, until the Enterprise D found his ship
08:22and revived him in the 24th century. It was awesome to have Scotty return and react to his new life in the future,
08:27but there was one scene in Relics that's quite frustrating for fans, really, who care about continuity.
08:30When Scotty first learned that he was rescued by the Enterprise, he didn't know so much time had passed,
08:34and said that he thought Jim Kirk himself came looking for him. Of course, there's one problem.
08:38Kirk was believed dead when he was lost in the Nexus in Starter Generations, and Scotty was
08:42present on the Enterprise B when it happened. Generations, of course, came out about two years
08:46after Relics, but the thing is, Ronald D. Moore was involved in writing both stories. Now,
08:54it just makes Scotty seem like a bit of a jerk for forgetting about his friend's death. Of course,
08:57they do talk about that .00003 degradation, so... all's fair. Number 1. Seti Alpha what now?
09:06There were a lot of problems with the beginning of The Wrath of Khan, an otherwise amazing film.
09:10Pavel Chekov and other crew members of the USS Reliant were sent to Seti Alpha 6 to survey a
09:14supposedly lifeless planet for experimentation with the Genesis device. While exploring the circus,
09:19Chekov and Captain Terrell encountered the wreckage of the SS Botany Bay, Khan's ship from
09:23Space Seed. Despite the fact that Walter Koenig hadn't joined the cast yet when Space Seed was filmed,
09:27Khan immediately recognized Chekov. There's actually a different part of the scene that's even more
09:31annoying. Khan explained that the planet they were on was, in fact, Seti Alpha 5, the planet that Khan
09:36and his fellow Augments were left on at the end of Space Seed. Apparently, Seti Alpha 6 exploded and
09:41devastated the already harsh environment of Khan's planet, yet it's unexplained how a planetary explosion
09:46could be missed by the Federation, especially since they know that a group of the most dangerous
09:50humans in the universe settled in that same system. One would also think they returned to check
09:55on the Augments? You kind of can't be mad at Khan for being frustrated here. Now that's everything for this list,
09:59and if you reckon there's anything more that we missed, let us know in the comments for a potential
10:03third list. Don't forget to go back and read the article written by the wonderful Marcus Fry and
10:06don't forget to check out the first list of most frustrating Star Trek moments. I have been Sean
10:11Ferrick. You can catch us over on Twitter at TrekCulture and you can catch us on Instagram as well
10:15at TrekCultureYT. You can catch myself at Sean Ferrick on the various socials. Make sure that you look
10:20after yourself till I see you again. Make sure that you live long and prosper. To our friends in Ukraine,
10:23stay strong, keep fighting, and to our friends in Iran, you inspire us daily with your bravery.
10:28Everyone, have a wonderful however long it is. I'm talking to you again. Make it so.
Be the first to comment