It would be interesting if she turns out to be a 24th century Vulcan design. Not all Vulcan ships have to have ring drives, as the Surak clearly demonstrated and nearly 130 years before the current show.
It's 2030. There are 9 concurrent Trek shows running on CBS All Access. Every single show uses one starship design for everything, which John Eaves first submitted in 1997 and has resubmitted for every ship design he was ever asked for in the subsequent 33 years. He has reached the apex of concept design.
Much like how chronologically the last of the battleships were very young, in some cases only 3-4 years old, when they were retired..but they were very obsolete in technology and doctrine. Granted the Iowa class gets a special allowance on that because they were repeatedly brought back for shore bombardment work..but that's not what their original design intention was.
And to be fair, he is a competent if not a pretty good starship designer. It's not his fault Bryan Fuller wanted to completely ignore previous 23rd century starship design and just a decade before TOS. When you're told you can only design ships with long, pointy and jagged nacelles and oddball proportions you have to work with the parameters you're given.
John is just one of the symptoms of the problems inherent in DSC.
They were never designed to escort carriers. The design for the Iowa class was finalized in 1939 before the shift to carrier warfare became necessary due to the destruction of the pacific fleet at Pearl Harbor.Iowa class was explicitly designed to escort aircraft carriers. Carriers typically had a top speed of over 30 knots. American "standard" battleships built around WW1 topped out at 22kts, and even the "fast" North Carolina and South Dakota classes could only hit 28kts. Foreign battleships typically operated between those numbers.
Iowa was designed for 32.5kts, hit 33 in real life, and USS New Jersey once hit 35kts fresh out of drydock...which is insanely fast for a ship. Nothing that size has hit that speed before or since. And it took insane amount of power and a hull design that somewhat sacrificed protection for speed.
Basically, they were the only battleships on Earth that fit into the new, faster carrier-oriented world.
Eaves is all cut-ins and knife edges. It's tiresome.
Yes.Doug Drexler's busy with the Orville production team these days, right?
Why would there be a definitive look for civvie ships built by hundreds of different member planets? We've seen plenty of Vulcan designs and a few Andorian and Tellarite.Nobody has nailed down "Federation but not Starfleet" yet, though. The 1950s style rockets from TOS-R were neat, but hardly definitive.
Timo Saloniemi
You're right about this, I think.Nobody has nailed down "Federation but not Starfleet" yet, though. The 1950s style rockets from TOS-R were neat, but hardly definitive.
Why would there be a definitive look for civvie ships built by hundreds of different member planets? We've seen plenty of Vulcan designs and a few Andorian and Tellarite.
I guess the big question is who built the ubiquitous Merchantman and Batris/Norkova designs.
Which is my preference, personally. So many different member worlds would allow for some variety in ship component and design language. As much as I love the original Enterprise there was no indication that its design language was the only one used.One thing I do like about the DSC Era of starships is that the variety of weird designs lets us speculate that some of them could be designed by and even crewed by officers from certain member worlds of the Federation. The Magee-class stands out very strongly in the mid-23rd century but could indeed be an Andorian design and thus why the Shran is a prominent starship seen at the Battle of the Binary Stars. She could be manned by Andorians in much the same way the Intrepid at the time of "The Immunity Syndrome(TOS)" was manned entirely by Vulcans.
Somebody once pointed out design similarities they saw between the Shran and the Andorian Kumari-class warships of ENT.
We use essential cookies to make this site work, and optional cookies to enhance your experience.