Discussion in 'Star Trek: Discovery' started by Commander Richard, Mar 7, 2019.
I completely missed the mention of duotronics in this episode.
So did I. I did, however, catch the mention of an "SQL injection". Interesting how today's concept of the structured query language for modern database systems will live on for at least another 2-300 years!
10/10. I'm a bit late throwing in my two cents about this episode, and while I haven't managed to read through all 64 pages in this thread, I'm pretty sure I don't have anything particularly new or insightful to add, so I'll try to keep it brief. in short, I loved it. In fact, I slightly surprised myself when I found myself thinking, "I love this show," which I doubt is something I would have thought during season one. I did like the first season, mostly, but if I'm being honest, there was probably also this feeling that I was partly watching it out of a sense of obligation because it has Star Trek in the title. However, I'm now at the point where I can comfortably say that I'm really liking/loving Discovery. When I saw the preview, I had some niggling qualms about the Talosians looking slightly different than they did in TOS, but those thoughts evaporated almost instantly as I got sucked into the story.
My biggest worry is that people, especially the on-the-fence skeptics, will set this as the new bar, which I'm not sure is at all fair or realistic.
This was an instant Trek classic. I have no expectation that tonight will compare, nor will I feel that "DISKUVRY IZ TEH SUX UHGAIN" if it fails to do so.
I hope people are prepared to take it all in stride.
It doesn't have to be a classic as long as it is entertaining. Something Discovery has been very hit-and-miss on up to this point.
Oh, I just remembered something I wanted to say before. As soon as Culber was brought back to life a few episodes ago, I've been hoping that the writers would acknowledge the fact that he and Tyler were, in a weird way, kind of alike now, so I was glad that Ash addressed that at the end of their confrontation.
I totally didn't make this connection until Tyler said it flat out, and I was pretty blown away by it. That was some clever writing.
Ok. This was cool.
When Leiland appeared on the viewscreen, the never-staying-still Disco camerawork was happening on the S31 bridge camera. While I love how Disco is shot, even when Skype is tracking your movement it doesn't look like that.
This is unavoidable...
My dad would have loved this episode.
This was a fantastic episode. Both this and episodes 1 and 2 are my proper favourites of the season.
10/10 for Melissa George capturing Vina so well.
This is probably the best episode of the season but it doesn’t fully explain whether Talos is under General Order 7 or not.
they probably retconned it cause let's be honest killing people because they visited a star system is barbaric
Talos is a plague world.
You can go there and come back as a Manchurian candidate, with the tools to destroy the Federation, if the Talosians are feeling malevolent, or you come back to the Federation with the mind powers of a Talosian, and give up. You stop being productive, and society crumbles to dust because you're too busy telepathically masturbating, just like how the Talosians became reduced to a dead end, if the Talosians are feeling Benevolent.
If you get close to their planet, close to their solar system, you are already a zoo exhibit who is as good as dead, and you are a weapon that might take out ships planets and empires lockstep with your own hubris that had you think that you could deal on a level playing field with asshole telepaths.
The Talosians lost warp.
That's a level of dumb that cannot be allowed back out into the Galaxy, for fear that their dumbness will spread. It could even be an application of the Prime Directive that contact is suspended with any species that loses warp, like when our grand parents forget how to drive, or forget how to drive safely.
Actually what is the range of their power? How far away was that shuttle when they did the illusions?
Separate names with a comma.