Which had already been established in the Prime timeline.
Well if you're looking for realism, science fiction probably isn't your best bet. As technology gets better things have a tendency to get smaller, not larger.
I don't know. Then again, how many other COMMAND officers are on the Enterprise? Kirk, Sulu, Chekov and god knows who else have all taken temporary command of the ship when the CO is off the bridge. If Kirk and Spock were both killed on an away mission, Sulu would take command, and he would probably STAY in command until Starfleet came up with a very strong reason to replace him.Actually, my point is that this seems to be a relatively normal occurrence in Starfleet if said cadet is sufficiently qualified.So your point is that if a mistake was made by filmmakers in the past it should be okay to make that mistake again?
Which of course is the main problem with promoting Kirk, especially to that level of command. Presumably Saavik is already sufficiently qualified from a scientific point of view. You say "chief science officer on USS Grissom". How many other science officers were on board, do you recall?
No, she had the science officer's job; she just had to do all the REAL work while the Captain took all the credit.In any event she didn't have the same kinds or level of responsibility a Captain (of a flagship!) would have.
Starfleet isn't a Navy.I don't know, but I suspect NASA would be a somewhat different animal in a number of respects and if they do things differently to what you would expect from a Navy
Yep. As Kirk said to one of his students, "We learn by doing."But surely the academy is just the beginning of learning, not the end.
Of course not. The Enterprise is a ship, one which Kirk has -- through valorous conduct -- demonstrated himself fit to command.I presume by "earn it" you mean: showing he could do the job? I don't think the Enterprise should be treated as a bouquet of flowers or a bonus cheque.Even so, he still wound up having to earn it IMO.
I don't know. Then again, how many other COMMAND officers are on the Enterprise? Kirk, Sulu, Chekov and god knows who else have all taken temporary command of the ship when the CO is off the bridge. If Kirk and Spock were both killed on an away mission, Sulu would take command, and he would probably STAY in command until Starfleet came up with a very strong reason to replace him.
It could very well be that Starfleet officers are so highly trained in their jobs that the command officer's main skill set is his ability to "see the big picture" and coordinate all the different specialists under his command. In that sense, another analogy might be the practice of businesses to hire business-school graduates for management jobs despite the fact that some of those graduates have never run anything more complicated than a gas station.
Starfleet isn't a Navy.
Yep. As Kirk said to one of his students, "We learn by doing."
Of course not. The Enterprise is a ship, one which Kirk has -- through valorous conduct -- demonstrated himself fit to command.I presume by "earn it" you mean: showing he could do the job? I don't think the Enterprise should be treated as a bouquet of flowers or a bonus cheque.Even so, he still wound up having to earn it IMO.
Apparently it doesn't take much. You have to be smart enough to do the job (that's what the tests are for) and have the strength of character to do what is needed no matter what else is going on. Kirk's test scores are apparently second to none, but his CHARACTER was called into question with the Nibiru Fiasco. Those questions were decisively answered the moment Kirk climbed into the Enterprise's warp core and reset the damn thing in a cloud of radiation.
Last time I checked, Kirk is not in charge of Starfleet.Besides, your analogy might be closer if such "business-school graduates" were placed in charge of the companies that hire them or given a seat on their boards.
If you believe the tie-in materials (and you're clearly meant to given the references in the movie) he's actually been in command of the Enterprise for about a year before the Nibiru mission.And nuKirk hadn't really done that much when first promoted to command the Enterprise. Ironically, having been in the job for a year or so when he was demoted, he at least had some working experience of the job by that stage.
Starfleet gave him a medal. Giving him the Enterprise was Pike's idea.Not necessarily, courage, duty and loyalty are only parts of his character and don't guarantee he is the right person to command a Starship. Test scores aren't experience either. It does all help of course.But saying he got the Enterprise "through valorous conduct" still make it sound like a bunch of flowers (or a medal).
Exactly right. If Kirk had simply been upfront about how the Nibiru mission went down and owned up to his responsibility in the mission, Pike would have reprimanded him and sent him on his way. But falsifying his reports is a GIGANTIC no-no with serious implications otherwise.By the way, it has been suggested here previously that Kirk lost his command due to lying on his report to Starfleet rather than breaking the Prime Directive, which did save a sentient species afterall. I tend to agree. I imagine that is your impression too, given how often the PD gets broken.
Navigator.... same as Saavik was the best science officer and got THAT job as well.
Last time I checked, Kirk is not in charge of Starfleet.Besides, your analogy might be closer if such "business-school graduates" were placed in charge of the companies that hire them or given a seat on their boards.
Starfleet gave him a medal. Giving him the Enterprise was Pike's idea.Not necessarily, courage, duty and loyalty are only parts of his character and don't guarantee he is the right person to command a Starship. Test scores aren't experience either. It does all help of course.But saying he got the Enterprise "through valorous conduct" still make it sound like a bunch of flowers (or a medal).
Something else to consider is that it may not actually take a great deal of knowledge and experience to command a starship (Hell, Doctor Crusher even did this once). On the contrary, it takes a lot of knowledge and experience to be a GREAT commander of a starship. KirkPrime was arguably one of the best commanders in Starfleet history, a legend in his own time. NuKirk isn't much better off than J.T. Esteban.
It doesn't even appear that there was a problem with Kirk's judgement or command abilities. The problem seemed to be his capacity to face the consequences of his actions in a mature, adult way.
Which had already been established in the Prime timeline.
Precisely.
Of all the batshit insane things that Trek has pulled out of its ass from day one, landing the ship on a planet and submerging it is the unbelievable thing?
Prespective people.
Is there a reason why it should?Which had already been established in the Prime timeline.
Precisely.
Of all the batshit insane things that Trek has pulled out of its ass from day one, landing the ship on a planet and submerging it is the unbelievable thing?
Prespective people.
As you put it so elegantly these have been "batshit insane things" "from day one" yet did not prevent the nuTrek producers to further develop, feature and highlight these "batshit insane things".
Bob
Nonsensical does not equal fun. And the bottom line is, there was no reason at all for the Enterprise to dive underwater. None at all. I don't care about the science of it or anything, but there should have been some attempt to provide a story reason for why they submerged the ship. Which there wasn't.
Nonsensical does not equal fun. And the bottom line is, there was no reason at all for the Enterprise to dive underwater. None at all. I don't care about the science of it or anything, but there should have been some attempt to provide a story reason for why they submerged the ship. Which there wasn't.
Exactly.Nonsensical does not equal fun. And the bottom line is, there was no reason at all for the Enterprise to dive underwater. None at all. I don't care about the science of it or anything, but there should have been some attempt to provide a story reason for why they submerged the ship. Which there wasn't.
The absurdity IS the point. I've just rewatched the film and I was reminded of an aspect of it that I like more each time I view it (same goes for the first): somethings are left unexplained. There is no need to provide a "story reason" for the ship being underwater. We are simply coming into the story mid-stream. We can use our imaginations to come up with all sorts of reasons why it's there (as have been offered here and elsewhere) or we can ignore the reason and "go with the story as is". When did it become necessary for every single action or situation in a movie to have an explicit explanation in the movie? I absolutely HATE when movies do that--I'm not an infant, I can reason things out for myself.
"Realistic" doesn't either. In fact, when it comes to science fiction, it's usually the OPPOSITE of fun.Nonsensical does not equal fun.
The ADF novelization mentions that the entire island -- and the Volcano in particular -- were chock full of ferromagnetic materials that were screwing with their sensors, and transporter functions were limited to just a couple of kilometers. They had to be extremely close and within a direct line of sight to beam anyone down at all.And the bottom line is, there was no reason at all for the Enterprise to dive underwater. None at all. I don't care about the science of it or anything, but there should have been some attempt to provide a story reason for why they submerged the ship.
We use essential cookies to make this site work, and optional cookies to enhance your experience.