Showing posts with label J J Abrams. Show all posts
Showing posts with label J J Abrams. Show all posts

Wednesday, December 25, 2019

The Rise of Skywalker (a movie review post)

Well, here we are, 42 years later. I have to say I'm not really sure how I feel.
If you're a reader, you'll know that there are some books that leave you with a very bittersweet feeling at the end. There's a sadness that the book is over but, also, a joy in the completed journey. For me, the books that most do that for me are The Hobbit and Lord of the Rings. And I could have said that about Star Wars back when Return of the Jedi was the final movie. That feeling of bittersweetness is not a not knowing how to feel; that is the feeling.

I'm not left with that feeling now that I've seen Rise. There's no sadness that it's over or any joy in a journey completed. There's just a... sort of emptiness. A sadness, maybe, that I don't have any of those feelings.

And, you know, a large part of that lack of pleasurable pain has been caused by the overly toxic fan base, mostly people of my generation and mostly white dudes. It leaves a distaste in my mouth for nearly everything to do with the movies since they drove George out with their faux lightsabers and pitchforks.

But it's not just them. It's also Kathleen Kennedy's egregious mishandling of the Star Wars franchise and her lack of any kind of vision or leadership. She's treated the movies like middle school end of term projects with no real guidelines. You know, just do whatever you want.

And there was Abram's misguided attempt to make a movie that the fans would love when he started all of this with Force Awakens. Never try to pander to the fans. Tell the story that needs to be told, not rehash one that's already out there. Abram's also lacked vision, but, then, it wasn't really his job to provide that.

Mostly, though, it's the mess that Rian Johnson caused that is at issue, which I'm not going to go into again, and which could have been prevented if Kennedy had just had control of the ship rather than letting the monkeys play with the controls. Yeah, I really do lay all of this at her feet. She was supposed to be in charge!

All of that said, The Rise of Skywalker is probably as good a movie as it could be. At least, it's as good as Abrams was able to make it. I don't have any issues with the movie in and of itself. Well, that's not true. There are a few things I don't like. Or two things...

The movie feels too fast. Too rushed. And it's nearly three hours long, so I have a hard time with why it feels so rushed and undeveloped. It goes at the speed and heedlessness of a line of toppling dominoes. Things just keep happening, and no one is making any decisions.

It also has a very questy feel to it. So did the last one. I don't enjoy that feeling of quest, quest, subquest, quest, subquest. Find this, find that, get the thing that will make this work. Neither the original trilogy nor the prequels ever felt questy. It's not a thing you want to actually notice happening in the story, just like you don't want to notice the salt in your food. Just enough to bring out the flavor, not to taste on its own.

But the movie is fine. I mean, it's good. As I said, Abrams made what was probably the best movie he could make. It has a satisfying conclusion given what he had to work with.

And, no, I don't have an issue with that thing people are complaining about. Anyone who has known Star Wars should have known that was always in the cards. Always the plan. Maybe if Lucas had been able to do what he wanted to do with Darth Maul people would have had a better idea of what's going on in the movie, but, alas, someone had a big mouth and Lucas dropped that part of the story.
No, I'm not going to speak more clearly about any of this. If you don't know what I'm talking about, it would be too spoilery. And, if you do, then you don't need me to be more explicit.

So... The Rise of Skywalker:
Not the best Star Wars movie but certainly not the worst.
Still a Star Wars movie.
Has some really cool stuff in it.
Has some stuff which is cool in the moment but I probably disapprove of because it feels like it was done for the "cool factor" and really has no basis in the mythos. Oh, well, it's canon now.

Maybe I'm not through talking about my reaction to all of this, but I figured I should get my initial review up.
Merry Christmas!

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.

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 15, 2016

Star Wars: A Discussion (Episode V)

Okay, so, now we get to it. How do I really feel about The Force Awakens?
The answer is probably way more complicated than it ought to be, but it is what it is.
So let's start with the good...
Oh! There will be spoilers. Probably a lot of them.
Just sayin'.
[As it turns out, all but one spoiler has been pushed to the next post.]

It's a good movie. A very good movie. I say that not as an evaluation of actually quality but in its ability to make me want to watch it again. [I've seen it three times and want to see it again.] And, hey, it's Star Wars. It's full of action, non-stop action, in fact. The special effects are amazing, as you would expect.

Probably, the best thing about the movie is Adam Driver. It was a bit of an eyebrow-raiser for me when he got cast, though less of one when I found out it was as the villain. He has an interesting intensity about him, and it worked really well as Kylo Ren. He's able to do a lot with his voice and gave a much more nuanced performance than anyone in a Star Wars movie other than, perhaps, Ewan McGregor. Plus, his height made his stalking-walk very effective.

Finn and Rey are great additions.

I think it must be difficult to convey emotion while wearing stormtrooper armor, but John Boyega manages it. He is equal parts enthusiasm and naivete... well, when he's not being freaked out by what's going on around him, that is. I liked his performance, and I like the character.

Rey is great. She is now both my daughter's and my wife's favorite character in Star Wars (okay, well, my daughter may still like both R2 and BB-8 better) AND she is my oldest son's favorite character. Yes, even more than Luke Skywalker (though my son has been a devoted follower of the Empire for years, now, anyway). Daisy Ridley is good in the role.

The Force Awakens is actually as close you can probably get to the "perfect" fan movie for Star Wars. Except not for actual fans in the actual meaning of the word. Most people who call themselves a "fan" of something don't actually mean that; what they mean is that they like the thing. Actual fans invest themselves into the thing they're a fan of, hence the origin of the word from "fanatic." So, sense everyone gets to be a fan these days just for liking a thing, this movie is perfect. It's perfect for all of those people who saw the movies in the theater almost 40 years ago and thought it was great but, then, didn't think about Star Wars anymore until the prequels came out, which they hated, because what they wanted was another experience like A New Hope. The Phantom Menace was not that experience, but The Force Awakens is.

The Force Awakens achieves this by being almost the exact same movie. Except faster and more intense. This is a point of conflict for me. On the one hand, it is a fun movie but, then, I have to ask, "What's the point?" Of course, I know the point: Disney wanted to make a buttload of money, and they have succeeded admirably. But, seriously, from a story standpoint, why tell the same story again? From that perspective, I sort of feel gypped, because I already watched the one where they have to take down the shields so that they can destroy the giant planet-killing machine.

Which brings me, obliquely, to the major issue I have with Force: It feels like a movie about Star Wars but not quite like it is actually Star Wars. Honestly, effectively, that's what it is. The Force Awakens is a piece of officially sanctioned fan fiction. The fact that movie moves so quickly contributes to this feeling. So, while the non-stop action is attractive to the larger audience, the non-stop action also rushes past any feeling of being Star Wars. It does not "feel the Force." Ever. It's the lack of originality that really does it. The movie feels most like the kind of story a kid would make up to use his action figures with and destroy an EVEN BIGGER AND MORE POWERFUL Death Star. (Okay, there was your spoiler.)

Don't get me wrong; this doesn't make it a bad movie. It's an Abrams movie, and Abrams knows how to do big action and all of that. And fast. Very fast. So it's good. And fun. A good and fun bit of fan fiction that Disney has made into actual Star Wars canon. Maybe that's not a bad thing. I don't really know. All I know is that I wish Disney had actually held true to Lucas' story like they said they were going to do when all of this began. But, well, you can't stop them from following the scent of money, I suppose. Clearly, they have taken the "quicker, easier, more seductive" path.

Next post we'll talk about BB-8 and why he exists.

Monday, May 20, 2013

Into Whatness?

As I mentioned in my last post, I had a very busy weekend. On the tail end of everything that had been going on, Sunday night we went to see Star Trek Into Darkness. That was a drama in-and-of-itself. Initially, we'd planned to go see it on Friday night, but something came up on Friday night that I "needed" to do (there will be a post on that later), so we were going to do it Saturday. Of course, that was the plan before we pushed my daughter's sleepover party to this past weekend rather than the prior weekend, so Saturday got knocked off. That left Sunday, and my wife didn't want to do Sunday after the weekend we were having. She just didn't want to add that to the end of everything.

The suggestion, then, was that I take my oldest son to go see it and that would be that. My younger son has an ingrained opposition to Trek because of his love of Star Wars, so he had stated that he didn't want to go. My daughter wanted to go only because it was "going;" she had no real desire to see the movie. "Going" is always better than "staying" in her book. So the idea was that I would take the oldest to the afternoon matinee.

BUT there were complications. To start, he had gone off to spend the night with someone to avoid my daughter's sleepover, and he neglected to arrange for a ride home. There are two things to that: 1. We told him due to all of the stuff on during the weekend, we would not be available to transport him, so he had to arrange his own transportation. 2. My wife let him know very explicitly that she didn't want him gone all day because of his lack of planning. She wanted him home at a reasonably early hour on Sunday. Well, he failed to take care of that stuff. He called around 2:00 p.m. to let us know that he still had no ride home, a call I had been anticipating. At that point, I told him that we (he and I) were going to Star Trek... unless he didn't make it home, in which case, he would miss out. I figured that would put a fire under his butt. [It did. he dragged himself in the door somewhere around 3:30 (although, technically, he's missed the showtime I'd planned on).] The other complication was that I was just dead tired after all of the girls left and had needed a nap (which I barely got), so I hadn't been ready, yet, for the 3ish showtime, anyway.

Here's where it gets interesting:
So my oldest son walked in the door just as I was getting ready to leave to pick up my younger son from the work party he was at for the musical he's in at school (see why we weren't available to drive the oldest anywhere? Besides, if he wanted to, he could take some steps in getting his driver's license, but he's balking at that). My wife said to me as I was walking out that door, "You should see if he wants to go with y'all."
My response: "But he said he does not want to go."
"Just ask him anyway."
So I did. His response (once I picked him up (covered in paint (including a hand print on the leg of his pants from a girl (which would embarrass him to no end if he knew I was printing this))): "Sure, I have nothing better to do."

Okay, so, now, it was just us guys going to the movie. When it was just the older boy and me, my daughter had decided to stay home because she was have a water balloon fight in the park (this after all the water activities at the end-of-season league party); however, when she found out, upon coming in to refill the water pump, that both boys were going, she immediately changed her mind about the movie. Now, this was a problem. Not that she wanted to go but because now everyone was going but my wife who is the only one in our household that really identifies as a Trek fan. So I had to talk her into it, which wasn't as hard as all that after all; I just said, "Look, everyone else is going, but you're the one that really wants to see this, so you should just come, too." So she did. And she was glad of it.

As for the movie... well, let's start at the title.

What's the deal with meaningless titles? They annoy me. The title has no more to do with the movie than it could have to many movies. Like The Empire Strikes Back could have been called Into Darkness, and it would have held more meaning to the actual movie than this one. I get that it sounds cool, but, seriously, the title (of anything) ought to relate to the thing that's being titled in more than some vague way.

Past that, though, the movie was pretty awesome. Abrams  knows how to bring the action and keep you tense and on the edge of your seat. And, hey, there was no red matter, this time, so double plus good. Without giving anything away, I loved best the role reversal of Spock and Kirk. That was pretty awesome.

I have only two negatives (other than the title) at this point:
1. I do not want to see "old Spock" pop up in every movie as their tiny "god in a box." I get that the fans love seeing Nimoy (I do; I get it), but, from a story perspective, it's gonna get old if they always contact him when they're in trouble.
2. As much as I love Simon Pegg and love Simon Pegg as Scotty, he is the one character that doesn't quite feel right. he has moments where he feels like Scotty but, most of the time, the character seems off target. I don't blame this on Pegg, as he has no control over the writers having him do things that are not "Scottyish."

Speaking of the characters, I still love Karl Urban the most. Man, he could be DeForest Kelley. I swear, I can't tell the difference; he's just like watching the original Bones at work. And they gave him the line! Well, not the line but a the line: "I'm a doctor not a..." It was awesome.

Zachary Quinto comes in a close second to Urban on pulling off the channeling of the original character. Of course, he has had the privilege of actually working with Nimoy, so he wouldn't have an excuse to not be able to pull it off.

And, well, then there's Benedict Cumberbatch who was a perfect match to the rest of the cast. Mostly, it's the voice. But he seems to be able to play any kind of role he wants to play (see War Horse and Tinker Tailor Soldier Spy to understand what I mean by that).

And that's really about all I can say about the movie without giving stuff away, and I don't want to do that. As someone who is not really a Star Trek fan, I loved the movie. I do know that there are Trek fans out there that don't like what Abrams is doing, but, really, I'm not quite sure I get that, because he's really captured the heart of the original series with how closely they've managed to get the characters to their originals. It's actually enough that it makes me want to go back and watch those old episodes, and how much more successful can you be than that?

Tribble!

Wednesday, July 13, 2011

Super 8 or What's Behind My Back?

My wife screamed. I mean, she really screamed. I don't remember one time in over a dozen years when she's actually screamed during a movie. Generally speaking, she just likes to cut the circulation off in whichever of my limbs is closest to her during any suspenseful or scary parts. This time, she screamed. Loud. And ended up half in my lap. From a movie seat, so that was kind of impressive. She made me jump. I don't even remember what it was that caused the reaction, at this point, but she followed it up with 3 or 4 lesser screams throughout Super 8. And she squeezed my left arm off. Yes, it fell onto the floor, and I had to have it reattached. It was pretty gross, though. I mean, have you ever really looked at the... goo... on a movie theater floor? Let me just tell you right now, you don't want your arm laying around in it. Fortunately, because we went to a late showing several weeks post release, the theater wasn't very crowded, so there weren't many witnesses to take care of.

My first reaction to Super 8 was very positive. There's a good story there. An actual story about real people. So here's the warning: there will be spoilers. I want to actually talk about this movie and J. J. Abrams, and I don't want to try to do it while dodging around trying not to give anything away about the movie. Also, despite anything negative I may say about Super 8, let me just reiterate that I thoroughly enjoyed the experience of watching the film. It's easily one of the best stories in a movie I've seen this year. Not the best, but, probably, top 5.

I have very ambivalent feelings about Mr. Abrams. The more removed I am from the experience of sitting in the theater watching Super 8, the more my ambivalence towards Abrams extends over to the movie. See, Abrams has this problem: he likes to hide things behind his back to generate suspense. You remember doing that when you were a kid, right? Or, at least, having it done to you? When you're a kid, it's kind of fun. Trying to "convince" someone to show you what he's hiding. It's fun because you know he really does want to show you, so, once you've played the game long enough, he'll give you a peek. Teenagers change this to the "I've got a secret" game, but it's really the same thing.

There are two problems with this: 1. the thing is often anti-climactic 2. sometimes, we already know. Oh, actually, there's one other problem: it only works once. It's sort of a cheap trick in story telling because of that, when the suspense is being generated by just holding the secret behind your back. There's no reason to go back and experience it again, because you already know the secret. As opposed to a movie like The Sixth Sense (and I hate using this, because I don't have much respect for what Shyamalan has become. However, you can't deny that this one film was brilliant. Possibly the most brilliant of its genre) where the secret is really in front of you the whole time, you just don't know it because you haven't figured it out. You can watch it over and over again marveling at how you should have figured it out but just didn't.

That was the biggest issue I had with Super 8; I had flashbacks of Cloverfield, which is a movie I just didn't enjoy. I appreciate what Abrams was trying to do (it was a great idea), but the execution was... well, it was just weak. A movie without a plot with the author holding a monster behind his back that he flashes to us for a brief moment at the end and leaves us saying, "That's it? That was all? Two hours of this just for that?" He applies this same gimmick to Super 8, and, although he gives us a better view of the critter at the end of the movie, I still felt like I'd been kind of cheated. It was sort of like finding out that all he'd had behind his back the whole time was a frog. There was nothing startling about the alien. It was an alien. Big deal.

Abrams' genius lies in his ideas. He comes up with great concepts. Like Cloverfield. He doesn't have the best execution, though. He lets the idea run away with him instead of harnessing the idea. His Star Trek is a great example of this. He has this problem. He needs to re-boot the Star Trek franchise, but he doesn't want to just do the same thing over again. How could he shake things up? Destroy Vulcan. Go off on a whole new timeline. It was a great idea. But red matter? Seriously? That's the best he could come up with? And some guy sitting around in a space ship for decades just waiting? Yeah, it sounds malevolent and all, but, come on, decades? There's bound to be a point where the boredom sets in. Don't get me wrong, I loved his Star Trek. It's the best Star Trek out there, but, in the end, it's still just Star Trek with things like red matter that make my eyes roll.

He seems to have a follow through issue, too. Like a cat in a field of butterflies. Alias comes to mind. Another great idea. The first season was exceptional. Hooked me and my wife. We watched the whole series based on that first season. Well, the second season was pretty good, too. Somewhere in the third season, though, he got a new idea, Lost, and left Alias to pursue that instead. And Alias was full of the "what am I hiding behind my back?" plots. Every season. Oh, and everyone was an enemy spy that they would just suddenly reveal "by the way, I have a secret." I haven't watched Lost, but it has sounded like it was much the same. Great concept. It must have been considering how many people flocked to it, but he left it somewhere in there to go do Fringe, which I couldn't watch. I tried. But it was just too Abrams. Oh, and there was Star Trek in there, too, so, really, all you people out there upset about how Lost ended, you can't exactly blame Abrams, because he wasn't there. Other people were responsible for whatever bad stuff happened at the end of the series. Oh, wait. Abrams wasn't there. I guess you can blame him. But, you know, he probably didn't have any idea about how to end it, either, so it probably wouldn't have mattered if he had been there.

Super 8 evokes all of these Abrams issues for me. I can see them all in there. However, 8 has one saving grace: the story is just E.T. With a twist. It's the "what if the government had found the alien first?" version. But it's still a story about a boy that has lost a parent and is trying to cope with his loss. By meeting an alien. If only that was an option available to all boys that have lost a parent. Spielberg gave Abrams an assist on the story, so it's not surprising that that's what we're getting. Just with a lot of explosions and guns and eating humans (because that's really the freakiest moment in the movie, the alien casually munching on a human limb like it's eating a chicken leg). It's a strong story, and I could probably watch Super 8 again for the story, although the suspense surrounding the alien won't be there. My wife said she'd watch it again just to see the train crash again. It is spectacular.

Abrams does an excellent job with the setting. It evokes that sense of nostalgia in people my age and older. Those memories of what it was like to be a kid at that time. It's probably the strongest thing about the movie. It's perfect. Kids riding bikes. Models hanging from ceilings. Star Wars posters and comic books. All those things that are gone from mainstream life today. No cell phones. No computers. Cameras that actually use film that has to be developed. In that respect, I'm not sure how the movie plays to younger audiences. I haven't seen anything from that demographic about it, and we didn't take our kids to see it. I'm pretty sure all the explosions would make up for any lack of connection with the world of the movie, though.

There's even a message. Most movies, these days, don't have messages. Or themes. Nothing beyond the good vs evil. Which is fine, but it can go deeper than that. Abrams doesn't want anyone to miss his message, so he states it plainly for the audience. I'm impressed by this. Not in that he did it, but that people have still missed it. I know they have. I've read more reviews about this movie than any movie in a long time, and they all missed it. I would have thought that stating it the way Abrams did was a bit heavy handed, but, evidently, you have to put it right out there for people to even have a hope of them getting it, and, still, people will miss it. It's like communication with teenagers. Maybe that's where he messed up; he didn't state the message at least three times. Having spent many years of my life working with teenagers, I have experience with the "at least three times" thing. Most of them will get it after three times, although some still miss out and have to come back and ask "what did you say?"

At any rate, it's a good message. So good, in fact, that I'm going to quote it. The whole movie, the whole story, leads up to this one line. From the very first frame, he begins setting up the story, with a true  plot arc, to lead up to the one line of the movie that will sum everything up. However, I don't think it will spoil anything to know it ahead of time, because this particular aspect of the movie is about the journey. The journey of a father and a son trying to figure out how to connect with each other after the loss of the wife and mother. It's a touching journey and more grounded in reality than E. T., since the relationship in E.T. is the relationship with the alien. Who, then, leaves. Like Eliot's father left. This time, though, the boy is left with his father and the knowledge, "Bad things happen. Bad things happen, but you can still live."