Sunday saw the premiere of Star Trek: Discovery, the latest installment in the Star Trek franchise. The first story was a 2-parter, only the first part of which aired on CBS; the rest of the season will air on the new â€œCBS All Accessâ€ subscription streaming network, which I have no interest in subscribing to, so I only saw the first episode, which ended on a cliffhanger.
As my readers may know, Iâ€™m working on over 30 years of disappointment in Star Trek. Despite the occasional good story here and there, Star Trek has been a dramatic, storytelling and characterization wasteland since Star Trek: The Next Generation premiered in 1987. I guess itâ€™s a testament to how wonderful the original series (and Star Treks II and III) were that I keep trying the new series. (Well, okay, I passed almost entirely on Voyager, since Star Trek was entirely superfluous from 1994-1999 due to the presence of Babylon 5.)
Despite hoping that the decade-plus since Enterprise went off the air would lead to some philosophical changes in the Star Trek TV franchise, the first episode of Discovery, â€œThe Vulcan Helloâ€, was about as mundane as ever. The series takes place in the original timeline (i.e., not the J.J. Abrams reboot timeline), approximately 10 years before the original Star Trek series (i.e., about 2 years after the events of â€œThe Cageâ€, the one Christopher Pike episode), and it focuses on the (apparently last) adventure of the USS Shenzhou, which encounters an alien object while investigating damage to a remote yet apparently important satellite.
There isnâ€™t really a way to discuss the episode without spoilers – frankly, there isnâ€™t enough story here to discuss otherwise – so Iâ€™ll continue after the cut: