Lots of beam spam from the Enterprise, no doubt.
The Naked Now - The crew disabled the 1701D
The Last Outpost - Superior technology disabled the 1701D
Home Soil - The silicon life forms were able to take control of a limited portion of the ship and computer.
Elementary, Dear Data - Moriarty was the ships computer.
Contagion - Alien "Virus" much more advanced than the 1701D computer caused the problems.
Evolution - Nanities infest the 1701D
Booby Trap - The name says it all.
Yesterday's Enterprise - 1701D overpowered with little room to maneuver.
Tin Man - Alien creature disables the 1701D and destroys a Romulan Warbird.
Hollow Pursuits - Nearly ship wide contamination caused the problems.
Galaxy's Child - Alien creature "feeds" off the 1701D
Night Terrors - Power loss caused by the rift.
Disaster - 1701D collides with quantum filaments, computer was not completely functioning.
Cause and Effect - explained above.
Timescape - the Aliens sent a feedback loop that overloaded the warp core, only the time bubble saved the 1701D
All Good Things... - The anti-time distortion caused 2 of the 3 1701D's to blow up.
I think those are all the times the 1701D lost power or her warp core was ready to blow. That's less than 10% of the episodes.
As an exploration ship, the Galaxy class was a success - the Enterprise's accomplishments are proof.
From a military POV, the galaxy was an embarassment. The warp core was vulnerable, the nacelles were vulnerable, the power system was vulnerable, etc
In DS9:Way of the warrior 2, The Defiant (without shields) withstands fire from a kingon ship (considerably larger than a BOP) for minutes, and is in pretty good shape afterwards.
In VOY:Equinox 2, Voyager survives fire from the Equinox (whose crew knew voyager's shield frequencies) for minutes and is in pretty good shape afterwards.
In Generations, Enterprise is destroyed by an ancient BOP (who knew its shield frequencies only at the beginning of the battle) in minutes. Pathetic.
In TNG:Cause and Effect, an old federation ship strifes enterprise's nacelle. Enterprise blows up less than a minute later.
In DS9:The Jem'hadar, both the Federation and the Dominion wanted to prove its strength to the other party. The feds decide to send a galaxy class - with predictable results: an embarassment for the federation.
In DS9:The Search, The Defiant did much better than the odyssey.
And then there are, of course, the numerous episodes where enterprise's power grid or warp core seem to want desperately to fail, and do so as often as possible.
You can add to these the episodes from your quote.Another example: in TNG:Rascals, the enterprise is overwhelmed (not "even" destroyed, but captured!) by two obsolete BOPs, manned by retard ferengi!
And, again, it was destroyed, and previously disabled in all of those other scenarios, not as part of a coherent scheme meant to depict the technological prowess of the Federation flagship, but because the story called for it. That's all.
Again, no. If they sent the Defiant, then IT would have been blown up, and the producers would have had to introduce yet another new ship the following season's season premiere. See, this is what I mean about it being a TV show and it's folly to try to apply reason to FX shots or careless battle dialogue.If the federation would have sent the Defiant, the battle would have progressed quite differently - as in, it would't have shamed the Federation.
Sure it can if it's a super duper Iconian virus that is to anything you're thinking of as a nuclear aircraft carrier is to a wooden branch floating on water. They were lucky shutting everything down worked, that the ship didn’t become sentient and started demanding pancakes. I'm being funny here but there's a point I'm trying to make that I think you and the guy below aren't getting…The problem is the Federation's obsession with centralized computer integration. Any sane ship designer would have made designed the critical safety systems to function totally offline, without interfacing with anything else on the ship. Physically isolating critical systems and networks is the gold standard in security. No matter how advanced a virus is, it can't infect your computer if your computer isn't pluged into anything else.
Okay, 1) that's a metaphor. And 2) only because the lame ass producers never got 7 years with it…have we forgotten how shitty the show became at the end?But the Sovereign was never blown up by a tribble.
What admirals are you talking about? There ARE no admirals. There is no "obsession with centralized computer integration." Starfleet didn't design the Galaxy Class. Andy Probert did - the outside anyway, with direction from Gene Roddenberry et al. Its performance was dictated by the story idea. "Hey wouldn't it be cool if" ...This week it's killer nanites, next week its Romulan warbirds, the following it's Q and the Borg. If the ship wasn't in serious shit, if the crew never needed fear for its safety, this site to which we allocate our time and effort into discussing this TV show, this "entertainment franchise" (blech) would not exist.And Starfleet's admirals are among the naivest people ever depicted on television - one example (among many) being in DS9:The search, where it's established that they discontinued the defiant project because "the borg threat became less urgent" - that, after TNG:Best of both worls!
Again, it's consistent that this naive bunch would continue to use a militarily incompetent ship as a flagship..
And, again, it was destroyed, and previously disabled in all of those other scenarios, not as part of a coherent scheme meant to depict the technological prowess of the Federation flagship, but because the story called for it. That's all.
True.
But, as I said before:
"The galaxy class is a fictional construct. It is what it is shown to be in canon. If it is consistently shown to be a death trap, then it is a death trap!"
The galaxy class ships are virtually identical - the same blueprint, the same construction methods. Enterprise, odyssey, etc are virtually identical - except for some bridge aesthetics.And, again, it was destroyed, and previously disabled in all of those other scenarios, not as part of a coherent scheme meant to depict the technological prowess of the Federation flagship, but because the story called for it. That's all.
True.
But, as I said before:
"The galaxy class is a fictional construct. It is what it is shown to be in canon. If it is consistently shown to be a death trap, then it is a death trap!"
Agreed. But I still don't see proof that the class was a deathtrap. The Enterprise-D, maybe, but not the whole class.
And, again, it was destroyed, and previously disabled in all of those other scenarios, not as part of a coherent scheme meant to depict the technological prowess of the Federation flagship, but because the story called for it. That's all.
True.
But, as I said before:
"The galaxy class is a fictional construct. It is what it is shown to be in canon. If it is consistently shown to be a death trap, then it is a death trap!"
Agreed. But I still don't see proof that the class was a deathtrap. The Enterprise-D, maybe, but not the whole class.
What admirals are you talking about? There ARE no admirals. There is no "obsession with centralized computer integration." Starfleet didn't design the Galaxy Class. Andy Probert did - the outside anyway, with direction from Gene Roddenberry et al. Its performance was dictated by the story idea.[...]And Starfleet's admirals are among the naivest people ever depicted on television - one example (among many) being in DS9:The search, where it's established that they discontinued the defiant project because "the borg threat became less urgent" - that, after TNG:Best of both worls!
Again, it's consistent that this naive bunch would continue to use a militarily incompetent ship as a flagship..
What I see here is fans who don't like the stories told as much as…no that's not it either…they're here because they like the stories but want more, they want to see these spaceships kicking ass and taking numbers, and they cling to whatever ship "class" had the most FX shots doing that. Then they go back miffed at the other ships and come up with all these biased arguments trying to sway others to follow their literal-minded madness neglecting likely facts about these spaceships (i.e. the Federation's flagship is, um, tough) because they didn't get enough space battles! Good grief!
And then they feel persecuted when fans of the ship THEY're attacking argue back. Especially with that sin of internet jerk sins: reality.
No, they're not. Just because something is built to the same blueprints does not make it completely identical to another thing. There are a myriad of industrial reasons how and why the D could be the exception rather than the rule.
We saw other Galaxys doing fine in combat on DS9 during the Dominion War.
This means that the trekverse is fictional, not real. It means that this fictional universe is populated with fictional naive admirals and fictional starships.
And some fictional starships were depicted as being cool - for example, Defiant, who successfully engaged multiple dominion ships on many occasions. Other fictional starships were depicted as being pathetic - the galaxy class, for example.
No, they're not. Just because something is built to the same blueprints does not make it completely identical to another thing. There are a myriad of industrial reasons how and why the D could be the exception rather than the rule.
We saw other Galaxys doing fine in combat on DS9 during the Dominion War.
And then there are, of course, the numerous episodes where enterprise's power grid or warp core seem to want desperately to fail, and do so as often as possible.
The Naked Now - The crew disabled the 1701D
The Last Outpost - Superior technology disabled the 1701D
Home Soil - The silicon life forms were able to take control of a limited portion of the ship and computer.
Elementary, Dear Data - Moriarty was the ships computer.
Contagion - Alien "Virus" much more advanced than the 1701D computer caused the problems.
Evolution - Nanities infest the 1701D
Booby Trap - The name says it all.
Yesterday's Enterprise - 1701D overpowered with little room to maneuver.
Tin Man - Alien creature disables the 1701D and destroys a Romulan Warbird.
Hollow Pursuits - Nearly ship wide contamination caused the problems.
Galaxy's Child - Alien creature "feeds" off the 1701D
Night Terrors - Power loss caused by the rift.
Disaster - 1701D collides with quantum filaments, computer was not completely functioning.
Cause and Effect - explained above.
Timescape - the Aliens sent a feedback loop that overloaded the warp core, only the time bubble saved the 1701D
All Good Things... - The anti-time distortion caused 2 of the 3 1701D's to blow up.
I think those are all the times the 1701D lost power or her warp core was ready to blow. That's less than 10% of the episodes.
The Naked Now - The crew disabled the 1701D
The Last Outpost - Superior technology disabled the 1701D
Home Soil - The silicon life forms were able to take control of a limited portion of the ship and computer.
Elementary, Dear Data - Moriarty was the ships computer.
Contagion - Alien "Virus" much more advanced than the 1701D computer caused the problems.
Evolution - Nanities infest the 1701D
Booby Trap - The name says it all.
Yesterday's Enterprise - 1701D overpowered with little room to maneuver.
Tin Man - Alien creature disables the 1701D and destroys a Romulan Warbird.
Hollow Pursuits - Nearly ship wide contamination caused the problems.
Galaxy's Child - Alien creature "feeds" off the 1701D
Night Terrors - Power loss caused by the rift.
Disaster - 1701D collides with quantum filaments, computer was not completely functioning.
Cause and Effect - explained above.
Timescape - the Aliens sent a feedback loop that overloaded the warp core, only the time bubble saved the 1701D
All Good Things... - The anti-time distortion caused 2 of the 3 1701D's to blow up.
I think those are all the times the 1701D lost power or her warp core was ready to blow. That's less than 10% of the episodes.
You missed quite a few episodes - off the top of my head, 11001001,
Arsenal of freedom,
Ship in a bottle.
Then there are my previously shown examples:
As for your justifications for enterprise's failures - they change nothing. Enterprise (galaxy class) is still a ship that can be overwhelmed by just about anyone
About your excuse for "Generations":
The Duras sisters knew the shield frequencies throughout the battle only if
-Worf didn't change shield modulation; this makes him an idiot;
-Geordi sat in front of one console during the entire fight; that's a huge stretch - when, in TNG, sat Geordi in front of one console during an entire battle (when he was in engineering)?
As an exploration ship, the Galaxy class was a success - the Enterprise's accomplishments are proof.
From a military POV, the galaxy was an embarassment. The warp core was vulnerable, the nacelles were vulnerable, the power system was vulnerable, etc
In DS9:Way of the warrior 2, The Defiant (without shields) withstands fire from a kingon ship (considerably larger than a BOP) for minutes, and is in pretty good shape afterwards.
In VOY:Equinox 2, Voyager survives fire from the Equinox (whose crew knew voyager's shield frequencies) for minutes and is in pretty good shape afterwards.
In Generations, Enterprise is destroyed by an ancient BOP (who knew its shield frequencies only at the beginning of the battle) in minutes. Pathetic.
In TNG:Cause and Effect, an old federation ship strifes enterprise's nacelle. Enterprise blows up less than a minute later.
In DS9:The Jem'hadar, both the Federation and the Dominion wanted to prove its strength to the other party. The feds decide to send a galaxy class - with predictable results: an embarassment for the federation.
In DS9:The Search, The Defiant did much better than the odyssey.
And then there are, of course, the numerous episodes where enterprise's power grid or warp core seem to want desperately to fail, and do so as often as possible.
I did say: the numerous episodes where enterprise's power grid or warp core seem to want desperately to fail, and do so as often as possible. But I also said: The warp core was vulnerable, the nacelles were vulnerable, the power system was vulnerable, etc. Notice the "etc". They didn't know what a firewall was on the enterprise.Another example: in TNG:Rascals, the enterprise is overwhelmed (not "even" destroyed, but captured!) by two obsolete BOPs, manned by retard ferengi!
In essence, you only said that the Defiant was lucky, Voyager was lucky and Enterprise was consistently unlucky.As for your justifications for enterprise's failures - they change nothing. Enterprise (galaxy class) is still a ship that can be overwhelmed by just about anyone - I mean, ferengi who don't know what a computer is? Really?![]()
Second - your apologetic rationalization is unconvincing.Not that it really matters; it wouldn't matter if the Duras sisters were dressed like clowns and fired with water pistols at the enterprise.
The "flagship of the federation" was destroyed by a 20 year old BOB plagued by significant design flaws - a huge embarassment.
To add to that, the Enterprise-D could be unique simply because of the kinds of adventures that ship has. I'm willing to bet that not alot of other Galaxies have saved the Federation as often, gone up against mad scientists as much, or discovered new things like the Enterprise has. That is, a lot of these mishaps tend to be circumstantial and not anything that any designer or engineer could have foreseen, or that Fed tech was simply too inferior. In either case, there's no fault of design.
If we substitute the E-D for the Defiant, I agree that the same glitches would happen. The only reason why the Defiant never had as many of those glitches is b/c she was bred for combat and not for encountering ancient computer programs, unknown aliens, and investigative missions.
Riker II took control of the Defiant? There's a big difference between a perfect spy + the Maquis and a bunch of idiot ferengi or a 20 year old BOP.
I would argue that Voyager suffered even worse luck more consistently (the show's entire premise began with being at the wrong place at the wrong time, for starters) but I can't recall anyone bringing up the Intrepid as an example of bad engineering.I did not respond to your post? In essence, you only said that The Defiant was lucky, Voyager was lucky and Enterprise was consistently unlucky.
That doesn't excuse the galaxy's poor performance. Consistent bad luck equals a badly designed ship.
This is what I don't like about fictional hindsight as opposed to real life; the situation that leads to such events tend to be heavily heavily manufactured by the plot gods, which makes hindsight kind of useless.And in order to fire through your shields your weapons don't have to match your own shields frequency. The shields are antigravity-based (their gravitational nature is established in many episodes). They don't let stuff in, but they let stuff out.
To add to that, the Enterprise-D could be unique simply because of the kinds of adventures that ship has. I'm willing to bet that not alot of other Galaxies have saved the Federation as often, gone up against mad scientists as much, or discovered new things like the Enterprise has. That is, a lot of these mishaps tend to be circumstantial and not anything that any designer or engineer could have foreseen, or that Fed tech was simply too inferior. In either case, there's no fault of design.
If we substitute the E-D for the Defiant, I agree that the same glitches would happen. The only reason why the Defiant never had as many of those glitches is b/c she was bred for combat and not for encountering ancient computer programs, unknown aliens, and investigative missions.
Was there in TNG an AI or computer virus or unknown alien that actually had problems infiltrating/disabling the enterprise? If yes, what's the ratio between the efficient threats and the inefficient ones?
And the galaxy class was defeated not only by these exotic apparitions. A faulty BOP was sufficient to destroy it. 3 dominion bugs were overkill.
Embarassing.
We use essential cookies to make this site work, and optional cookies to enhance your experience.