Friday, October 2, 2015

Don Quixote -- Part Two (a book review post)

A thing most people don't realize is that Don Quixote is actually two books written a decade apart. I know I didn't know before I picked up the book and did some background research on it. That's always a good thing, by the way. To understand the second book, in fact, you really need to understand the context of when and why Cervantes wrote it. Yes, there will be some spoilers (but not too many but one that reveals the end of the book).

Cervantes purposefully left the end of the first book open for a sequel, to put it in today's terms. Not the he necessarily intended to write one, but he wanted to be able to write more about Quixote if he wanted to. And he might have if the first book hadn't become the huge success that it became. "What?" you say, "That doesn't make sense." But it did.

See, Don Quixote became the most read book in the world at the time. Cervantes became a household name. He was world famous. It sounds great, right? It was... except for the part where he didn't receive a dime for his work. There was nothing to stop people from just printing his work on their own, no laws or anything protecting creators or copyrights or anything, and that's what people did. All over the world. So, although Quixote was a worldwide bestseller, Cervantes stayed penniless (which is how he died). I'm pretty sure that eroded his desire to actually go back and revisit Don Quixote and Sancho.

Until someone published a fake sequel. That pissed Cervantes off and prompted him to get to work on the second book. And here's why that's important: There are specific portions of the second book that are there to, basically, debunk the fake sequel. And, um, then Cervantes kills Quixote off at the end of the book so that no one else could write anymore fake Quixote stories. No better way to take care of that issue, I suppose.

As for the book itself, in many ways it's better than the first book, but it also suffers a little from addressing the audience about the fake sequel. It breaks the narrative. It's also amusing in sections, like when Quixote finds out that he supposedly goes somewhere in the fake book, so he completely avoids that place so as not to be confused with the fake Don Quixote.

The second book contains a bit more satire than the first and makes many of its points through making fun of Quixote and Panza. Sancho, though, frequently rises above the jokes being played on him, and the portion dealing with him as the governor of his "island" are some of the best in both books.

At any rate, you're not going to find the two books published separately, and it's unlikely that you'll want to stop reading at the end of book one if you get to the end of book one. So I'll say it again: Don Quixote is well worth reading, even 400 years after its original publication. Cervantes was a great writer. It's too bad he didn't write other novels. He did write some plays early in his life, and I might have to look into some of those. Don't let the length daunt you. Just dive in.

Tuesday, September 29, 2015

Clone Wars -- "Mystery of a Thousand Moons" (Ep. 1.18)

-- A single chance is a galaxy of hope.

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

Picking up on the heels of the previous episode, we see the release of the deadly virus Dr. Vindi was making. This episode becomes one of those "find a cure" episodes that so many TV shows employ at least once. And who's infected with the virus? Padme and Ahsoka, of course. Fortunately, a clue to a cure is near at hand, though you have to wonder how the virus was ever a scourge to the galaxy when they key to the cure turns up so easily.

Yes, yes, I know! Just because they Jedi have knowledge of the cure now doesn't mean anyone knew about it when the virus was a threat. Still...

The problem for me with this episode, at least on this re-watch of it, is that there really isn't any tension. You know that Anakin and Obi-Wan will find a cure for the disease. Of course, you know that. But the whole thing felt too easy for me. I don't remember how I felt about it the first time I watched it. There's also the issue that I'm not overly fond of the racing-the clock-to-find-a-cure-for-a-deadly-disease plot. I have a difficult time buying into those, because, on the whole, they never work the way diseases actually work.

There are some good points in this story, though.

We get Obi-Wan's first (I think (I'm pretty sure (at least, I don't remember any earlier ones))) look of suspicion at Anakin to do with his feelings about Padme. It's unfortunate that the series can't really deal with this dynamic in any depth because Obi-Wan still has to be surprised during Revenge of the Sith that Padme's pregnant by Anakin.

The side character Jaybo Hood is interesting.

We get to meet the Angels of Iego, which Anakin compares Padme to all the way back in The Phantom Menace.

The one other point of interest in the episode has to do with some of the clones who have also contracted the virus. Padme makes a comment about it being a shame that so many of them are sick and one of the other clones tells her that she shouldn't be so bothered about it because it's what the clones were made for. Again, the dynamics between the clones and their "masters" is one of the most interesting aspects of the show, and I'm glad they continue to explore the relationship.

The episode has its good moments, but it's not one of the more interesting ones. Even though it carries the "plague" idea over from the previous episode, it's still really a one-off, and I prefer when they do the story arcs that include character development.

Monday, September 28, 2015

Fallacies of the Church (part two) -- All You Need Is God

Maybe you've heard the joke:

There was a man caught in a flood because he didn't leave his house when he was told to evacuate. Rather than leave, he put his faith in God to save him. The waters rose higher and higher until he was eventually forced to climb out onto his roof. Once there, a man in a small boat came by and offered to carry him to safety. The man replied, "No, thank you. God will save me."

The waters continued to rise until he was sitting on the very top of his roof. A couple of men came by in a fishing boat and offered to carry him to safety. The man replied, "No, thank you! God will save me."

The waters continued to rise until he was forced to climb to the top of his chimney to sit. A helicopter came by and lowered itself and dropped a rope. The man replied, "No, thank you! God will save me!"

The waters continued to rise, and the man was swept away and drowned. Upon entering Heaven, he said to God, "God, I put my faith in you. Why didn't you save me?"

God answered, "I sent two boats and a helicopter. What more did you want?"

** ** **

Unfortunately, this joke is the perfect example of one of the greatest lies of "the church": God is all you need. And, hey, I get it; there are plenty of verses you can point to in the Bible that seem to say that, plenty of verses that talk about how God will supply your needs. Your physical needs. Except, the problem there is that those needs, with the exception of manna in the desert, don't magically appear. People provide them.

The thing is this: This is one of the most harmful lies of the church, this idea that God is all you need. It's always delivered in the context of someone needing help, which is what makes it so destructive. Are you going through an emotional upheaval, like a divorce? Don't worry; God is all you need. Are you going through a financial difficulty, like you just lost your job and can't make your house payments? Don't worry; God is all you need. Did you just suffer a physical trauma, like you found out you have cancer? Don't worry; God is all you need.

This line is always delivered in an effort to get the human(s) saying it out of any responsibility to be of assistance in the situation. "Oh, you don't need me. God is all you need." Then, if that situation doesn't turn around and end up in a positive manner? Well, there's definitely something wrong with the individual who had the problem. That person didn't "trust" God enough or, maybe, and even worse, God didn't like that person to begin with.

"All you need is God" is a cop out from "the church" and its members delivered on a weekly basis to people "the church" doesn't want to associate with.

What's worse (and it's worse because it's more insidious) is that it teaches people to not accept help, just like the guy in the joke. Accepting help from other people is some twisted kind of weakness and proof that you're not trusting God to... what? Who knows. Materialize a stack of money in your living room? "Fix" the spouse who is initiating the divorce? Heal you over night of the cancer? I'm just going to say this: If you're in need and someone offers help, fucking take the help! That's what people are for. Because God is actually not all you need.

What I know from experience from the use of this statement against people (and, yes, I do mean "against"), either from getting out of needing to offer help or people refusing to ask for it, is that when things don't work out, people feel abandoned by God and, therefore, abandon "the church," which, actually, might be for the better. However, destroying someone's faith is never for the better. And "the church" was put here to help people, not to tell them that they only need God and everything will be okay.

Look, I'm not going to get into a tit for tat verse argument about the validity of the statement; that would be pointless. Instead, I'm going to look at one particular event in the Bible, a foundational event, you could say. It doesn't even matter if you take this event as literal fact or some sort of metaphor, the truth that comes out of this is the same either way if you believe that God created man as a being meant to be in a relationship with Him. Let's look at Adam:

God is sitting around up in Heaven and, evidently, being a bit bored. All He has are Angels who don't have "free will," whatever that means considering a third of them rebelled against Him. Whatever the case, God decides to make a man, and He does. For a while, everything is great. God comes down to the special place He made for the man, Eden, and hangs out with him every night. Maybe they played poker? Or, maybe, they had a long running game of Monopoly going? You know with just two people that game can go on for ages. Or, maybe, they just skipped stones on the lake. I don't know.

What I do know is that, after a while, God realized that He, He being God!, was not enough for Adam. Adam was lonely and bored and couldn't handle all of the work of taking care of Eden all by himself. God was NOT all Adam needed. The end result of that is... well, people. Social people that need to depend on each other and cannot get by on God alone, as it were.

And I could go on and on. God appeared to Moses and told Moses that He would be with him, and Moses said, "Nope, I need a person." David had Jonathan. Paul had Barnabas. Jesus had his disciples! God, as man, needed people! Obviously, God is NOT all you need.

That the current iteration of Christianity is full of this message, "All you need is God," from the pulpit and pews to Christian music, is, well, it's horrible and destructive and a lie. In fact, it's undermining to the whole message of true Christianity. Of course, what we have in the United States today is more of a political movement, not a faith, and that message fits right in with that. A church that is preaching the "all you need is God" teaching is, more than likely, not a church you should be attending. Unless, of course, you're already bought into the same idea as a way of avoiding helping people.

Friday, September 25, 2015

Don Quixote -- Part One (a book review post)

I'm going to start by pointing out the obvious: Don Quixote is a long book. My copy, which is in small print, has more than 1000 pages. This is the main reason why it's taken me so long to read it. Not that I'm daunted by long books, but I would look at it and look at my other books and think that I could read so many other books in the same time it took to read Don Quixote, and that's what I would do. [I had the same problem when I was a kid collecting Star Wars toys. There would be some big item I wanted, like the Millennium Falcon or an AT-AT, that I would save up money to get but, when I got to the store, I would look at that one thing and realize how many action figures I could buy with the same money and end up buying the action figures.] I'm sorry I waited so long to read it.

Don Quixote is a great book full of laugh out loud moments. Now, understand, this is a book that was written 400 years ago. What this tells me, which is something I already knew but this serves as confirmation, is people don't really change all that much. I mean, you have everything here, from Quixote and Sancho puking in each other's faces to political satire to ripping on other authors' popularity despite poor quality writing to statements about the human condition. The book is compelling and a surprisingly fast read. At least it was for me.

Just the basics in case you don't know them: Quixote (not his real name) is a minor Spanish noble in love with chivalry and everything to do with it, so much so that he decides to become a knight. Let me be clear about this: He just decides to become a knight. This would be like just deciding to become Batman. You go out and buy a Batman costume and a bunch of gadgets and start stalking the streets in hopes of finding bad guys to beat up. Essentially, this is what Quixote does. He puts on some armor, gets his nag of a horse, and hits the trails looking for bad guys to defeat in honorable combat. Needless to say, hi-jinks ensue. And a little bit of crazy. Okay, a lot of crazy.

The crazy is best summed up in the whole tilting-at-windmills scene but only because, if there's anything people know about Don Quixote, it's the bit where he tries to joust with the windmills. He thinks they're giants. This is far from the best or funniest scene in the book; people know about it because it happens early. It's like how everyone knows about the Lilliputians from Gulliver's Travels even though the first section, the section in Lilliput, is the least of that book.

Quixote's friends don't like what he's doing and decide that he's gone crazy and needs to be cured. Their method of curing him is to burn all of his books. Books, see, are bad examples. At least, the books about chivalry that Quixote loves are bad examples, so they decide to remove the source of his illness by burning the books. Of course, before they burn them, they go through them and keep for themselves all of the valuable ones or the ones they just happen to like. It's really pretty horrible.

It's also Cervantes method of dismissing authors he thought were hacks (for lack of a better word) and uplifting authors he admired. Including, or maybe especially, contemporaries.

Look, there's a reason that this book is still considered one of the greatest novels ever written. I wish I hadn't waited so long to get around to it. It's well worth the time even if it does look long.

Tuesday, September 22, 2015

Clone Wars -- "Blue Shadow Virus" (Ep. 1.17)

-- Fear is a disease; hope is its only cure.

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

This is another one-shot episode. I want to like it, but I don't quite, I think. The villain, Dr. Nuvo Vindi, is too cliche, too Nazi mad scientist. He even defends the right of life for a virus, the most deadly virus the galaxy has ever known.

And, fine, I get that. It's an interesting philosophical question. What right do we as humans have to try to eradicate diseases, which are also living things? But I don't think anyone is going to say that any living thing doesn't have the right to try to defend itself against things that are trying to kill it and a disease, by default, is attacking the host. So, yeah, I find the argument that a killer virus has just as much right to life as humans to be a little... weak. To say the least.

The threat is one of biological warfare. Dr. Vindi, working for the Separatists, wants to release a virus that could, potentially, wipe out all life in the galaxy. Of course, it wouldn't affect droids, so the droid army would be able to advantage of the chaos of a plague and defeat the Republic while they tried to halt the spread of the virus. From that perspective, I can't say it's a bad plan. And it mirrors the efforts of certain groups in our world to weaponize diseases for use in war.

Beyond that layer, though, it's just another rescue mission. Padme and Jar Jar, because they go off on their own, get captured by Vindi. Since Anakin's along, the focus is on rescuing Padme even though he knows the stakes are much higher. So we do get to see that some more, that Anakin's attachment to Padme is something that interferes with who he is as a Jedi. It's good development. But I do think I'm ready for them to lay off of the rescue missions for a little while, especially ones that involve Padme getting caught because she goes off like Lois Lane in pursuit of a story knowing that Superman will rescue her.

Okay, well, it's a fine episode. Taken on its own, it's an especially fine episode. Jar Jar is fine. Everything is fine. For the season, though, I don't think this one is particularly strong in comparison to some of the other stories.

Monday, September 21, 2015

Fallacies of the Church -- An Introduction (part one)

As I've talked about before, I grew up in "the church;" specifically, I grew up Southern Baptist. Beyond that, I've worked in "the church," across several different denominations. The difference between me and most people who grow up in "the church" is that, from a young age, I began exploring Christianity on my own. What I mean by that is that I did not rely on Sunday School or the pastor or the youth pastor or whomever to teach me what's what about what's in the Bible and anything and everything related to that. I studied on my own.

My tendency to do my own studying (I was the only one in my youth group when I was a teenager who had read the Bible (even worse, when I got to college, I knew ministerial students who had never read the Bible (that, actually, was more than 90% of them))) led to many disagreements between me and authority figures at my church when I was a teenager. They would say something like... Let's use a great Southern Baptist example! "The Bible says it's a sin to dance." And I would reply, "No, it doesn't." Then, there would be some complicated rationalization about how all these other things the Bible said arrived at the conclusion that "dancing is a sin." It's very clear that God thought it was excellent when David, so overcome by joy and praise for God, danced naked through the streets. I'm sorry, but it's hard to get past that.

The thing is, whenever I would get into one of these disagreements with an authority figure in my church (and remember, I was only 16-17 years old), they would always have to concede to me that I was right. Because I was. They had just accepted things because of the tradition that the church had that the Bible said these things (like "God helps those who help themselves," and "Cleanliness is next to Godliness"). The only one of these I didn't get a full turnaround from the other person had to do with the rapture and when that will happen (in relation to the other events of Revelation, not what year it will happen). He couldn't bring himself to tell me I was right, so he came back with, "I'm not saying you're right, but I will say that I was wrong."

Now, you might be thinking right about now, "Why does any of this matter? I don't care about the rapture or what Baptists think about dancing," and I get that. Totally. I don't care about what the Baptists think about dancing, either, even if I can't do it (and you can ask my wife, even after lessons and more lessons, I just can't dance). However, some of these things "the church" teaches are damaging to people, including what it teaches, mostly, about the rapture. I don't mean damaging in a little way, either. I mean damaging in a big way in that it becomes damaging to society in general.

Now, I am not setting out to be offensive, but I am sure that some, if not all, of what I say will be found to be offensive by at least some of the people who visit my blog. I'd like to care more about that, but I kind of don't. If I did, I wouldn't do this series to begin with. People in "the church" tend to believe too much and trust too much what pastors say just because it is a pastor who is saying it, pastors who have never read the Bible all the way through or ever bother to learn the historical context of what they were reading. I have had people tell me, "You don't need no schooling to be a preacher, all you need to do is have a Bible." And that attitude explains the abject ignorance of at least 80% of "the church." [Yes, I pulled that figure out of my butt, but I expect it's more like 95%, so I was being extremely generous. Remember, I spent decades around people in "the church" and found very few of them to be any kind of enlightened. About anything.]

Anyway... back at the beginning of the year, I promised to be more offensive, and this is just another of the ways I intend to do it. I don't have an issue with tackling difficult topics.

All of that being said, I am a Christian, but I am only a Christian in that I believe in the Kerygma (as I talked about here). I am certainly not the current iteration of cultural "Christian" who is so far removed from anything that Christ taught that if Jesus walked into their church, they would turn Him out. Or barely tolerate his presence in hopes that He would leave on His own. I'll put it like this: I find "the church" to be offensive. I find a significant number of right-wing nutjobs supporting their actions by waving the Bible around (like Kim Davis) to be offensive. I find the people who hold rallies for those people and wave the Bible around as an excuse (I'm looking at you Mike Huckabee) to be offensive. Well, it's time for you to own up to what's not actually in the Bible and to start treating people the way Jesus said to: with love.

Friday, September 18, 2015

Softball Victims

Let me start out by saying that I don't carry cash. Almost ever. I only carry it when I know I'll need it. My kids got me out of the habit of ever having cash on me something like 10 years ago. If I carry it, they spend it.

I haven't talked about my daughter's softball stuff this year at all. I've meant to, but, really, I've had other things on my mind and just didn't get to it. The main thing you should know is that we let her do fall ball, this year, for the first time. Yes, it's difficult to keep up with the softball schedule during the school year. So difficult!

But, anyway, she had her first fall tournament this past weekend. Which they won, by the way. I'm just telling you now because this post isn't about that. Actually, this post isn't really about softball at all. So, see, when we got there, I had to pay to get in. I had to pay to get in!

There were some problems with this:
1. I have never had to pay to get into one of my daughter's softball tournaments before.
2. No one told me I was going to have to pay.
3. I don't carry cash.
Needless to say, I was a bit irate. Hmm... "a bit" might be an understatement.

As I was pulling out my cash... oh, wait! the cash. Well, see, after my daughter and I were already in the car and pulling out, I thought, "Wait, I better go in and grab some cash so that I can buy water if I need to." Because I didn't have any water to take with me. Yes, I didn't plan ahead very well for this particular tournament in those regards. So I hopped out of the car, much to the chagrin of my daughter who was worried about being late, and ran back in for some cash.

So I was pulling the cash out of my pocket as I was being upset about the whole thing, and I said to the girl who taking the money, "What if I didn't have any cash on me? No one told me I was going to have to pay to get in to my own daughter's softball tournament." The girl didn't answer, but a woman standing nearby did. She said something like, "Well, I guess that would just be too bad."

I was already irate, but that pissed me off. It pissed me off that some random bystander would make that comment to begin with, so I said, "Well, it's messed up. It's messed up to charge the parents, who have to drive their kids to the tournaments, to get in to see them play. No other tournaments charge." And that was the point that I found out that she wasn't a random bystander but someone who worked for the park the tournament was being held at. Needless to say, we got into it.

Let me digress for a moment. The night before, my wife and I had been looking at an article about the current victim-hood culture we have. It was an interesting article that I would link, but we were reading it on her computer, and I don't remember what site it was on. The thing that was most interesting was how "victims," in order to support their victim status, resort to proclaiming as publicly as possible about how they have been wronged. This draws sympathy and weird support form people they don't know and makes them feel validated in their victim-hood. Basically, rather than trying to work out an issue or taking some proactive approach, people tend to just, well, I'll call it "tattle."

I had gone on off to find my daughter. She didn't have to pay to get in (because that would have been even more messed up since they have to pay to play in the tournaments anyway), so I had sent her ahead to find her team while I was paying and getting my wristband on. Once I found her, I stopped to text my wife (who wasn't able to come to the tournament because, in her work, this is the busy time of the year, like tax time CPAs) that we were there. While I was doing that, my daughter's head coach came over and tapped me on the shoulder and said, "Look, I'm on your side, but..."

You can always tell by the "but." As it turns out, the woman I had words with was the director of the tournament, and she felt so victimized by me that she had to go tell the head coach of my daughter's team to have words with me about it. Because nothing says "I'm a victim" better than tattling. I felt like I was in kindergarten again.

Is this really what we've become in the United States? A nation of kindergartners who can't deal with their own problems? I mean, this was a grown-ass woman, older than me, and she felt the need to complain to my kid's coach about me saying it was messed up to charge the parents to get into the tournament. And let me tell you, it's one of the crappiest parks my daughter has played at. Maybe the worst. But the obviously expensive parks haven't charged anything. Which, at this point, is not the point.

So what is the point?

The point is that people need to grow up. When did we stop teaching kids not to tattle? I'm pretty sure that's not a thing anymore. I know it's not at my kid's school. We don't teach people to work things out anymore. We just teach them, culturally, to be a victims.
That's messed up!

[Edit: These tournaments are not related to any kind of school district league. These are organizations that hold the tournaments for the various softball leagues. None of this is related to schools. The teams have to pay to participate in the tournaments, and that's not cheap. Effectively, we've already paid for our daughter to be at any of these tournaments playing in the first place. This thing where I had to then pay to get in is kind of like when a store charges an entry fee so that you can go in and buy stuff.]