Dammit - in addition to the Saladin; I want the 3 Nacelle Franz Joseph Trek Manual Dreadnaught.![]()
NCC-2100 appearance or I boycott!
Dammit - in addition to the Saladin; I want the 3 Nacelle Franz Joseph Trek Manual Dreadnaught.![]()
There ya go. It's not warp nacelle scienceWhen people use language, we also use words non-literally--- metaphorically as when we wax poetic, without going all "Beep-beep-beep-beep The Enterprise is not a want or a desire, it is a mechanical device. Illogical, Illogical, all units relate. Norman coordinate."
When production personnel and actors refer to the Enterprise as another character in the show, they are speaking metaphorically, not literally, to elicit an emotional response and sense of connection. It's employed as part of a different rhetorical strategy than adherence to strict literalism and precise diction. As part of a public relations strategy, the use of language with more emotional connotations serves a rhetorical purpose that a simple, factual, 'The Enterprise is the setting of our stories, our vehicle for getting our characters where we need them to be" does not.
There are contexts in which "The Enterprise is a beautiful lady and we love her" is preferable to "The Enterprise is a wooden filming model constructed by Richard C. Datin," and other circumstances in which the converse is preferable.
COMPUTER: Computed and recorded, dear.The "Enterprise is a character" debate could be easily settled if we get an episode told from Enterprise's perspective, perhaps with a romance subplot? The shuttlebay clamshell doors could serve as the starship equivalent of a reptile's/dinosaur's cloaca.
The fallacy of your argument here is the fact that the ship's main computer is a component of the Enterprise. It is not the ship itself.COMPUTER: Computed and recorded, dear.
KIRK: Computer, you will not address me in that manner. Compute.
COMPUTER: Computed, dear.
KIRK: Mister Spock, I ordered this computer and its interlinking systems repaired.
SPOCK: I have investigated it, Captain. To correct the fault will require an overhaul of the entire computer system and a minimum of three weeks at a Starbase.
KIRK: I wouldn't mind so much if it didn't get so affectionate.
SPOCK: It also has an unfortunate tendency to giggle.
O RLYThe fallacy of your argument here is the fact that the ship's main computer is a component of the Enterprise. It is not the ship itself.
That's a lot of arguing for someone who says it's pointless to argue.![]()
They don't need to.Or will they try to make the two versions work together?
Well, on the up-side, at least it doesn't look like a freakin' beer brewery.Not sure if this has been discussed earlier: How many Engineering Refits are there going to be for the Enterprise?
Or will they try to make the two versions work together?
![]()
![]()
![]()
![]()
First image isn't working.Not sure if this has been discussed earlier: How many Engineering Refits are there going to be for the Enterprise?
Or will they try to make the two versions work together?
The fallacy of your argument here is the fact that the ship's main computer is a component of the Enterprise. It is not the ship itself.
Must have taken that three week layover, since it's never mentioned again. First season weirdness strikes again?There ya go. It's not warp nacelle science
COMPUTER: Computed and recorded, dear.
KIRK: Computer, you will not address me in that manner. Compute.
COMPUTER: Computed, dear.
KIRK: Mister Spock, I ordered this computer and its interlinking systems repaired.
SPOCK: I have investigated it, Captain. To correct the fault will require an overhaul of the entire computer system and a minimum of three weeks at a Starbase.
KIRK: I wouldn't mind so much if it didn't get so affectionate.
SPOCK: It also has an unfortunate tendency to giggle.
No, because it isn't the 1960s.Any chance Engineering sets will look like the TOS ones when Kirk takes overr?
^^^To be fair, miniaturization is one of the hallmarks of technological advancement. You could probably fit 1,000 Apollo Mission computers into a modern cell phone.![]()
We use essential cookies to make this site work, and optional cookies to enhance your experience.