Showing posts with label Han Solo. Show all posts
Showing posts with label Han Solo. Show all posts

Thursday, April 16, 2020

Clone Wars -- "Deal No Deal" (Ep. 7.06)

-- Mistakes are valuable lessons often learned too late.


Ahsoka and her new friends get mixed up in some spice trading. This seems to be a not good thing. I think I would like to talk more about spice but, honestly, I don't really understand "spice" so have no coherent thoughts on it. It's pretty clear that the idea of "spice" started out as a drug reference or something pretty close to that. It's also pretty clear that Lucas "borrowed" the term from Dune. The fact that you mine spice, though, seems to have complicated everything about it as the Star Wars universe evolved. What is clear, though, is that there are two sides to the spice trade: the legit side... and the other one. Ahsoka and friends end up on the other one.

And I'm not going to go into that other than to say that Ahsoka is still trying to hide her Jedi-ness.

Kessel is more interesting and also seems to have suffered from the same issues that spice did during the evolution of the Star Wars universe. The spice mines, according to C-3PO, are a horrible place that no droid wants to be sent to. I have vague memories of the depiction of Kessel in one of the Han Solo novels I read when I was a kid, and my memories are not much like how the spice mines are depicted in Solo. But Clone Wars chooses to give us a broader view of the planet and reveals that the planet isn't all spice mine.

What's my takeaway from all of this? I can't really tell you.
Kessel has become something not quite as foreboding as how I thought of it as a kid. Or as foreboding as that book made it out to be (Where I think there were monsters that lived in the rocks? I don't really remember, but it seems like there was some monster thing that came out of the physical walls of the mine and tried to get Han. Look, it's been 40 years since I read that; I have other things in my brain now). Which is the problem, of course, with going back and giving any mystery an origin. [Like Marvel should never have gone back and given Wolverine a concrete origin. Biggest mistake Marvel ever made.]

Mostly, I'm not really getting into this arc. I appreciate the focus on Ahsoka, but I feel like they should have offered a more meaningful story. Or maybe it will turn out to be more meaningful; there's at least one more episode to go. At the moment, though, I would put this in the "throwaway story" bucket. The arc is giving us some interesting glimpses of things in the wider SWU, but the story itself is a little lacking.


"You got any skills?"

"You ever thought you might be the trouble she needs to stay away from?"

Friday, March 27, 2020

Rebels: "A Fool's Hope" (Ep. 4.14)

-- "That would be no problem for me."


Ezra sees a window to get Lothal out from under the thumb of the Empire; the problem is that rebel command has written Lothal off as a planet that can't be helped. Which is totally understandable considering the fact that they lost their entire attack fleet (mostly fighters) when they went after the TIE Defender program. Every last ship. The cost of Lothal is just too high.

But in many ways, Ezra is the last Jedi -- Sure, Ahsoka is out there, and so are Yoda and Obi-Wan, but they've all retreated into hiding, which only leaves Ezra out in the world. Alone. -- and he has a plan.

Most of this episode is battle sequences, including a duel between Ezra and Rukh. Exciting stuff.

The episode is also fairly typical, story-wise, which is fine. It's an exciting episode. However, there is, for me, a major flaw with the story, one which is too spoilery for me to talk about. I'll just say that it would have been a much more interesting story if they'd gone the other way with it rather than sticking to what is stereotypical for these kinds of things. Maybe there would have been too much involved in doing that in a series that's winding down; I don't know.

But the episode has Hondo, so I can't complain too much, even if they did have him throw himself all in with the rebels. I get it. They have to tie up all of the loose threads, and Hondo needs an honest-to-goodness happy ending, kind of like Han in Jedi.


"He talks a lot for a smuggler."

"For that boy, there is nothing I would not do." -- Hondo

"This is the risk you take when you are a pirate."

Sunday, February 23, 2020

Rebels: "Heroes of Mandalore: Part Two" (Ep. 4.02)

-- "A Mandalorian with a jet pack is a weapon."

This is an episode that is a bit difficult for me to review.
On the one hand, it's a fine and good episode in the same vein as all of Rebels, all of Star Wars, in fact. It's exciting in all the ways Star Wars is exciting.
However, it fails in the same way much of Star Wars does in really making the characters have real stakes in the game. The most notable exception to this was Rogue One.

Maybe I've said this before, but Lucas' original idea for Jedi was that the Falcon wouldn't make it out of the Death Star explosion at the end of the movie, hence Han's "funny feeling" comment before they go off to Endor. But Lucas had a change of heart and decided that that would end the trilogy on too much of a down note, and he wanted it to be a full-on happy ending, so Lando and the Falcon come spewing out of the fiery explosion of the Death Star.

In much the same way, the tragedy at the end of part of of this two-part story is rolled back as we discover right away that Sabine's mother and brother did not die from the Empire's powerful new weapon. Just everyone else did. I feel it robs the story of its emotional impact. But I suppose it is a show that is supposed to be kid friendly, which is why so many of the stormtroopers throughout the series escape with their lives rather than being killed by the rebels. You can't have your heroes indiscriminately killing the bad guys.

Yeah, I'm in a bit of a mood after watching this one.
And I haven't talked about the deus ex machina ending.
I'm also not going to.
bah


"Mandalorian? I don't want to be a Mandalorian."

"It's time for you to prove your loyalty, not just to your family, but to all of Mandalore."

"It was a series of bad decisions, okay?"

"Don't move!"
"Oh, I'm movin'."

Friday, June 8, 2018

Issues in Story Telling: Marked by a Lack of Tragedy


Those of you who keep up with this sort of thing probably already know that Solo has been under performing as a Star Wars movie and is looking to come in as the lowest grossing Star Wars film ever. Considering the subject matter, everyone's favorite smuggler, this is rather surprising. And alarming. It's caused some pondering on my part.

I thought it was a fine movie. Enjoyable. But I didn't love it. "Fine" is not a great recommendation for a Star Wars film, not from me, at any rate. Of course, the problem is that it's not getting a lot of love from... anywhere. The big question, then, is why.

I think I know the answer. Which is not the answer that everyone else is giving; all of those answers have to do with the problems on set, the firing of the original directing duo, and the fact that something like 70% of the movie had to be re-shot. The actual answer is much simpler: The movie is marked by a lack of tragedy.

It's not that every movie needs to have some kind of tragedy, but, I think, Star Wars movies do. They, at least, need to have that feel that there's something that could be lost, and that's true for most all stories. The risk of loss is what provides the tension in a story. Even when you know everything's going to turn out all right in the end, there needs to be that feeling of risk involved. That just doesn't exist in Solo.

Really, the whole movie can be summed up by that first game of sabaac. Han enters the game with nothing. He can't even get into it without someone else fronting him the money to get a seat at the table, which she does because... I don't know. As a business venture, it wasn't wise, because the only thing she has to go on is Han's word, "I can take him." (Or something to that effect.) So Han's in the game with absolutely nothing to lose. It doesn't matter that he wins enough to have a stack of money in front of him; if he loses, he's no worse off than he started.

And he does lose. But, you know, big deal. And Lando doesn't seem to care, either, that he doesn't have the ship he claimed to have which he'd put up against the Falcon in their final hand. It just doesn't come up again.

At any rate, you can't feel bad for Han's loss because he had nothing to lose, nor can you be upset at Lando for cheating, because Han was cheating, too, even if not so directly as having a card up his sleeve.

And you can't feel too badly for the loss of Han's "friends," either, since those relationships were about as real as the ship Han lost to Lando during their game of sabaacc. They're not friends just because you declare them so, no matter how much the writers wanted us to believe it. Tobias just doesn't become a Qui-Gon and there's no sense of loss when he dies; it doesn't matter that Han pulled the trigger. In fact, it's probably because Han pulls the trigger that, as the audience, we're so easily able to shrug it off.

I just wish it didn't make the movie so easy to shrug off, which I think it is. That's disappointing to me from a Star Wars movie. The franchise seems to have lost its way without Lucas at its head to give it an overall vision. Which isn't to say that it has to be Lucas doing that, but someone needs to do it. This "let each director do what he wants" shit isn't working out. Someone needs to bring balance back to the Force before its the loss of Star Wars itself that is the tragedy.

Monday, May 28, 2018

Solo (a movie review post)

I'm going to be honest; I was more than a little dubious going into this movie. I read many of the Han Solo novels when I was a kid and had a pretty good grasp of his backstory in my mind. Or at least my impressions of that backstory; it has been a long time since I read any of those books. The movie trailers didn't lead me to believe that Disney was going to do more than pay token respect to that backstory, much in the same way they have only paid token respect to what Lucas had planned for the future of the series. But here's the thing: Disney was upfront when they bought the Star Wars franchise: They said, then, that the vast majority of pre-existing material other than the movies would be viewed as non-canon material and they would be free to paint over it however they wanted to, which, actually, was not any different than what Lucas had already said. At any rate, there was not a lot of canon material about Han's past for Disney to have to cling to, so I suppose I'm glad they worked in as much of the previous Han lore as they did.

That said, I really enjoyed the movie, much more than I expected to, as I kind of expected to outright not like it. Seriously, the trailers were some of the worst ever and not very representative of the movie. I really have only one complaint, a rather philosophical one that I'll get to in a moment. First, the good:

Alden Ehrenreich: He's great. I already liked him a lot from his role in Hail, Caesar! He's fantastic in that, and that one role really shows off his versatility. He does a great job of stepping into Harrison Ford's shoes, and I never didn't believe him as Han.

Donald Glover: The first thing I ever saw him in was The Martian and, for such a small part, he may have been my favorite thing about that movie. He's a good fit for Lando, though I think all the people saying that he was channeling Billy Dee Williams are only saying that because they're not very familiar with Glover as an actor. He seemed very Glover to me, but being Donald Glover is very Lando, evidently. I hope we get to see more of him in this role.

The introduction into the movies of so much material that has never previously been in the movies: It was awesome to have the introduction of the Teras Kasi into the Star Wars canon, see the Pikes onscreen for the first time, deal with the Crimson Dawn... So much stuff! The two animated series (and I'm not talking Droids and Ewoks) have suddenly become much more important.

In fact, I can't even say how important, because that would involve a major spoiler. Major. And it was so good and cool. I mean, I don't have a lot of OMG! moments in movies, but I had one over this. And maybe shouldn't have, knowing the backstory from Clone Wars the way I do, but, really, I just didn't expect them to draw it into the movies. And, now, I'm really excited for the next Han Solo movie. You did know there was going to be another one, right? Another two, actually. Anyway, this is kind of on the scale of, "Luke, I am your father."

There's other good stuff, but these are the highlights. At least until I've seen it again. Maybe other things will strike me at that point.

But here's my philosophical issue:
Why is that every hero has to have some kind of tragic backstory? Like Luke (or Harry Potter) growing up an orphan? Or Han growing up on the streets of Corellia, also an orphan? And, maybe, that wouldn't be an issue if his backstory had started him out that way.

See, here's how it was:
Han was pretty much a normal kid. Not a rich kid, but his parents were well-off enough to send him to the Imperial Academy where he became a hotshot pilot. He was pretty self-absorbed. Why not? It's a big deal to be the best pilot at the Academy. Which is all why it's an even bigger deal when, one day, Han sees an Imperial officer beating a wookie slave and steps in to save the wookie. this is a kid who has never thought about anyone other than himself whose eyes are suddenly opened to this cruelty that is happening right in front of him and, rather than walking away as everyone else is doing, he interposes himself in the situation, saves the wookie, but has to go on the run.

The lesson he learned? Don't get involved. It only has bad results. Han had everything going for him, and he lost it all in one moment of compassion. Sure, he got a wookie with a life-debt to him out of the bargain, but who's to say if he would do it that way again if he had the chance to do it over? He lost all of his fame and glory in that one act.

That's a story I find compelling.

Much more so than the way he and Chewbacca become companions in the movie, which was more about saving himself than about saving a wookie. And there's no mention of a life debt in the movie; why would there be? It's a mutual life-saving.

Which is not to deride the movie. The movie is good. But it also stays squarely within convention. I get that Disney knows what people like and play to that masterfully, but I think they missed out on opportunity to make Han a much more nuanced character than he now is. Which is to say that they made him less nuanced than he was because they fell back on making him merely a stereotype, the male version of the "whore with a heart of gold." As Qi'ra says to him, "I know who you really are. You're the good guy." Or something like that.

Monday, January 8, 2018

The Last Jedi (a movie review?)

Yeah, the question mark up there is legit. I think this is going to be less a review about the movie and more about a review of Rian Johnson, who thinks he is way more clever than he actually is.
But there will still be spoilers.

But let's get the most obvious question out of the way: Did I enjoy the movie?
Well, yes, yes of course, I did. It was, after all, Star Wars, and it did, as Leia would say of Han, have its moments.

But it also had its moments.
Like why are all of the resistance ships running out of fuel at the exact same moment. That this is a question that I was having during my first viewing of the movie is wrong on so many levels. I mean, when did fuel become a thing? Luke hyperspaces all over the galaxy in his x-wing during The Empire Strikes Back, and there's never a mention or need for fuel, which is good since Dagobah would have been a lousy place to find a gas station. And Han flies the Falcon between star systems without a need for fuel. And I'm not even going to touch the idea that the fuel consumption rates on all of the Resistance ships would have had to have been basically the same no matter the size of the ship (WTF!) for them all to be needling empty at the same time.
Clearly this was a plot contrivance by Johnson, who seems to believe that stupid ideas are justified if they provide for "cool" moments. To be fair, this is also a problem Abrams has.

So was all the dumb of this "chase" scene worth the moment when Holdo hyperspaces the Resistance command ship into Snoke's star destroyer? I don't really know. That was a cool moment, but my thoughts leading up to it revolved around: This is so dumb. And it was kind of painful to watch all of that the second time. Not the hyperspace moment -- that was still cool -- but all of the chase leading up to it.

I also think it's a little weird how Poe is kind of constantly running up to people and greeting them with extreme enthusiasm, "Hey, Buddy!"

And I could go on, bit by bit, with the things that poke at me, but let's just not do that. I'll sum it up this way:
There are no moments like that whole fuel thing in the original trilogy. There's no point where I stop and think, "Wait a minute... That's kinda dumb." The thing most like that is the dianoga in the trash compactor, but there are legitimate explanations for that, so I have to shrug it off. You can't shrug off the fuel thing, not after eight other movies have failed to mention a need for fuel and, not just not mentioned it, demonstrated a distinct lack of that need.

That's just an example of the kind of thing Rian Johnson must feel is clever but really just isn't.

However, that's not the thing that bother me most. None of the logic problems that Johnson introduced are the things that bother me most. No, what bothers me most is Johnson's lack of respect for the story. Not the Star Wars story but story in general.
Here's the thing:

In the movie, Kylo "reveals" to Rey that she's a nobody. No one from nowhere. And that would be fine if... It would be fine if it was the truth. It would be fine if it was Kylo lying to Rey to get her to join him. It would be fine if Kylo was just wrong, that he read things the wrong way. It would be fine if there was a story reason for Kylo to tell Rey that. But... there's not.
And Rian Johnson doesn't have any say in the matter.

In a recent interview Johnson revealed that the only reason, the ONLY reason, he had Kylo say that is that he believed it was the thing that would most piss off the audience. He wanted to get a rise out of them. This puts him on par with George RR Martin in my book. "I want to piss off my audience because it's fun so I'm going to kill this character they all love." He further revealed that Abrams is the one who has final say in who Rey really is and nothing he wrote about it actually matters. Sure, maybe Abrams will decide to go with it, but Abrams isn't bound by anything that Johnson did. I suppose that includes the death of Snoke (another stupid moment, cool or not).

Which reveals the further problem of no one being in charge of these things. There's no controlling vision. You can say what you want about Lucas and the prequels or whatever, but, logically and plot-wise, all of his movies work together. He knew what he was doing and had a vision for getting there. The new movies, despite being completely entertaining, are beginning to feel piecemeal... because they are. This is something that Disney needs to get a grip on before the franchise begins to drift apart. They need to actually take a good look at what Marvel has done in keeping all of their movies moving forward within a unified vision.

I suppose I feel about the whole thing the way Mark Hamill put it when he said he didn't agree with any of the choices Johnson had Luke make but, after all, it's just a movie. That and, despite the enjoyment factor of Force Awakens and Last Jedi, I would much rather have seen what Lucas had intended to do with these than watch clashing egos slowly erode the franchise.

Friday, December 8, 2017

Rebels: "Blood Sisters" (Ep. 2.08)

"It was mostly just an accident."

I've mentioned before the lack of attention given to the female characters and who they are and where they came from. We got origin-type material for Ezra and Kanan and, even, Zeb fairly early on, but, until now, there's been very little background provided about Sabine or Hera. Not that there's a lot in this episode, but it's something.

So what do we know now?
Sabine used to be a bounty hunter.
I don't know; she seems a little young to have used to have been a bounty hunter, but I suppose that explains the Mandalorian armor.
She used to have a partner. And they... split up, not on the best of terms.
Which, of course, makes their reunion less than pleasant.

I wish I could say that there was some kind of moral dilemma in all of this -- I'm going to be spoilery here -- some kind of dealing with past emotional trauma or... something..., but there's not. The Empire conveniently shows up and puts the two "friends" back together again. In some ways, it's a "Han Solo scenario," but it doesn't quite go that far.

Anyway...

It's a fine episode. Lots of action. But it's another reminder that Rebels fails to tackle the difficult questions.

Monday, October 9, 2017

"Creative Differences" or White Male Privilege at Work

If you follow any Star Wars news at all, which I do...
Okay, that's not exactly true, as such. I don't actually follow Star Wars news or do any searching out of Star Wars news or follow any Star Wars sites. This is much different from my younger years when I did all of that stuff but, mostly, these days, I don't want to know anything ahead of time about the movies or what's going on, so I don't keep up on that stuff. Or any of the Marvel stuff, either. However, when there's news that makes the mainstream media cut, I notice it and, depending on what it is, I might go read it. Never, though, if it's talking about plot stuff or leaked stuff or anything stuff that has to do with the content of any project still in development.

So...

If you notice Star Wars news at all, which I do, you might have noticed recently that a couple of projects that are in development have lost their directors. The first was Episode IX director Colin Trevorrow and the second was the directing duo Phil Lord and Christopher Miller who were set to direct the upcoming solo Han film. [no, I'm not apologizing] The reason given in both circumstances was "creative differences."

But what does that even mean?

Or, you know, what does it mean in this particular circumstance? Because, based on things said, especially by Lord and Miller, I can tell you. It means that the directors believed, based on the fact that they were hired at all, that they should be allowed to do whatever the fuck they wanted to do with the movies without any regard to what Disney hired them to do. It was white privilege at work (because the guys who do this kind of shit are always white dudes who start whining about how they're not being allowed their creative freedom).

Now, I'm not going to get into the minutia of how Disney catalyzed the problem by trying to hire hot, new directors and offering them some amount of creative control (like allowing them to take part in the writing process (something that has had two non-successes so far)), because this is about doing the job you're hired to do.

So let's start with Lord and Miller, the guys behind The Lego Movie, Cloudy with a Chance of Meatballs, 21 Jump Street, and a bunch of other comedic offerings. Yeah, in hindsight, maybe not the best fit for a Star Wars film, but Disney wanted the Han Solo film to be a bit heavier on the humor than previous Star Wars movies, so they hired some guys who had shown themselves capable. And Lord and Miller were riding a popularity wave after the Lego thing.

Here's your analogy:
Disney hired Lord and Miller to paint their Han Solo room. They told Lord and Miller they could paint the room however they wanted to do it as long as they stayed within the provided color palette and didn't include any clowns. And, so, Lord and Miller start painting neon green (not an acceptable color) clowns everywhere. When confronted about it, they do the classic, "Let us do what we want or we're gonna quit!" Disney showed them the door.

And Trevorrow? His claim to fame is that he wrote and directed one of last summer's biggest movies, Jurassic World. Of course, he "wrote" it by re-making Jurassic Park. Yes, they are basically the same movie. Who knows what he wanted to do with Episode IX, but it wasn't what Disney told him they wanted, but he figured he was a big enough hot shot to not have to listen to Disney, so they let him walk, too.

And I get that some of you might think I'm reaching when I say this is white privilege at work, but you don't get this kind of attitude from little nobody people unless they're white dudes. Seriously, Trevorrow? I'm still trying to figure out why they thought he was a good idea in the first place. The guy's a hack with almost no experience. And, while Lord and Miller have been around awhile and made some movies that have been noticed, they're not exactly household names. All of them were hired to do fucking Star Wars, and they couldn't get their heads out of their own asses long enough to realize what was going on.

Probably some of you are going, "But millennials...," right about now, but none of these guys are millennials. They're all gen-x white dudes. Really, it's not millennials who think they're all special; it's mostly just white dudes. Of all kinds of ages.

I mean, seriously, you have to think pretty fucking highly of yourself to try to hi-jack a Star Wars movie to make a name for yourself. Outside of the fact that if you're hired to do a job, a specific job, you DO THE FUCKING JOB you were hired to do. You don't get to do some other job that you'd rather be doing. And when it's Disney and Star Wars... Did someone hit these guys in the heads with a hammer?

But, then, that's the kind of culture we've put in place, a culture where white cops get to shoot people of color and walk away from it. A culture where a white man brags of sexually assaulting women and white men vote for him to be president.

White dudes are always going on about millennials and how they think they're all "special snowflakes," but the only ones I see out there acting as if they're special is white dudes, which just makes me sad to be a white dude. And when you're such a white dude that you can't manage to collaborate on a Star Wars project... Well, there really aren't any words for that kind of assholery.

Friday, September 1, 2017

Blade Runner revisited (a movie review post)

You know how in just about every cop show these days they do crazy-insane enhancements on photos in order to catch the bad guy? My kids and I were watching something recently and they were doing that, and it occurred to me that that whole thing comes from Blade Runner. As far as I know, that's the first time that was used in a movie like that, and we all know how influential Blade Runner has been. It also occurred to me that only 1/3 of my kids had seen Blade Runner, so we set about fixing that. And, well, it had been a long time since I'd seen it and, with a sequel coming out, it seemed like a good time to watch it.

I chose the original theatrical version to show them 1. because that's the version that had such a huge impact on movies and pop culture, and 2. because it's been so long since I've watched any version that I couldn't really remember what the differences are beyond that some don't have the narration. I happen to like the narration; it gives the movie that film noir detective feel that is one of its appealing aspects to me.

The first thing that became apparent is that the movie has retained its very unique look and feel. It was original 35 years ago when it first came out and, despite the amount of influence it's had on other movies, has rarely had that visual tone duplicated. That's kind of amazing, actually.

Beyond the fact the movie time is now present time and that the movie isn't anything like the present, it holds up remarkably well. And it's still a conceivable future in that none of the things in it have become things we no longer think are possible. In fact, all of the sci-fi things in the movie are on track to one day just being science. Which is kind of scary, still, especially considering the environmental implications in the movie, and we haven't done anything to stop that bit of future from happening, either.

Really, the only piece of the movie that has worn on me is Rutger Hauer. Remember back in the 80s how Hauer was such a big deal after Blade Runner? Well, I do. He was a name... that didn't last. Because he wasn't really a great actor. And that goes for in Blade Runner, too. Granted, some of the issues with his character are a matter of the directing, but I'd be willing to bet that a better actor could have pulled off some of his flubs (like the howling) more believably. Which is not to say he doesn't have his good moments, but he's probably the only real weakness in the film as a whole.

Unless you want to talk about Sean Young and her huge 80s hair, because wow... It should have been listed separately in the credits.

I'd say it's still a movie worth watching with a message that is still just as important now as it ever was. Even though I've read Do Androids Dream of Electric Sheep?, watching the movie makes me want to go back and read that again, too. I'm not going to, right now, but I want to, and you have to give credit to an adaptation that makes you want to go back to the source material. Again. And watching it again makes me both hopeful and fearful of Blade Runner 2049...

I definitely think there's more to explore in the world that was created for the first film; I just hope it's good. Harrison Ford said the script for 2049 is the best script he's ever read, but, then, he's the guy who wanted Han Solo to die, so I don't know if his opinion is trustworthy. At least Ridley Scott isn't directing it; he's more miss than hit.

Tuesday, March 14, 2017

Clone Wars -- "A Test of Strength" (Ep. 5.6)

-- The young are often underestimated.


[Remember, you can sign up to join the Clone Wars Project at any time by clicking this link.]
[Well, actually, considering that we're into season five, now, probably no one new is going to sign up, BUT! Hop over to The Armchair Squid for his take on the current episode.]


It's important to remember that Hondo is a pirate. Of course, he's a pirate in the same vein as Han Solo and Lando Calrissian: a charming rogue. It makes it easy to be taken in by him, characters and viewers alike. But, then, he does something every so often to remind us he really is just a pirate. It doesn't matter how "presidential" he sounds during his not-the-state-of-the-union address, he's still gonna cut your throat for profit if he thinks he's going to make some from doing it. There is no, and there never was, doing the right thing. He just fools you into thinking that when he's making money by being nice to you. But it all comes down to, "We all know how much I like to be rich, don't we?"

In the end, it makes Hondo no better, and possibly worse, than Anakin during and after his fall.

And this is how bad it is:
During the conflict when Hondo is obviously and blatantly trying to kill Ahsoka and those under her charge, Ahsoka says to him, "I don't want to hurt you." And she doesn't. Do you know why? She likes Hondo, just like we do, because why? Because he's a charming rogue, and you can't help yourself. Even while he's trying to slit your throat. Hondo's response? "I know." That's not a direct quote, but it's the spirit of it, and it gives Hondo the edge.

Oh, yeah, Honda is in this episode.

And David Tennant, my second favorite Doctor. Oh, no, not him, just his voice, but that's good, too.

Yes, we're still in the same arc started last episode. Let's just say it doesn't end well. You should probably just watch it.


"The lightsaber is a Jedi's only true ally."

Tuesday, November 15, 2016

Clone Wars -- "Kidnapped" (Ep. 4.11)

-- Where we are going always reflects where we came from.


[Remember, you can sign up to join the Clone Wars Project at any time by clicking this link.]


A theme Star Wars returns to rather more frequently than you'd think -- or, at least, I'd think -- is slavery. Chewbacca was a slave, freed by Han. Anakin was a slave, freed by Qui-Gon. The Hutts run slaves. The Trandoshans trade in slaves. And those are just the ones I can think of off the top of my head. Oh, and the Empire, because Chewbacca was a slave owned by the Empire.

"Kidnapped" introduces a new race that specializes in trading in slaves, the Zygerrians. At least, they used to specialize in it before the Jedi shut down their slave trading ways. The problem is that the Zygerrians have been holding a grudge and have joined forces with the Separatists in the hopes that they will be able to re-establish themselves and their slave market. Their opening gambit is to invade the planet Kiros, a colony of the Togruta, a peaceful people who have no weapons.

The wrinkle? Ahsoka is Togruta.

When the Jedi arrive to assist the Togruta population, they don't find them. Any of them. All of which leads to an interesting face off between Obi-Wan and Darts D'Nar, the Zygerrian leader of the Separatist forces.

That's about all I can say without spoilers. It's a good, solid episode, and a good start to this arc.

Tuesday, July 12, 2016

Clone Wars -- "Overlords" (Ep. 3.15)

-- Balance is found in the one who faces his guilt.


[Remember, you can sign up to join the Clone Wars Project at any time by clicking this link.]


Other than that the Force exists, Star Wars doesn't often stray into the realm of metaphysics, even when dealing with Jedi training. There are moments, as with Yoda's speech in The Empire Strikes Back:
For my ally is the Force, and a powerful ally it is. Life creates it, makes it grow. Its energy surrounds us and binds us. Luminous beings are we, not this crude matter. You must feel the Force around you. Here. Between you, me, the tree, the rock, everywhere! Yes, even between the land and the ship.
Then Yoda lifts Luke's x-wing out of the swamp to prove his point. But, on the whole, the show tends to take a much more Han Solo view of the Force.

"Overlords," though, firmly steps into the realm of metaphysics and deals very directly with aspects of the Force that we've never seen before. And, other than this story arc, may never see again. Considering that The Clone Wars is canon, it makes me wonder how the events here relate to what's going on in The Force Awakens, because it almost has to relate. [Except for the fact that Abrams probably didn't see these episodes or do any research into what he was talking about or what he meant when Snoke said, "There has been an awakening in the Force." We just have to hope that other people who know more about what's going on were paying attention and keeping things on track.]

This episode also directly addresses what it means that Anakin is "the chosen one." Hopefully, without giving anything away, or at least too much away, the idea here deals with potential. Not only must Anakin have the potential to be the chosen one, but he has to choose it. So many stories deal with this idea in terms of absolutes. "You are the chosen one, so are the chose one. It is your destiny, your fate, and there is nothing you can do about it." I like very much the idea that Anakin must make a choice to be "the chosen one."

More than any other story arc in The Clone Wars, I think this one is a must see. Whether you enjoy the story or not, if you're a fan of Star Wars, this is essential viewing.
Personally, this is my favorite arc from the whole series. I wish they had delved more into this story and these characters.

Friday, February 26, 2016

Rebels: "Spark of Rebellion" -- Part 2 (Ep. 1.1b)

"You're about as bright as a binary droid."

The real question in this two-part opening to Rebels is, "Is Ezra a good guy?" Ezra doesn't seem to think so. He looks out for himself. Period. At least, that's his perception of himself. It's all rather Han Solo. Of course, as with Han, Ezra finds out he can't so easily turn his back on those in need.

Which gets him into trouble.
And allows him the opportunity to find out whether he can depend upon the crew of the Ghost.

Oh, and, also, Kanan, the captain of Ghost, or at least the leader of the little rebel group that operates on the Ghost, is a Jedi.

But... Wait! What about Order 66?
Yeah, I hear you out there.

Order 66 didn't quite get all of the Jedi, just almost all. There's that whole thing about Darth Vader hunting down and killing the remnants of the Order. Kanan was one of the survivors. So the question is simple:
Did he get lucky or is he that good?
That, I suppose, is something we'll have to wait and find out.

And, yeah, I want to find out.
I'm still not happy about losing Clone Wars, but I'll take Rebels as a reasonable substitute.
I'll note again, though, that Rebels is a show that is unambiguously targeting a younger demographic. You can even see it in the animation style. I don't know. Maybe that it clearly targets kids as its viewing audience allows adults to feel more at ease watching it. It's clearly defined, and adults seem to need stricter definitions than kids. So it's okay to watch a "kid show" if you know that's what you're doing, but it makes you ill-at-ease to watch a show that skews to both markets. Or something.

Monday, January 18, 2016

Star Wars: A Discussion (Episode VI)

One of the big questions around my house (mostly from my daughter because she loves R2-D2) leading up to The Force Awakens was, "Why is there a new droid?" It's a fair question but one I mostly had to shrug at when she would ask it. My wife, though, gave the cynical (but probably accurate) answer of "merchandising."

However, after seeing the movie, I think the impetus lies elsewhere. This is how I imagine it going:

Abrams: We have a problem.
Disney: What's that?
Abrams: I gotta go fast.
Disney: We, um, don't know what you mean.
Abrams: That's okay; I don't either. But this movie is going to be fast! Lots of running.
Disney: Yeah, so?
Abrams: Bro, R2 is slow. He can't keep up with all the action I'm gonna throw! I need a droid we won't have to tow. It's gotta go fast!
Disney stares at Abrams for several long minutes. Abrams is virtually vibrating in his seat.
Disney: So what you're saying is that you want a new droid?
Huey Lewis music suddenly wafts through the air with the words, "I want a new droid. One that does what it should. One that won't make me feel too slow, one that'll help my livelihood." It suddenly stops and Disney smiles.
Disney: Oh! You want a new droid! A fast droid! Yes! We'll make you a new droid.
Abrams: Great! Awesome! I gotta go fast!

Yeah, that's kind of how it goes in my head. Abrams gets a droid that can roll and bounce along on the ground with Rey and Finn as they run like crazy and Disney gets a brand new cute droid to merchandise the hell out of.

And, well, that worked. Yes, my daughter loves R2 but, now, she also loves BB-8. "He's so cute!"

But, you know, BB-8 is a fine addition to the movies. He rather subverts R2's  observational role but, hey!, Disney has subverted many things with their whole "making a movie for the fans" thing. He, the droid, was fun, and that's what counts, right?

However, not all of what made it into The Force Awakens works so well as BB-8, Starkiller Base, for instance. Setting aside the fact that this is part of the whole repetitive story issue (but seriously! again?), how does this even work? It's like they forgot to think the whole thing through (but at least it's not as bad as "red matter" (because, really, "red matter" was the best you could come up with, Abrams?)). I can be okay with them building a Death Star inside of a planet, but there are... let's call them inconsistencies:
1. Starkiller Base destroys the Hosnian system. Where did it get the energy for that blast? You're not going to convince that it "came loaded with one shot already available." Sure, as my wife pointed out, maybe it was a binary star system, but that doesn't ring true to me. It still had an atmosphere and plant life on the surface, so it hadn't come from some other system first. It had to be still in its home system.
2. The Star Wars database says that the beam from Starkiller Base travels through hyperspace, which explains how it gets to Hosnian Prime so quickly. But, if it's travelling through hyperspace, why can we see it? Come on guys; that's just not cool. Don't break the rules just because you want everyone to watch the beam go by and be all "oooh..." at it.

Oh, and see, I had to go to the Star Wars database to find that out about the beam going through hyperspace (because prior to looking, I was miffed that the beam shot across the galaxy in seconds), which is something something that irks me. I shouldn't need to go looking outside the movie for explanations of things inside the movie. Like the thing with Ren's lightsaber and why it's built that way (because there's an actual reason beyond it looking cool). That's one thing Lucas did very well: He gave us all the information we needed within the movies. And you might say that knowing why Ren's lightsaber looking the way it does (and I mean the flame-like appearance of the blade, not the cross-hilt) is not necessary, but an aberration like that popping up after six movies of lightsabers not looking like that begs the question. I shouldn't need to go out of the movie to find "why?"

And, yes, maybe that info will come in backstory in the next movie. Who knows. If that was the only thing, it wouldn't bother me, but that's just a prime example of a lot of things in this movie where Disney put the information in some other medium so that you have to buy a book or a comic book or whatever to find out. Irksome. And damaging to the integrity of the movie.

The other big problem I have with the movie is that everyone knows everything right away all the time. It's very un-Star Wars. I mean, the search for the droids by the Empire in A New Hope is part of what gave the early part of the movie its tension. But in this one, everyone knows that BB-8 is BB-8 as soon as they see it, and the First Order just shows up. But, you know, gotta go fast! It's not restricted to the First Order, though; it's everyone all the time. Rey and Finn steal the Falcon: Han shows up. [I'm sorry; there's no good explanation for that.] Then both rival gangs show up. Not to mention the Resistance showing up to take down the First Order when they're attacking Maz's place. There's just too much everyone knowing everything and/or coincidence.

And don't even get me started on the whole "map to Luke Skywalker" thing. Why is there a map to a person? And how exactly is that bit of the galaxy "uncharted" when it clearly fits within a map of the entire charted galaxy. Oh, wait... I said don't get me started. Oops.

So, yeah, I like the movie, but I'm not in love with it the way I am with the rest of Star Wars. Not right now. I'm sure it will grow on me but, right now, it's like the one kid who is constantly getting into everything and you keep having to say "stoooop!" to. You love the kid, but you just wish s/he would go away for a while and quit making noise. And, yes, darnit! I want to go see it again.

Next: 3D!

Friday, January 1, 2016

Star Wars: A Discussion (Episode I)

This is not a review; that will come later.

Those of you who know me at all or who have been following for a while probably know (ought to know) that I went to see The Force Awakens at the earliest possible showing. What that turned into was seeing it twice on "opening day," which was not, actually, opening day, because it was the day before opening day. Fortunately one of those showings was at 7:00 because the main thing I learned is that I am definitely getting too old for midnight shows, which the second viewing was. I also learned that my boys have nowhere near the stamina I did at their ages as both of them also struggled with the midnight viewing. Up until a few years ago, midnight shows where commonplace in my movie viewing repertoire.

All of which is, of course, beside the point other than the fact that when I said to my sons, "I'm getting too old for this sort of thing," as we were leaving the theater (at 2:30am!), they didn't get it. Yes, I was disappointed.
Anyway...

I want to provide some context for the upcoming review and the things I say about Force Awakens before I actually get to talking about that movie.

I have always said that Star Wars changed my life, and I mean that in a very literal sense. Even as a teenager looking back at my childhood, I could see the point where Star Wars came into my childhood and changed my path. Before Star Wars, everything was dinosaurs and cowboys and Indians. Everything changed when I seven. I was one person entering the theater and someone else when I came out. To again borrow the words of Ben Kenobi, I'd taken my first step into a larger world.

Star Wars never faded from my life, though it faded from the world around me. My Star Wars toys decorated my room all the way through the 80s, long after everyone had forgotten Return of the Jedi, and into the 90s just waiting for the resurgence that happened with the release of Zahn's Star Wars novels and the Dark Empire comic book series from Dark Horse in the early 90s. Needless to say, I was elated when Lucas announced the special edition versions of the movies.

And I remained elated after I saw them.

Let me be clear, I am not a part of the "Han shot first" crowd. I am from the "Han shot" era. That was it. Han shot. The whole argument over Han shooting first annoys me to no end. That being said, I have no issue with Lucas adding in the thing with Greedo shooting. It doesn't destroy my childhood or the movie or, even, damage them. I get it. Star Wars became a thing that's much bigger than Lucas ever imagined it would be and making Han a better role model for kids is something I can understand.

There was only one thing they added to the special editions that I didn't like, the scream by Luke as he dropped into the shaft in Cloud City after the duel with Vader, and they later took that back out.

And then there were the prequels...
Let's make that next post, shall we?

Tuesday, August 25, 2015

Clone Wars -- "Jedi Crash" (Ep. 1.13)

-- Greed and fear of loss are the roots that lead to the tree of evil.

[Remember, you can sign up to join the Clone Wars Project at any time by clicking this link.]

This episode opens with one of those huge, spectacular battle sequences. We don't get those all the time in Clone Wars because, I'm assuming, of the time and expense in producing them, which, I know, sounds weird for animation (it's just coloring, right?) but is true nonetheless. And I do understand that they're "just animated" (but, after all, that's what CGI is, too, and this stuff is basically the same), but they're still spectacular.

This is another episode which features on a fan favorite Jedi from the movies: Aayla Secura. I think when you look at the character, you can easily identify why she's such a favorite. heh

This is an interesting episode in that Anakin and Ahsoka are coming to Secura's aid, but Anakin is badly wounded and it's Secura and Ahsoka who have to rescue him. Amidst many, many complications. Including incorrect hyperspace coordinates which, as Han Solo told us, can lead to flying right through a star. Um, yikes! Because that's right where they're headed.

This episode centers on a philosophical question, which the series does from time to time:
Does fighting for peace justify fighting? As one of the characters says, "It takes two to fight." It is a legitimate question with no good answers. After all, Jesus said, "Turn the other cheek." It may be something that's easier done by an individual rather than by a whole society, though, because how can you choose to let an aggressor subjugate or enslave a group of people unopposed? The show doesn't try to answer the question; it merely poses the conflict between the two ways.

I think that's the mark of a good show, though: It poses the questions and doesn't try to tell you how to think about it, just that you ought to think about it. So, yeah, what if someone did a throw a war and one side just didn't show up? Is that even a possible thing? Maybe not, but maybe it could be.

Wednesday, May 27, 2015

The Clone Wars is coming...

I see some of you out there shaking your heads and thinking, "You're a little late to the party," but just give me a moment. I don't mean The Clone Wars is coming to TV; I mean The Clone Wars is coming to my blog! Sounds awesome, yes? Yes! Of course, it does.

In conjunction with The Armchair Squid, we'll be going through each episode on a weekly basis and evaluating and reviewing them. That means that for... well, like, a couple of years, I guess, there will be a weekly Clone Wars post. If you haven't watched this show and you like Star Wars at all, you really should watch it, and this is a great excuse to do it. This is easily one of the best animated shows ever on TV and, actually, one of the best sci-fi shows, animated or not. Trust me; I've been known to watch some bad sci-fi, and this is not that. If you've already seen it, well, you know you should get in on this. If you want to sign up, just follow the link over to Squid's blog and get signed up!

Now, a few words... which is difficult, because I want to say a lot of words about a lot of different things, but, then, that's a lot of different things, and I don't want this post to go on all season. So let's talk canon. Hey! Pay attention! I said "canon," not "cannon." We are not shooting explosives at people. Here, we use more elegant words from a... okay, well, not so civilized age. Anyway...

Last year, when Disney took over Star Wars, one of the first things they did was to "do away" with the Star Wars Expanded Universe. I have found this whole thing amusing, but the statement they were making had to be made. But let's back up a moment.

Prior to 1991, the only Star Wars canon was the original trilogy. Sure, there were a handful of books in existence (Splinter of the Mind's Eye, some Han Solo books, a Lando book or three), but no one took those as real, especially since some things like Luke cutting Vader's arm off certainly didn't happen within the movie time line. Those books were just fun things on the side. But all of that changed in 1991 due to a couple of events:
1. The publication of Heir to the Empire by Timothy Zahn.
2. Dark Horse comics' release of Dark Empire #1.

Both of these series take place after Return of the Jedi and are responsible for bringing Star Wars back into the American consciousness. One way or the other, you can probably thank Timothy Zahn for the fact that the prequels exist. It was his Thrawn trilogy (and everything that happened after because of it) that showed Lucas that there was still an interest in Star Wars.

Interesting fact:
Zahn originally wanted to write a trilogy set during the Clone Wars. Lucas said "no" because he knew that if he did ever make the prequels (because at that point he had no plans to do that), they would invalidate the books Zahn wanted to write. So Zahn reformed his clone story and set it after Jedi.

Now, here's the thing:
Lucas always said that anything done outside of the movies could be invalidated at any time (see Splinter of the Mind's Eye) and was never considered canon, hence the Expanded Universe. That's what it was: non-canonical material. But, over time, as there became more and more of it and people became more and more invested in it, even people at Lucasfilm, people began to view the EU as being pretty much as valid as anything Lucas himself did. People had come to view the EU as canonical even though they had been told again and again that it wasn't.

When Disney came in with their plans to officially expand the Star Wars universe, to provide a vast tapestry of new canon, they had to make a hard statement so that people would understand that they weren't going to accommodate the EU into their plans. So "the EU doesn't exist anymore" was a clear way of stating that.

The Clone Wars, though, having come from Lucas, is official Star Wars canon. This is the story. I think it's a good one. I hope you come along for the ride.

Tuesday, January 28, 2014

Vader's Offspring

My two younger kids got these books for Christmas. I have to say they're pretty awesome. Sure, they look like books for kids. Little kids. I'm sure it's because they're picture books. But they're those kinds of books that look like they're for kids when they're really for adults, like Animaniacs is a cartoon that's really for adults. Sure, kids like it, but kids don't get it; they just think it's funny when an anvil falls on someone's head. Which, I have to admit, can be freaking hilarious. Wait, I'm not making my point, am I?
You do know there was a Star Wars Animaniacs special, don't you? Totally awesome.

Wait! Wait! I'm talking about these books by Jeffrey Brown.
The books have brightly colored pictures that are easily appealing to kids. Funny things happen, like Luke hitting Lobot in the head with pasta sauce at dinner, which are also appealing to kids. However, it takes a certain knowledge of Star Wars and of being a parent for these books to really hit home.

I love Darth Vader and Son. It captures a moment when Luke is probably around six or so and is a great picture of what it's like to be a dad. As in the scene with the pasta sauce: Vader's hand is to his forehead in that great "I can't believe he just did that" pose. This, though, is one of my favorites:
It takes a classic situation and puts a great Star Wars spin on it. The whole book is like that.

Vader's little princess is good, too, but it doesn't quite live up to Vader and Son. Mostly, it's because he used all the great kid moments in the one about Luke. Because of that, the one with Leia is less focused and strays up into teenagerdom and young adulthood. I have to say, though, that some of the dating stuff with Han is pretty funny. Here's one of my favorites from Leia's book:
The books are a lot of fun if you're Star Wars fan and worth having around as conversation pieces, if nothing else. But, if you're not going to buy them, you should at least make a special trip to the bookstore to check them out. They don't take long to read, and it's totally worth it.

Sunday, January 12, 2014

It's a Lego Christmas (with a dose of Doctor Who) -- Part Two

Before we get to the BIG Lego events of Christmas, here is the first of the Lego sets that I got. These were sort of consolation Lego gifts because the Lego set I really wanted became unavailable. And was, actually, too expensive, but my kids had this plan to combine their money and buy it for me. That's actually a longer (and unimportant) story. As it turns out, though, that set was on its way to retirement, so there was no re-stocking of it as places ran out of it, and my kids waited too long to try to fulfill their plans. So I got this, which was pretty cool (and approved by Mr. Bunches):
I want to point out that Admiral Ackbar came with a beer mug. I have to assume it's a beer mug, because it's  not like the cups that come with other sets that are clearly coffee mugs. Ackbar comes with a space beer mug, and I don't really understand why. Han comes with his blaster, which makes sense, and the pilot comes with a large wrench (as seen in Han's hand because the pilot is busy about to take off), which makes less sense (because why would the pilot need a wrench?), but it makes much more sense than the Admiral and his beer mug. Unless Ackbar has a problem that we've never been privy to? What makes less sense than that, though, is why Han comes with an A-wing fighter. It's like they had an extra batch of Solo minifigures lying around so they just threw them in with the A-wing. And Ackbar. But Ackbar doesn't have his own ship, so I suppose they needed to put him somewhere. The A-wing is really cool, though, so I'm not complaining.

I also got
Okay, that's not actually true. My younger son got it, but he already had this one, so he gave it to me. It was part of his new planet Lego sets. That is not an A-wing, just so you know. Here are all of this year's planet sets together:
My daughter's Lego Advent calendar for this year:
After the fact, that is. This is the little Christmas party she made from what came in it.

Which brings us to the big Lego project for this year. My younger son, the most devout Lego enthusiast in our house (and at his school) got
the Republic Gunship! Here are some in progress shots:

But the BIG Lego event was actually a contest. My younger son and I actually received a duplicate Lego kit, so he challenged me to a race. I just want to make it very clear that I don't spend a lot of time putting together Lego kits at this stage of my life. In fact, I can't remember how long it's been since I've put one together. Probably half a dozen years, at least. But I couldn't very well say no. So we got set up:
I prepared with... tea. He prepared by sorting all of his pieces out so that he could find them more quickly. Clearly, my lack of recent experience in this worked against me. Our first time stop for progress pics:
That's my son's stuff right up front there. You can see mine to the upper left. He is clearly already in the lead.
The second time stop:
That's mine at the bottom, this time. My son's is at the upper right, and you can see that he is still in the lead. Can I come back for the surprise finish and win the race!?
Actually, no.
My son's model is finished, and mine is... well, not finished, as you can see from the picture. It wasn't as close as it looks from this shot, either. I had something like 15 more minutes of building to go. Or more. I don't remember, exactly. What I remember is that he finished way before me. But here are both Mandalorian Speeders sitting next to each other once I did get mine finished.
Clearly, I need more practice at this if I'm going to pose any kind of threat to my son next Christmas.

And that's our Christmas, or most of it, in a nutshell.
My daughter is already counting down to this year's Christmas. yea?

Thursday, November 14, 2013

You Know You've Made It When...

You know you've made it as an actor when you get turned into a Lego minifigure. I think it used to be when you were turned into any kind of action figure, but, these days, especially after McFarlane Toys came onto the scene in the mid-90s, almost anyone can get turned into an action figure. It ceased to be something difficult to achieve. However, it's still noteworthy to get turned into a minifigure even if minifigures don't look like the actors.

Even more noteworthy? Getting turned into two completely different minifigures. And, yes, okay, this topic completely came out of a conversation with my sons. They have a completely disregard for action figures because, well, all sorts of movies get action figures (or, at least, used to; I suppose that trend has died down somewhat in the last few years), but only the really cool ones get made into Lego.

Of course, this whole conversation started with Harrison Ford.
Star Wars was the first Lego franchise, so you can almost say this all started with him.
That's one of the very first Han Solo minifigures, back when they were still yellow like regular Lego minifigures. Now, they look like this:
And, of course, the second incarnation of Harrison Ford as a minifigure:
There ensued a long "discussion" of what other actors had two different character minifigs. [Don't ask why discussion is in quotes; just accept it.] Here's what we came up with:

Chris Evans:
Johnny Depp:
Samuel Jackson:
Ian McKellen:

Christopher Lee:

Orlando Bloom:
Those are the ones we came up with. Ones that have actual, physical minifigures. There are a few more that have two different characters but one of the minifigures is only in one of the Lego video games.

If you can think of more, let me know!