Plus 24 Biblical titles.
Makes sense. King James version was written in the same general time frame.Plus 24 Biblical titles.
To be fair a mangled barely functioning computer that lobotmised itself to stay functioning.It actually really was. A comic book convincing the ship computer to turn over control to who it perceived to be intruders. Utterly fucking ridiculous.
I think a lobotomized computer would be even harder to access rather than easier. But who knows.To be fair a mangled barely functioning computer that lobotmised itself to stay functioning.
Oddly personable like the Athena's computer, they made a big deal about Zora but these computers have a fair bit of personality to them. The shuttle computers seen in DSC were certainly just traditional sounding so it doesn't seem like they adjusted computers to sound more organic as time went on.
Then it was JJA!Someone went in and added a small flare to all the deltas for some reason.

There's a touch of Galaxy Quest's Thermians and the "historical documents" in there, it's true. It didn't trouble me too much b/c it was a computer that had been dead for over a century that they were trying to revive -- which circumstance I could see affecting its standards somewhat -- but if it doesn't work for you, it's not like I can blame you.The entire thing about the comic book convincing the computer that the crew was dead was beyond ridiculous.
Nah, I'm alright with it. I've said in this thread that you can both think it's ridiculous and enjoy the episode. It probably is more fun than entering some code or something. And anything with TOS in it is OK by me!There's a touch of Galaxy Quest's Thermians and the "historical documents" in there, it's true. It didn't trouble me too much b/c it was a computer that had been dead for over a century that they were trying to revive -- which circumstance I could see affecting its standards somewhat -- but if it doesn't work for you, it's not like I can blame you.
If you're a code monkey trying to work forward in a genuine way from the disaster they describe, and this doesn't seem to you like how a computer would behave in that circumstance, that's valid. Whether it's narratively interesting is a different question, but it's valid. For much of the audience, I think the pace of events kind of carries us past that? But that doesn't make you wrong.
Further to this, I also kind of feel the person who was irritated by the Sargasso getting murked in a single volley during the final action sequence. I can see why it happens, in part because the total mismatch between the Federation and incidental opposition that many viewers were accustomed to in TNG doesn't apply in this setting, but I can't lie: I also saw how it was a contrivance b/c there wasn't time built into the script for an actual space battle in that moment.
These things don't bother me the way they seem to bother some. But I can see where people are coming from.
Eh, there's a lot of Discovery stuff that's being quietly retconned.To be fair a mangled barely functioning computer that lobotmised itself to stay functioning.
Oddly personable like the Athena's computer, they made a big deal about Zora but these computers have a fair bit of personality to them. The shuttle computers seen in DSC were certainly just traditional sounding so it doesn't seem like they adjusted computers to sound more organic as time went on.
Eh, there's a lot of Discovery stuff that's being quietly retconned.
Starship AI were outlawed.Starship AI have rights in the 32nd century. Zora's issue was that she hadn't joined Starfleet.
I always thought of it as an exercise in trying to overcome a ship in the field needing repairs, with a limited amount of time to solve the problem, and after each group of students did their best, everything was reset by the staff, for the next group of cadets to solve as a problem from the same starting point. Although a computer program was left in engineering, by an earlier set of students, that allowed for the restart of the drive, but the students weren't initially told about it.My take is the Miyasaki was much, much worse but the War College has been making yearly trips to repair parts of it for five years.
It's a long running project.
And only now did they get the life support up.
I always thought of it as an exercise in trying to overcome a ship in the field needing repairs, with a limited amount of time to solve the problem, and after each group of students did their best, everything was reset by the staff, for the next group of cadets to solve as a problem from the same starting point. Although a computer program was left in engineering, by an earlier set of students, that allowed for the restart of the drive, but the students weren't initially told about it.
From what I got out of the episode was that the ship was a total loss, and in a ship graveyard. It wasn't ship recovery, but crisis response simulation training. The ship's mechanical systems were destroyed, and the crew killed when its drive was first activated. They weren't there to completely repair the ship and return it to service, but to practice crisis response and support of the rescue, in the situation of a ship disaster.I didn't think they'd reset it because I think they'd want to recover a ship from the previous century given the current scarcity but I don't think they gave an indication one way or the other.
I assume they reset the ship and disable everything that's fixed.My take is the Miyasaki was much, much worse but the War College has been making yearly trips to repair parts of it for five years.
It's a long running project.
And only now did they get the life support up.
I assume they reset the ship and disable everything that's fixed.
Otherwise how is it a test that you can compare teams against?
I am surprised so few people remembered that.It looked like the one from early Disco S2, where they find Reno
Who/when?A red blooded Vulcan![]()
We use essential cookies to make this site work, and optional cookies to enhance your experience.