Population Numbers...
Granted, I don't have an encyclopedic knowledge of ST....I've seen most of TNG era episodes( DS9, Voyager included), and a decent number of TOS...but I don't recall even *hints* about there being some sort of cover up about the "real" reason the two species split off.
Furio--Lvl 50+3 Fire/Fire/Fire Blaster, Virtue
Megadeth--Lvl 50+3 Necro/DM/Soul MM, Virtue
Veriandros--Lvl 50+3 Crab Soldier, Virtue
"So come and get me! I'll be waiting for ye, with a whiff of the old brimstone. I'm a grim bloody fable, with an unhappy bloody end!" Demoman, TF2
Additionally, in the TOS era, even in the JJ continuity, no one in the Federation had ever seen a Romulan. They didn't know that Romulans and Vulcans were related. So, even if they did count as part of the Vulcan population, which they don't, no one would have known about it anyway.
|
And beyond all of those points, you're missing an even bigger question than why there are only 10,000 Vulcans left. Namely, in the hours it took for Nero to drill into Vulcan, why were they only able to evacuate around 10,000 people from Vulcan? Ok, so Nero warps in and starts doing **** to Vulcan. Distress signal goes out. Starfleet warps in and dies. Maaaybe that should've been an indication that people should GET THE HELL OUT OF THERE BEFORE SOMETHING REALLY REALLY BAD HAPPENS!!! And it's not like they wouldn't have any ships. There would've been interplanetary shuttles, cargo ships, the Vulcan Science Academy's own fleet. They had options. Instead, they sat around with their thumbs up their ***** while a big scary ship sits in orbit, kicks the **** out of a small fleet, and drills into the center of the planet. Seriously, how many signs did they need before they realized that something bad was going to happen? |
As soon as Spock realized what Nero was doing, he ordered Uhura to signal a planetary evacuation. The planet was destroyed just a couple of minutes later. That's not a lot of time to evacuate an entire planet. And as far as I can see, there were only two modes of escape from Vulcan. One: board a shuttle and take off really fast. Two: find a transporter room that can beam you on board the Enterprise. And they didn't have long: even before Spock beamed up its clear large parts of the planet were already unstable or uninhabitable.
[Guide to Defense] [Scrapper Secondaries Comparison] [Archetype Popularity Analysis]
In one little corner of the universe, there's nothing more irritating than a misfile...
(Please support the best webcomic about a cosmic universal realignment by impaired angelic interference resulting in identity crisis angst. Or I release the pigmy water thieves.)
Well, you know what they say about when you assume.
It is highly illogical
"Ben is short for Frank."
-Baffling Beer-Man, The Tenacious 3: The Movie
[IMG]http://i197.photobucket.com/albums/aa10/BafflingBeerman/teamjackface1.jpg[/IMG]
That's actually somewhat wrong Nightblade, there are others that are not "Vulcan" or Romulans. It's actually a focal point of a few episodes of TNG.
Spock was not the first Vulcan in Starfleet.... T'pol was. He may have been the only at the time. Officially noone had seen a Romulan for a long time, but Humans had, and Vulcans did know that they were related to Romulans. the distress call was for an earth quake evac...apparently they didn't see the giant ship and such.. Also again it was a "anyone in range that can help" type alert, not a "oh **** we gettin blown up" type alert and if any other alert went out before then starfleet would have known of it and it is general protocol to send a message back saying we're on the way. As far as the why Romulans left, that is likely a lie or been warped over time as the teaching of Surak had beened and so many other things are so I would never take that at face value... |
Damn Superboy Prime and his time punches!
I say they just use the number "40" to mean "a lot" and move on. Forty people died on Vulcan; there were only forty survivors. They lost over 99% of their people.
We don't actually know that. Its plausible to suspect that the proto-Romulans that left Vulcan took basically most or all of the exploratory types with them, leaving behind a much more insular society. And we know Vulcans are not as diverse or as evoutionarily progressive as humans are: in Enterprise its revealed that Vulcans are actually afraid of humans, primarily because they are amazed that humanity was able to recover from a global nuclear war that destroyed their civilization in less than a century, something that took Vulcans over a millenium to accomplish. Vulcans are smart, but they were only a few decades ahead of humanity at the time of Enterprise after having more than a thousand year head start. They are not progressive people.
In many ways, Vulcans are analogs for historical Chinese. At one time China had huge exploration fleets and the best science and technology in the world. But it was Europeans who colonized much of the world, and when they did they didn't find very much in the way of Chinese outposts in their way. China withdrew, much as Vulcan could have. 10,000 does seem low given that Starships would still be out there, but if all Vulcan ships were primarily science vessels, its possible that such ships only contained crews of a hundred or so each, not a thousand like a ship comparable to Enterprise. |
If you pick and choose what parts of canon to accept, you're writing canon, not critiquing in.
|
Luminara, a bigger ship is easier to maintain because there are less moving parts. If you have to clean 100 tiny mechanism or 1 giant one it will take you usually several times as long to clean the 100 tiny ones than the 1 giant one. Also having 100 smaller one increases the chances of 1 of those will break down, while the bigger one while just as likely as any one of the smaller one to break down is less likely in terms of once it's up an running. And it also takes less material, so even if the big one break down its easier to replace.
[Guide to Defense] [Scrapper Secondaries Comparison] [Archetype Popularity Analysis]
In one little corner of the universe, there's nothing more irritating than a misfile...
(Please support the best webcomic about a cosmic universal realignment by impaired angelic interference resulting in identity crisis angst. Or I release the pigmy water thieves.)
No, what I am saying is that, according to canon, Vulcan history is known to have been distorted and it is reasonable to presume that the Vulcan/Romulan split was not due to Surak's teachings since Surak's teaching were different than what it was believed they were up until the 2160s if I remember right, and given not only the long life but the stubborness of Vulcans it is likely that even presently "Surak's teachings" are not his teachings, but rather a bastardization of both what Surak taught and what it was though he taught for those thousand years.
|
Moreover, Surak's teachings were distorted at the time of Enterprise but its clear that this was for the most part corrected with the discovery of the Kir Shara. By the time of either TOS or the Abrams Trek, the teachings of Surak would have been properly known. I'm pretty sure they included stuff like not conquering neighboring worlds somewhere in the fine print. Its also clear that Romulans rejected Surak's teachings of using logic to control emotions and passions.
[Guide to Defense] [Scrapper Secondaries Comparison] [Archetype Popularity Analysis]
In one little corner of the universe, there's nothing more irritating than a misfile...
(Please support the best webcomic about a cosmic universal realignment by impaired angelic interference resulting in identity crisis angst. Or I release the pigmy water thieves.)
Actually, its a continuity glitch that in the Abrams timeline, Vulcans and/or Humans must have made some contact with the Romulans that did not happen in the original timeline. In the original TOS timeline, humans had not seen a Romulan (in a manner that was widely reported) until the incident with the Enterprise. Spock theorizes at that time that Romulans might be an offshoot of Vulcans, something he implies is not a certain fact. But in the Abrams timeline, Spock states to Kirk that Romulans and Vulcans are related as a matter of fact statement without any controversy or doubt. That suggests events happened a little differently after the Kelvin incident than just Kirk's childhood history.
I would imagine that a planetary evacuation is not something that happens often, if almost ever. There was no evidence of a threat to the entire planet, and at the time the technology probably didn't exist to destroy a planet so completely. When a mysterious starship appears overhead and starts firing a weapon at the ground, I really don't think your first option is to evacuate the planet. You'd think that the big scary ship that just destroyed the starfleet expeditionary force might obliterate your evacuation fleet as well, or at least sizeable fractions of it. As soon as Spock realized what Nero was doing, he ordered Uhura to signal a planetary evacuation. The planet was destroyed just a couple of minutes later. That's not a lot of time to evacuate an entire planet. And as far as I can see, there were only two modes of escape from Vulcan. One: board a shuttle and take off really fast. Two: find a transporter room that can beam you on board the Enterprise. And they didn't have long: even before Spock beamed up its clear large parts of the planet were already unstable or uninhabitable. |
And ok, so planetary evacuations aren't that common an occurrence. Still, it seems to me that someone should've been paying enough attention to sound an alert after Nero destroyed the fleet sent to investigate. The planet must have some sort of sensor array that directs orbital traffic, which means that whoever was manning it would've known that the ships sent to investigate were turned into a brand new orbital debris field. Now I don't know about you all, but if I were on duty when the planet started shaking and a bunch of Starfleet ships-of-the-line were suddenly destroyed, I'd be telling people to evacuate on whatever ships were in orbit/planet side. At the very least I would start preparations for evacuation, so that if the call came it would go a lot faster and more people would make it off the planet.
Goodbye, I guess.
@Lord_Nightblade in Champions/Star Trek Online
nightblade7295@gmail.com if you want to stay in touch
I don't remember the first part, but it's been a while since I last watched JJTrek. And there are a lot of continuity errors like that (I blame Enterprise. For everything. Including JJTrek. And Final Frontier), which makes it hard to keep up.
And ok, so planetary evacuations aren't that common an occurrence. Still, it seems to me that someone should've been paying enough attention to sound an alert after Nero destroyed the fleet sent to investigate. The planet must have some sort of sensor array that directs orbital traffic, which means that whoever was manning it would've known that the ships sent to investigate were turned into a brand new orbital debris field. Now I don't know about you all, but if I were on duty when the planet started shaking and a bunch of Starfleet ships-of-the-line were suddenly destroyed, I'd be telling people to evacuate on whatever ships were in orbit/planet side. At the very least I would start preparations for evacuation, so that if the call came it would go a lot faster and more people would make it off the planet. |
How exactly do you prepare to evacuate an entire planet without actually doing it? Perhaps to their detriment, the Vulcans are unlikely to go on TV and say every man for themselves: make a break for it. They would have proceeded orderly and logically and my guess is many shuttle pilots died on the ground waiting for orders to depart or their passengers to arrive. They would not leave with empty craft when there were people heading to them for evacuation, and few if any knew exactly how much time they actually had. It might have been as little as two minutes. And panic is an emotional response.
Edit: I'm reminded of the Decker error. You're in command of a starship that is investigating a string of destroyed solar systems. You come across an incredibly powerful weapon that you cannot dent and is blowing your ship apart. So you beam your crew down to the safety of a nearby planet, whereupon the incredibly powerful weapon decides you're not interesting anymore and proceeds to destroy the planet you transported your crew to. In retrospect, perhaps not the best move. You are, after all, investigating destroyed solar systems. But you believe at the time that you're facing a weapon that will eventually kill you all and can do so easily, so you make the call, and it ends up being the wrong one. The Vulcans were in a similar situation. Unknown powerful enemy vessel capable of destroying an entire fleet. Logic suggests not sending up any more vulnerable starships, and protecting your people on the ground. Because logic doesn't warn you that the vessel is about to eliminate the ground.
[Guide to Defense] [Scrapper Secondaries Comparison] [Archetype Popularity Analysis]
In one little corner of the universe, there's nothing more irritating than a misfile...
(Please support the best webcomic about a cosmic universal realignment by impaired angelic interference resulting in identity crisis angst. Or I release the pigmy water thieves.)
a bigger ship is easier to maintain because there are less moving parts.
|
Think of a house. Now think of an apartment building. Which is more complicated and harder to maintain?
-np
I see myself as witty, urbane, highly talented, hugely successful with a keen sense of style. Plus of course my own special brand of modesty.
Virtue: Automatic Lenin | The Pink Guy | Superpowered | Guardia | Guardia Prime | Ultrapowered
Suppose the Vulcans were actually as on the ball as you expect them to be. We have an unknown vessel that is firing an energy weapon at the planet that is disrupting communications and transporter technology. It has destroyed a fleet of starships. At this moment, the logical thing to do would be to order the population in and around the area of the ship into civil defense shelters probably underground. The rest of the planet would be similarly warned to keep away from potential military targets such as spaceports. It would be illogical to head into space at this point in the face of an unknown enemy that is primarily shooting up starships and generating electromagnetic disruptions. No one either on Vulcan nor on Enterprise had any idea that the safest thing to do was *not* to head underground shelters until Nero shot the red matter into the borehole. At that moment, most of the population was not primed to evacuate the planet.
How exactly do you prepare to evacuate an entire planet without actually doing it? Perhaps to their detriment, the Vulcans are unlikely to go on TV and say every man for themselves: make a break for it. They would have proceeded orderly and logically and my guess is many shuttle pilots died on the ground waiting for orders to depart or their passengers to arrive. They would not leave with empty craft when there were people heading to them for evacuation, and few if any knew exactly how much time they actually had. It might have been as little as two minutes. And panic is an emotional response. Edit: I'm reminded of the Decker error. You're in command of a starship that is investigating a string of destroyed solar systems. You come across an incredibly powerful weapon that you cannot dent and is blowing your ship apart. So you beam your crew down to the safety of a nearby planet, whereupon the incredibly powerful weapon decides you're not interesting anymore and proceeds to destroy the planet you transported your crew to. In retrospect, perhaps not the best move. You are, after all, investigating destroyed solar systems. But you believe at the time that you're facing a weapon that will eventually kill you all and can do so easily, so you make the call, and it ends up being the wrong one. The Vulcans were in a similar situation. Unknown powerful enemy vessel capable of destroying an entire fleet. Logic suggests not sending up any more vulnerable starships, and protecting your people on the ground. Because logic doesn't warn you that the vessel is about to eliminate the ground. |
The thingy was...
Goodbye, I guess.
@Lord_Nightblade in Champions/Star Trek Online
nightblade7295@gmail.com if you want to stay in touch
No. The more functions you cram into a device, the more overly complicated it gets.
Think of a house. Now think of an apartment building. Which is more complicated and harder to maintain? |
Even if you had two or three, that's still way more concentrated value than I would ever recommend in a system intended to keep an entire species going. When you're talking about the survival of your race, six-sigma doesn't seem all that impressive anymore.
[Guide to Defense] [Scrapper Secondaries Comparison] [Archetype Popularity Analysis]
In one little corner of the universe, there's nothing more irritating than a misfile...
(Please support the best webcomic about a cosmic universal realignment by impaired angelic interference resulting in identity crisis angst. Or I release the pigmy water thieves.)
The Alt Alphabet ~ OPC: Other People's Characters ~ Terrific Screenshots of Cool ~ Superhero Fiction
There was one Starfleet ship (USS Intrepid) that was crewed entirely by Vulcans. It was mentioned in the Original Series episode "The Immunity Syndrome" (a.k.a the Giant Space Amoeba episode), and in the episode "Court Martial". According to Memory Alpha, "The Immunity Syndrome" occurred in 2268 which is 10 years after Vulcan is destroyed in the new movie, and "Court Martial" was in 2267. I don't know if the USS Intrepid was around at the time of Vulcan's destruction, but it likely was since it was a Constitution-class like the USS Enterprise.
|
The Alt Alphabet ~ OPC: Other People's Characters ~ Terrific Screenshots of Cool ~ Superhero Fiction
Quote:
|
In this instance, though, since Abrams' movie is considered a reboot, none of the other series or movies matters. So if Spock said only a few thousand Vulcans survived, then that's likely the case since he doesn't make a lot of mistakes.
The Alt Alphabet ~ OPC: Other People's Characters ~ Terrific Screenshots of Cool ~ Superhero Fiction
Luminara, a bigger ship is easier to maintain because there are less moving parts.
|
Furthermore, the larger your transportation unit, the more "stuff" you have to put into it to support the inhabitants, and unless you make it with magic, there is a point where that one large unit is using more "stuff" to keep it going than all of the smaller units would use combined. Additional cooling for working systems, extra backup systems to avoid wiping out the entire population in the event of failure of a single system, more spare parts which must be checked and tested for functionality regularly.
If you have to clean 100 tiny mechanism or 1 giant one it will take you usually several times as long to clean the 100 tiny ones than the 1 giant one. |
Also having 100 smaller one increases the chances of 1 of those will break down, while the bigger one while just as likely as any one of the smaller one to break down is less likely in terms of once it's up an running. |
If one smaller one breaks, it doesn't put the entire population at risk.
The larger one is more likely to break than a smaller one because it is more complex. Yes, it may have "less moving parts" than a hundred smaller ships, but that's irrelevant because 100 smaller units aren't going to suffer identical failures at the same time. In actuality, you can only compare the repair and maintenance time of a single large engine to the expected average for the smaller ships together.
Analogy: A single semi has fewer moving parts than a hundred mopeds. But a single semi is not easier to maintain or repair than a hundred mopeds, because a hundred mopeds won't all fail at the same time, won't all fail in exactly the same way and won't require exactly the same repairs. Nor is it easier to work on that semi, because the complexity of the the engine, fuel system, hydraulics, electrical system and mechanical parts are all far, far greater than the complexity of the mopeds.
The larger one is also more likely to break than the smaller ones because the parts are being used more heavily and with fewer rest periods for maintenance, replacement and adjustment. Smaller ships can stop, do maintenance or repairs, and catch back up to the fleet later. A large ship just breaks down and drifts, or kills the entire population if the failure is severe.
And it also takes less material, so even if the big one break down its easier to replace. |
Read up on ocean liners. They operate essentially identically to what you're describing for a "city ship". They aren't as simple as you'd like to believe, they don't have the material requirements that you espouse and the same is true of spacecraft.
Why is that a reasonable assumption? If the objection is that Vulcan is relatively insular and isolationist, then no percentage is necessarily reasonable. To take it to an extreme, if I were to say that millions of Vulcans were cannibals, based on the assumption that only one tenth of one percent of them eat other Vulcans, its clear the percentage is meaningless. There's no basis for assuming that percentage without evidence. Similarly, without evidence, there's no reason to assume some percentage of Vulcans must be off-world.
|
Luminara, You keep on saying bigger things are more complex. They aren't. 10 feet of rope is not more complex than 100 feet of rope. It just isn't. It's a larger amount to look after, clean, repair, and whatever else, but that doesn't make it more complex. It makes it take longer to clean, repair, traverse, or whatever on a 1 to 1 basis but on a 1 to 100 basis it makes it much much simpler and easier because even with redundant systems on the large one it is still a lot fewer than the 100 small ones.
As far as the Vulcan thing...How can you argue that all the Vulcans were on Vulcan. Vulcans are logical, they'd have had a secondary and tertiary colony at the very least because it is logical to get your species off a singular planet for just such an occurrence as the planet blows up.
Luminara is correct. Do you seriously think that rope is an accurate analogy to a ship?
Furio--Lvl 50+3 Fire/Fire/Fire Blaster, Virtue
Megadeth--Lvl 50+3 Necro/DM/Soul MM, Virtue
Veriandros--Lvl 50+3 Crab Soldier, Virtue
"So come and get me! I'll be waiting for ye, with a whiff of the old brimstone. I'm a grim bloody fable, with an unhappy bloody end!" Demoman, TF2
They aren't. 10 feet of rope is not more complex than 100 feet of rope. It just isn't. |
And despite that being the stupidest analogy possible, it can still be used to prove that you're wrong. When you extend the length of that rope 10x, you correspondingly increase the risk of breaking the rope as well. The longer it is, the greater the chance of failure at some point along the rope because it will have more flaws and you will have a greater likelihood of missing something during an inspection or repair. The only thing you've proven is that you know even less about any of what you've said than was previously in evidence.
Goodbye, I guess.
@Lord_Nightblade in Champions/Star Trek Online
nightblade7295@gmail.com if you want to stay in touch