Friday, December 29, 2017

Furies of Calderon (a book review post)

Any of you who have been around here for a while will know that I have a fairly high tolerance for reading -- let's say -- poor books. Sometimes really poor books. Sometimes really poor series of books. It's not that I enjoy it -- the pain of reading bad books -- I just don't like not finishing something that I start. Also, I tend to hold out the hope for some of them that they'll get better.

I suppose I was hoping this would be one of those, one that gets better, because I like Jim Butcher. The Dresden Files are great, at least the first dozen or so that I've read are, so I was expecting that The Codex Alera would be at least somewhere in the same range of quality.

But no...

Let's make a sports analogy, just for fun. If The Dresden Files were a major league baseball team, Furies of Calderon would be, like, a little league team. Except it would be grown men playing at a little league level and trying to go up against a major league team. It would be something worse than the Bad News Bears.

This book was bad.

Seriously, there was nothing in it that I enjoyed. Not even a single character. The plot was a pretty cliche. And don't get me started on the magic system.

Let me give some context:

I picked up the first two books when I got Furies. See, I really did expect to like it. Jim Butcher, right? By halfway through, I'd decided that there was no way I was going to read anymore of the books, and I hate not reading a book that I've already bought. It's a waste of money. But it was so bad I knew there was no way I could do it.

But I decided that I would, at least, go ahead and finish the one I was reading. I mean, Jim Butcher! It could get better! There was a chance, right? So I forged ahead... and got to within a hundred pages of the end of the book (and it's a long book, so 100 pages was, really, close to the end) and...
Well, I decided I'd had enough. Even with just only 100 pages to go, I couldn't bring myself to finish it. It wasn't worth wasting that much more time to do.

Here's my insight into this series:
Butcher has said that he always wanted to write epic fantasy. It was what he started out trying to do when he was a kid after reading Tolkien. I think this is the story he came up with when he was a teenager, maybe a middle schooler. Once he got famous enough off Dresden, he went back to this story he dreamed up when he was a kid and began writing it without any changes. Because it reads like it was written by a kid, and I've read enough stories by middle schoolers to recognize the style.

Oh, and possibly the worst thing in the book?
He uses the word "pace" all the time! No one walks; everyone paces. And it just doesn't mean the same thing. It broke me from the story every time he used it, sometimes three or four times on a page. It was awful. That wasn't the only word he used repetitively, but it was by far the worst.

All I can really say is don't read this book. I mean, I couldn't finish it. I couldn't finish it, and that's pretty significant.

Thursday, December 21, 2017

Rebels: "Stealth Strike" (Ep. 2.09)

"Just so you know, when I escape, I won't hurt any of you."


Well... It's actually been a couple of weeks since I watched this and it's not exactly fresh in my mind. The Last Jedi is fresh in my mind, but I'm not going to talk about that until I've seen it again.

Here's the thing, Kanan and Rex don't exactly like each other. More to the point, Kanan doesn't like Rex. You kind of can't blame him considering that Kanan was a Padawan when Order 66 was enacted, and he watched his Master killed by clones and had them try to kill him, too. There's a lack of trust going on despite the fact that Rex has stated he removed his control chip prior to Order 66.

Kanan and Rex do have a thing in common, though: their affection for Ezra. So, of course, when Ezra is captured, Kanan and Rex go together to rescue him. I mean, neither of them can let the other guy get the credit for it.

Yes, this is another rescue mission... but it's not exactly the kind of rescue mission you'd expect.
And it's a lot of fun to have Rex and Kanan together.



"This armor doesn't protect you from anything!"

"So much for stealth."
"It's not like they don't know we're here!"

Monday, December 18, 2017

Girls of the Golden West (an opera review post)

Here we are at the end of another opera season...
It's short this year because of next summer's presentation of The Ring Cycle. WooHoo! I can't wait.
...and I was really hoping it would end with a bang. Maybe something like a gunshot, considering this last opera being performed, but, if it was a gunshot, it was a popgun.

It's too bad, too, because I really wanted this to be great. For one thing, it's cool to get to go so world premiere operas; this makes our third. For another thing, after our gold country tour back in May, we felt a connection to the subject matter. However, one thing I've learned in my opera going is that I don't enjoy operas done in the modern style. It's the music: I just don't enjoy it.

So, yes, as with Elektra earlier this season, I couldn't get into Girls of the Golden West because the music proved too much of a barrier.

Not that it didn't have a few moments...

Have you ever tried to fly a kite on a day when there's not quite enough wind? There's almost enough, but it's just not quite enough to keep the kite up. So you run and you run and the kite starts going up and it keeps going up and you think you have it and you slow down to start feeding the kite some string... and it crashes to the ground.

That's how the music was for me in Girls. Someone would begin a beautiful aria, the music would start to take off, then it would be over and back to the driving rhythms.

It was disappointing, to say the least.

Having said all of that, the performances were great, and the opera has an interesting story. A compelling story about three women during the California gold rush. True stories, even. However, the writing was not quite compelling as the librettist frequently fell back on narration to tell you what happened rather than showing it. For instance:

There's a hanging. The lead up to the hanging happens onstage but, then, as the hanging is about to happen, one of the characters turns and, basically, tells the audience that the hanging happened and that's the end of it. There are several moments like that in the opera.

So... I'm glad I saw it. It was far from horrible, but I don't feel like I would want to watch it again. I am interested in seeing some of Adam's earlier operas, though, especially Nixon in China, which is quite famous.

Thursday, December 14, 2017

"You Didn't Do Anything Illegal"

That's what the cop led with when he pulled me over, "You didn't do anything illegal." That was probably in response to the look of bafflement on my face because I didn't know why I was being pulled over. What he said didn't clear that up because, then, my mind immediately went to, "Then why am I being pulled over?"

He answered my unspoken question, "You made someone else do something illegal."
Wait.
What the fuck?
Someone else broke the law and I'm the one being pulled over?
Not that I said any of that.
He was already going on, anyway, about how when I pulled over at the curb to drop my son off someone else had, instead of waiting, gone around me. They went around me in a no-passing area so crossed the double lines to do it.

Here's what was happening:
It was raining, so I was taking my son to school. Normally, he rides the city bus, but it's a pretty long way to the bus stop, and I didn't want him to have to walk in the rain, especially since it had turned out that he had outgrown his jacket, something I didn't know about until the rain started. [Yes, he has a new one now.]

I drop him off on this side street down by the junior college because it's a relatively close point to the building he's going to. Just to be clear:
There is no red painting on the curb.
There are no signs prohibiting stopping or dropping off/picking up.
There might be a "no parking" sign somewhere along the street, but, obviously, I didn't park. I might have been pulled over to the curb for something like 10 seconds, long enough for my son to hop out and shut the door.

So I pulled over and he got out, and some car went around me while I was doing it. However, that was the only other car on the road. It was a pretty light traffic morning. After my son got out and I began to pull away, the cop turned on his lights and bwooped his siren at me. I actually looked around for other cars that he could be flagging down, because what had I done?

Nothing illegal.

But, seeing as I was the only car, I pulled around the corner on the next side street and pulled over. the cop came up to my window and said, "Don't worry; you didn't do anything illegal." Then he went on at great length about how I had caused the other driver to make an illegal action, then went on to say how I should be grateful that he was only giving me a warning because he could give me a several hundred dollar ticket...
Wait!
What the fuck?
He was saving me from a ticket from a non-illegal action I took?
What could he have even given me a ticket for?
But I didn't say any of that.
I learned the hard way a long time ago about what it gets you to argue with a cop, especially when the cop is in the wrong. It doesn't matter if what a cop is doing is wrong or illegal: The cop has all the power. Kind of like when your dad punishes you for something your brother did because your dad likes your brother more (true story).

Here's the thing:
What the cop did was illegal. Pulling me over and taking my license and registration without just cause was an illegal act. You can't just stop someone for driving. Or for walking down the street. Or for whatever thing a cop may decide to do to you for whatever spurious reason he has. Unfortunately, I didn't have the presence of mind to get his badge number or anything. At that moment, I was just being glad he wasn't making up a false ticket and wanted to go.

This is the kind of thing that cops count on, though, and it's why they feel empowered to do... well, whatever they want to do. Look, I'm a white dude, and that cop felt completely within his rights to pull me over. Illegally. But, you know, maybe he thought I was going to be some mom dropping off her kid, which is probably much more frequent, and he thought he could get a little bit of intimidation going on. [I have heard -- literally listened to -- cops bragging about how they will pull women over for no reason just to see what will happen. And, yes, sometimes "things" happen, and they always happen because the woman feels intimidated.] And it's because cops feel empowered to do this kind of thing that black men wind up shot.

And Trump (#fakepresident), especially, has made cops feel emboldened to do as they please. [Yes, I listened to a cop talk about that, too, about how now that Trump was #fakepresident cops wouldn't have to worry so much about following the rules.

People who work for the public, whether they be cops or politicians, should not feel like they are the ones running the show. The GOP, especially, feels like they get to make the rules no matter how the public feels about what they're doing. They're playing "daddy" with the whole country, and it's time to put an end to it. This whole patriarchy thing really has to go.

Cops should be held accountable when they do illegal things.
Here's an idea, cops who shoot people should automatically lose their jobs. Maybe that would make some of them stop and think about whether there's a better solution than a gun.
Pedophiles shouldn't get to hold office. Or even run for election.

Monday, December 11, 2017

A Pocketful of Marbles

Remember marbles?
Not, do you know what is a marble, but do you remember marbles? Like from when you were a kid. Back when marbles were magical and sprang into existence through spontaneous generation and you only acquired new ones by finding them, trading for them, or having some benevolent Being gift some to you. When I was a kid, I did, in fact, have a special bag just for marbles. And acquiring new marbles was always cause for trading with my friends, some of whom also had marble bags though some just had jars.

Marbles were like trophies. When you're a kid, trophies also are like magical totems that come into existence for the sole purpose of being awarded to kids who have risen to the level of trophydom. After all, you can't buy trophies at the store, so they must be special. Unless, you know, there are special trophy stores... which there are... but you don't find that out until you're older. Like that whole Santa Claus thing.

But marbles! Marbles were better than gold. Of course, mostly, you could only trade them for other marbles... unless you had some super-cool marble, and, those, you could trade for almost anything. They were magic baubles. You could do a lot when you were a kid with a pocketful of marbles.
Not so much anymore, probably, but the philosophy is sound.

Because, in the end, marbles are worthless. Just bits of polished glass.

Dazzling, polished glass.

Right now, Republicans, the voters, are being dazzled by these bits of polished glass. GOP congressmen have filled their pockets with marbles and are trading them for your freedom. For our freedom, and you Republicans keep handing us over to them in exchange for shiny baubles that mean nothing.

They offer you a wall to keep out all of those dirty illegals,
and you give them your healthcare.

They offer you a tax break,
but they raise your taxes so that the rich can continue to get richer.

They offer you jobs
but give you a ruined environment.

They offer you guns
but give those to you as mass shootings, because the US is #1 in the world in mass shootings, the GOP is determined to keep us that way. After all, America has to be great at something, right?

They offer you marbles,
and you give them your freedom.

Unless your idea of freedom is the freedom to pay them more money. For everything.
Because that's what the GOP is all about, pricing the poor out of life and making slaves of them. And if you're not super rich, you're the poor. In the Republican world view, there is no middle class, and they're doing everything they can to siphon all of that money up to people who already have too much.

So if you're a Republican or if you vote Republican, especially if you voted for Trump (#fakepresident), I hope you have fun playing with your marbles. Maybe one day you'll open your eyes (or get your heads out of your asses) and see that you gave away everything of value for a few bits empty promises and polished gas.

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.

Wednesday, December 6, 2017

Rebels: "Wings of the Master" (Ep. 2.07)

"We lost the transport! We lost the transport!"

When I was a kid, I never had any of the starships from Star Wars. In fact, almost all I had was action figures. My mom didn't believe in supporting my Star Wars obsession, so I had to buy all my toys with my own money, and money isn't the easiest thing to come by when you're eight years old. So I would save up for one of the ships but, any time I had enough money for one, I would compare the one ship to all of the action figures I could get with the same money, and I would buy the action figures, the one exception being the Rebel transport from Empire, because it doubled as a storage case (and it was cheap).

All of that changed when the b-wing fighter was released. I thought b-wings were so cool after Jedi came out, and I loved the way the cockpit turned on its own as you rotated the ship. When that came out, I bought it. It was my first ship. Of course, I was 13 by then and had much better avenues for earning money.

You can imagine, then, my surprise and delight to discover that this episode was about the origin of the b-wing. It was very cool, and that's all I'm going to say about it. If you're curious, you should just watch it.
And, yes, I do still have my b-wing, and I still love it.



"I just hammered it together, young pilot; you made it soar."

Monday, December 4, 2017

Coco (a movie review post)

This turns out to be a difficult movie for me to review. Seriously, I've been contemplating the review for two days and still haven't figured out how exactly I want to approach this.

The easy thing to do is just to say that it's a great movie, because it is a great movie. In fact, since Toy Story 3 came out in 2010, Coco is one of only two great movies that Pixar has released, the other being Inside Out. The story is well-told and heartfelt. Heartfelt enough that it brought a tear to my eye. The aforementioned Toy Story 3 was the last movie to do that to me, as far as I remember.

As per Pixar, even in their less than good movies, the animation was fantastic. And fantastic in a way that we really haven't seen before: It was fabulously colorful. Like a sugar skull:
In fact, there's not anything I can point to that I would say would make the movie better. No improvements necessary.

And, yet...

And, yet, I am uncomfortable with the message, the message that family always comes first and is most important. More important than anything. I just... well... That's just not true.

I could get into examples of why that's not true, but it's probably not really necessary. Either you agree with the statement or you don't and nothing I say is going to matter one way or the other. Besides, any examples I could make could be entire posts, and I don't want to get into trying to summarize things in a way that is succinct. For instance, I could say:
When my grandmother died, my uncle, through unethical and possibly illegal methods, stole all of  the land my grandparent's had owned, leaving my mother and my aunt with virtually nothing.
But, then, you're going to want me to explain that, and I don't feel like getting into it. The short of it is that family shouldn't get any special passes just because they're family.

However, my disagreement with the message doesn't detract from the movie itself; the movie is great, and you should certainly go see it. At the theater even. It's really a movie which should be enjoyed on the big screen.

Friday, December 1, 2017

Manon (an opera review post)

Before I get into the review, let's have some background.

One of the ways my wife and I are able to afford the opera is that we sit in the cheap seats. The San Francisco Opera House has multiple balconies, and we sit allll the way at the top. Well, close enough. We also buy season passes, because that's much cheaper than buying show by show. Because up at the top is so far up at the top, for certain performances, they have screens that lower for the upper balcony and they broadcast close up shots of the performers for those of us too far away to see faces. It's way better than having to use "opera glasses" the way people used to have to do, though we still see those from time to time.

The screen provides some advantages to sitting up at the top. Occasionally, we get to upgrade our seats (for free) and move down to lower balcony. In front of the screens. So, yes, we're closer (much) to the stage and what's happening and don't really need the screens to see what's going on, but you don't get close ups of the performers faces with your eyes alone.

All of that to say that Ellie Dehn was excellent as Manon, and I know because we were up at the top and had the benefit of the screens and were able to see her facial expressions throughout the performance. And, sure, opera is about the singing -- she sang great -- but it has to also be about the acting or there's no life to the performance, and Dehn was amazing.

And I only bring up any of this because one of the things my wife and I do on our drive back home after the opera is look up reviews of that opera to see how the reviews compare to what we thought. Generally, reviews for any given opera are pretty similar, either everyone loved it or everyone hated it, but reviews for Manon were mixed, and they all seemed to center around Dehn. Either the reviewer thought she was great, or the reviewer thought she was flat and lifeless, which made me wonder if those particular reviews were just unable to see how expressive she was.

Maybe where you sit at an opera is more important than I previously thought?
Or maybe those reviewers went on an off night for her? It's hard to tell with live theater.
Whatever the case, we thought she was great.

Michael Fabiano, as Chevalier des Grieux, was also great, but I would say he was not quite as good as Dehn. [That's them above.]

I also really enjoyed David Pershall as Lescaut, Manon's cousin.

The set for this one was interesting. It used a combination of reflective surfaces (including Lescaut's shiny pants in act one) and shadows to lend atmosphere. Mostly, it was a minimalist set design, but the frequency of the large shadows of the actors on the wall behind them made it seem as if there was more on the stage than there really was.

But the real strength of this opera, for me, was the story. Because of the necessity of music, opera stories tend toward, let's say, straight forward and tend to have one dimensional characters. It's difficult to get more involved than that when your entire piece is around two hours long and it takes a six minute (or more) song to deliver a brief dialogue that would only take a few seconds to speak. The characters in Manon, though, were suitably complex even while dealing with what could be seen as a typical tragic love story. It was engrossing.

Of course, it was also long. Three hours. AND they cut out the ballet sequence; I have no idea how long it would have been with that. By the way, did you know that the origin of ballet is within opera? Well, it is.

I really liked Manon. It's not my favorite because the music wasn't quite compelling enough for that, but I would gladly watch it again, which is something I'm finding is a measure of how much I like things.

Tuesday, November 28, 2017

The Rest of the Year

the rest of the year...
It's going to be a BIT MEssY
somewhat
LIKE
this
post

Things are just...
>>>>>>>>>>busy<<<<<<<<<<
And I'm behind
on most things
BUT
specifically
the Blog
Because I keep it several weeks ahead most of the TIME
But tIime
caught up to me during all the stuff with the fires, and I've failed to get back ahead of things

SO
even though I don't have a specific
SCHEDULE
I do have a pattern
most of the time
but NOT through the end of the year

Also...
I'm working on beginning to sell off my comic book collection
right NOW
and that's taking a lot of tiMe
but
you know
if you want to buy some comic books
let me know

Monday, November 27, 2017

Rebels: "Brothers of the Broken Horn" (Ep. 2.06)

"We were enjoying a friendly game of sabaacc and, well, now, it's my ship."

With one episode, Rebels won my heart. Hondo Ohnaka was one of  my favorite side characters from Clone Wars, and it's a delight to have him show up here. Don't get me wrong, I'm not saying he was my favorite side character, but he was definitely top three. I hope this is just the first of many episodes for him to show up in. [Evidently, he still has the best writers. So many great lines!]

"Oh, the stories I could tell, so many of them true."

Ezra's having a hard time dealing with all of his responsibilities. On top of learning to use the Force and all of the other things he has to do to be a part of the team, Rex is now working on teaching him how to be a soldier. It's more than a bit overwhelming, which is what leads to running into Hondo. Ezra takes a... day off. So to speak.

Nothing philosophical. Not really. Just a fun episode. A romp, if you will. Definitely worth a watch.


"Well, that's another version of the story; I suppose."

Friday, November 24, 2017

Rebels: "Always Two There Are" (Ep. 2.05)

"You're like a broken protocol droid!"

Ooh... A haunted house story! Well, you know, derelict space craft/station story. I don't remember them doing one of these before. Of course, Rebels hasn't done one of these before, but I don't remember one from Clone Wars, either. I think the closest we've had to the feel of the beginning of this episode is Luke's visit to Dagobah. If someone had said, "I feel like...," I wouldn't have been surprised. It was an appropriately creeping beginning for a visit to an abandoned Republic space station.

It's good to have Rex in the series; he's a good foil to Kanan. I hope he stays around for a while.

Mostly, though, the episode is about introducing us to the new Inquisitor. Excuse me, two Inquisitors. The image of the new Inquisitor from last episode is appropriately imposing, but, as it turns out, Fifth Brother is just the muscle; Seventh Sister is the real creep fest, here, and it works to introduce these two in this episode.

BUT!

The show has yet to tackle any of the more complex philosophical issues that Clone Wars often took on. Rebels has become more enjoyable as they've deepened the personal relationships, etc, but it hasn't really taken on any questions beyond the difference between good and evil. It seems like there will be a lot of that as Ezra has more individual contact with characters like the Inquisitors. So, yes, I'm liking Rebels more than I did, but it still lacks the depth and complexity of The Clone Wars. But more on that next time...

Thursday, November 23, 2017

Rebels: "Relics of the Old Republic" (Ep. 2.04)


I'm a bit reminded of Howl's Moving Castle with this pair of episodes. The clones live in an old Republic tank, travelling slowly around the desolate planet they live on. There are things, like laundry, hanging off the outside of the tank. Being just a 20-minute show, they don't spend much time delving around the innards of their home, but there's just enough there to make me wish that they had. The fact that Gregor's kind of crazy just heightens that desire. I mean, who knows what kind of stuff he has stashed in odd corners inside that thing.

The only problem in all of this is that someone called the Empire. "Hello, we have a Jedi here..." As if Kanan didn't have enough against the clones already.

But it does give us a chance to see the clones scoff at and make fun of their first AT-ATs. That was a fun moment. Oh, come on, it's not anything people haven't said before, so it's good, I suppose, to see the creators making fun of their own thing. And what do AT-ATs care?

All of that, and a new Inquisitor is coming to town...

So far, season two is shaping up to be far superior to season one. The themes being introduced are much more mature and interesting than the rather juvenile season one. Which is not to say that I don't expect there to be more juvenile hi-jinks, because even Clone Wars had its more juvenile moments.

Wednesday, November 22, 2017

Rebels: "The Lost Commanders" (Ep. 2.03)

"There are questions, questions that need answering."


With those words Ahsoka is off to delve into the mystery of the Sith Lord she encountered last episode because, yeah, she doesn't know that Vader is Anakin. That conveniently takes her out of the picture for the moment, leaving our own little rebel band to go off on their own mission.

So... Ever wonder what happened to the clone troopers after the end of the Clone Wars? Did they end up on street corners holding bean cans while begging for handouts? I can't answer that question for you, not in a general sense, but we do get to find out what became of Captain Rex. Turns out he's on my least favorite planet in the galaxy. Oh! and hey! Gregor survived! Well, more or less. You remember him, right? The best part of my leasy favorite Clone Wars story arc ever.

The problem with all of this? Kanan was there when the clones turned on the Jedi. He watched his Master gunned down by clones she had served with for years, and he ran as they turned to do the same to him. They are both his betrayers and his reminder of his own guilt. Should be some interesting stuff if the clones stay around long enough, though there may be more betrayal in the offering.

Personally, I hope Rex stays around, and I hope we find out what happened to Cody, too, though I suspect nothing good if he's not with Rex.

Oh, and Zeb gets used as bait. Like worm bait.

Tuesday, November 21, 2017

Rebels: "The Siege of Lothal -- Part 2" (Ep. 2.02)

"We're going to have to smuggle ourselves off Lothal for a change."


Ezra meets Vader...

It doesn't go well.

It doesn't go well for anyone. 

Vader takes on a whole rebel fleet in his special TIE fighter, and we see why he's so feared as a pilot. Seriously, the stuff he does with his TIE is so far beyond anything we've seen from him, and we saw Anakin do a lot of impressive flying during Clone Wars.

The take away, though, and this is spoilery, is that Vader discovers his old apprentice is still alive.

Really, that's all I'm going to say about all of this (almost). It was a great start to season two and bringing Vader and Ahsoka together has me fully invested in where this is going to go.

All that and Lando makes an appearance.
And the Emperor.

Monday, November 20, 2017

Rebels: "The Siege of Lothal -- Part 1" (Ep. 2.01)

"I guess there is no going home."

It's Rebels week here at StrangePegs, which means two thing:
1. There will be an episode of Rebels reviewed each day!
2. No politics this week.
Except that it's Rebels, so there's a good chance there will be politics.

So... Kanan isn't happy. His and Hera's small rebel band of hooked up with the larger Rebel Alliance after the events that ended season one, and Kanan is feeling uncomfortable being a part of a larger organization. And taking orders. He really doesn't like having to take orders and be part of a chain of command.

Probably, he doesn't like having Ahsoka around, either, but that's just me saying that.  It doesn't come up in the episode.

Vader's not happy with the fact that our group has joined the larger organism, either, but that's because they're not on Lothal anymore, and Vader wants them back. Which means a plan...

Remember The Empire Strikes Back and that whole part where Han and Leia go to Bespin and... it's trap! This is kind of like that. Vader knows what's going to happen since, you know, he can see the future and all, which makes it a bit unfair. Evidently, Kanan never progressed in his training enough to be able to get glimpses of the future? I don't know. It's not a thing all Jedi can do, anyway, so maybe he just doesn't have that skill.

But, anyway, part of what happens is that Vader and Kallus order Minister Tua to make things... difficult... for the population of Lothal. This also echoes Empire; however, Tua doesn't have the stomach for it. Although she's a good little Nazi, um, Imperial agent, it seems that there are some things that go beyond even her ability to condone, very unlike our very own Republicans who seem just fine with rape as long as it's a good Republican boy doing the raping. [See, I told you. Politics.]

This episode is a good start to the season, and I didn't want to stop watching to write this.

Friday, November 17, 2017

Blade Runner 2049 (a movie review post)

Before I get started, this review is going to be full of spoilers. FULL! Seriously. I want to talk about this movie that, really, disappointed me, and I can't do that without talking spoilers. You've been warned.

But let's talk about Blade Runner first, which I reviewed a couple of months ago but didn't go into much detail when I did. I'm about to change that, so, if you haven't seen that movie, either, you might want to skip all of this.

We all know that Blade Runner was a visual masterpiece. It has been considered one of the most influential sci-fi movies of all time. Not as influential as Star Wars, of course, but, if you look at sci-fi movies after Blade Runner compared to before, you can see the difference.

However, it was the visuals that made the movie what it was. It's never just the visuals. The thing that was compelling about the movie, the thing that made it a great movie, was the question... I'll say it like this: What does it mean to be human? Which is actually the summation of many questions: Do I have a soul? Why do I have to die? What happens to me when I die? These are all questions Roy wants answers to.

Not that the movie definitively gives answers to any of these question, which is part of what makes the movie so compelling, but the scene at the end when Roy releases the dove is poignantly symbolic.

Blade Runner 2049 fails at all of the things that made the original so great.

Rather than the gritty realism that was so enticing in the first movie, 2049 is immaculately polished. Even the grit is polished. It's the difference between a box full of rocks and a box full of rocks that have been through a rock tumbler. Sure, they're prettier than a box of rocks, but all of the realism is gone.

Like, all of it. I mean, what the fuck is with the orange landscape with giant statues of naked women in high heels in porn poses? We're supposed to buy that as any sort of realism? And don't give me any "well, it's the future" crap, because that doesn't make the idea of that any more realistic, especially since that place would have to almost already exist so that it could be abandoned for 20-30 years by 2049. And a lot of the movie is like that: "cool" visuals for the sake of being cool but with no anchor to reality or purpose.

Not to mention how full of plot holes the movie is. Let's just talk about my "favorite" one:

Wallace has finally caught Deckard and wants some information from him that Deckard won't give up. Wallace informs Deckard that he will have to take him off-planet to torture him so that he'll talk. Wait, what? He needs to take him off-planet to torture him? What the fuck sense does that make? Wallace has already killed someone in his office, and he wasn't too worried about that. Sure, she was a replicant, but the movie tries to heavily imply that Deckard is, in fact, also a replicant -- though without coming out and saying it (it's like the writer, Hampton Fancher, can't decide if wants Deckard to be a replicant or not and, so, doesn't want to nail it down in case he changes his mind later) -- so what's the big deal about torturing Deckard in a place where, evidently, he routinely commits murder? Or whatever you call killing a replicant. Retiring?

Plus, no one knows Deckard is even still alive. He disappeared 30 or so years prior, so it's not like anyone is going to come looking for him.

The whole scenario is ridiculous and contrived so that Deckard can be put in a position for K to rescue him, something that wouldn't have been possible within the confines of Wallace's headquarters. I hate contrived bullshit that writers use to get themselves out of a hole they've put themselves in.

Other stupid things I'm not going to go into:
The threesome K has with his hologram and a prostitute. Not just that it happened but that it was inserted at a time when K should have been fleeing for his life, but, no, he has time to stop and have sex with a fucking hologram!

The junkyard people who decide to shoot down a police vehicle for no discernible reason and the divine intervention exercised by Wallace's lackey to get K out of it. Literally, K just shrugs off the fact that missiles rain down on his opponents and goes about his business, no questions asked.

The fact that this movie is no more than a bridge to set up for a replicant rebellion story line.

But the worst thing about the movie? It has no questions. There is nothing in this movie to give it any depth or, pardon the pun, soul. Its attempt to come to grips with the question, "Do replicants have souls?" is clumsy at best and results in a miracle-baby-orphan-savior cliche plot. Seriously, that's the best you could come up with, Fancher? It's not like that hasn't been done to death already. The child even has her own scar, of sorts, to mark as special, to mark her as "the one."

When the best sequel you can come up with to one of the greatest sci-fi movies of all time is a cliche, maybe you should leave the original movie to stand alone. It didn't need a sequel. But, then, maybe you needed the money.

Tuesday, November 14, 2017

Clone Wars -- "Unfinished Business" (Ep. ?.8)

-- Learn from the past but live for the future.


Well, here we are... at the end. End of the arc. End of the season. End of the show.
>sigh<
End of line.

Oh, wait, wrong movie. That's some other Disney franchise.

All of this started with Admiral Trench -- not the show, just this arc -- and we return to Trench's attack on the Republic's shipyards to finish up this bit of unfinished business, not that Trench isn't another piece of unfinished business.

One of the greatest moments in the series happens in this episode. It's a bit understated, but it's pretty awesome. Let's just say it this way: Mace Windu gives a speech.
To battle droids.
In front of Obi-Wan.

This is a good solid arc. The Bad Batch is an interesting idea, though a bit like the X-Clones (if I didn't say that before). Their introduction was obviously not intended as the series-ending arc it turned out to be. There's a lot left to be explored here, not least of which is whether there are more clones like the Bad Batch.

And, then, there's Echo, because it's clear from "Unfinished Business" that his story line was just beginning. It makes me hope he shows up in Rebels. Yes, I know I could check, but I'd rather be surprised.

Anyway... It was not a bad arc to end the series on, though I rather wish they'd been able to craft a story that would have felt like a story that was bringing the series to a close. In most respects, with Ahsoka leaving the Jedi Order, season five has much more the feel of the series coming to an end. It certainly feels as if they were working up to... something, and I really wish Disney had allowed the series to continue. There's no real reason why Clone Wars and Rebels couldn't have run concurrently.

Oh, well...

Monday, November 13, 2017

So That You Understand



This was a neighborhood. My friend had a house here. Whole parts of the city look like this.

Friday, November 10, 2017

At the Mountains of Madness (a book review post)

Yes, I'm still working my way through Lovecraft. No, I wouldn't recommend him to anyone else, not in general. There are a few, just a few, stories I'd suggest for anyone wanting to try him out. This is not one of them. Especially not at its length.

Funnily enough, when Lovecraft wrote this story, it was considered a novella but, by today's standards, it's novel length. It's more than 12,000 words longer than his next longest story and, I'm pretty sure, he could have cut all of them out. All of them. No, Lovecraft is not an author who gets better with length; he just gets more repetitive. I mean, it's possible that all 12,000 of those words are instances of "cyclopean" (one of Lovecraft's favorite words) and "decadent" (a new favorite for this story (seriously, if I ever again hear the term "decadent statue," it will be too soon (What even is a "decadent statue"? Lovecraft never says. He just tosses in the descriptor at some point to differentiate between the earlier statues))).

I did have hopes for this story when it started out. For one thing, it has a new setting. A new setting for Lovecraft, at any rate, though it's not really a common setting: the Antarctic. And it starts out well enough as Lovecraft goes into the scientific mission of the team and setting up the base camp and all of that but, of course, there's an unexpected discovery and everything goes horribly wrong.

Also, of course, the narrator isn't present for any of the action. That's how Lovecraft do. But what that does is forces the author to only tell you what happened, never to show it. It just gets boring after a while. Even when Lovecraft puts the narrator into the action, it ends up being passive. The narrator gets scared and runs away and never even sees what he's running from. His companion does, but that thing, whatever it was, is never revealed. You just have to trust that it's something really scary. So scary that the narrator's companion can't speak of it, another trick of Lovecraft's: the nameless terror.

It's so old, Man! Get a new trick.
Oh, no, wait, this is one of Lovecraft's last pieces, so it's not likely that he's going to find any new tricks.

The real problem with the story, though, is a thing a lot (maybe most?) of sci-fi authors have a problem with: I came up with a really cool idea and I want to tell you all about it even though it has nothing to do with the story and my character has no reason to know anything about it. Like a Joe Shmoe explaining how warp drive works or something. Of course, Lovecraft has to surpass everyone else and spend half of his book explaining something that his character shouldn't know, the back story of an alien race.

Sure, Lovecraft tries to make it plausible for his protagonist (I use that term loosely since the character does nothing more than walk around then run away) to know what he knows, but it's a ridiculous supposition, and you have to have severe cognitive dissonance to believe that his character could decipher and read the entire history of this race in the short amount of time allotted to him to do so by Lovecraft. It hurt my head, actually, trying to pretend that I could go along with the idea long enough to finish this "book."

Thursday, November 9, 2017