Leave a comment

Comments 9

bart_calendar December 6 2015, 14:39:31 UTC
What wasn't justified was trying to use the Death Star to blow up Yavin IV.

1. It put the most powerful weapon in the galaxy at risk - along with the thousands of people on it.

2. There are what, at most, 200 rebels on Yavin IV? Couldn't like two Star Destroyers and a bunch of X-wings wiped them out in a couple of hours?

3. As far as I can tell, the rebels have maybe 30 fighter ships. Certainly no more than that. So, even if the rebels tried to flee Yavin IV (making the idea of blowing up the planet even dumber) they could have been destroyed easily by an X-Wing swarm.

Reply

gonzo21 December 6 2015, 15:25:38 UTC
It was also pretty inexcusable to chart a path into the system that put the Deat Star deliberately behind a moon for so long. Instead of, you know, just shifting their approach over a few degrees.

Clearly there was a liberal terrorist sympathizer in charge of navigation.

Reply

drdoug December 7 2015, 12:36:15 UTC
I think the Rebellion must have infiltrated the navigation sections of the Imperial navy. As well as this situation, the Imperial Fleet comes out of hyperspace too close to the Hoth base and thus alerts the Rebels to the imminent attack. Vader blames Admiral Ozzel for this, without any investigation, but Rebel sympathisers in the navigation section may well have played a role.

Reply

gonzo21 December 7 2015, 12:39:43 UTC
I bet R2 implanted some backdoors into their code structure when he was plugged into the Death Star. The equivalent of them having left a USB port unprotected. That droid is the unknown hero of the Rebellion.

Reply


cartesiandaemon December 6 2015, 15:14:44 UTC
I felt sure Darth Vader had been shown gratuitously choking an underling who brought him bad news, but on checking, it seems like most of the people were at least personally responsible...

Reply


Leave a comment

Up