Tuesday, August 25, 2009

LOST---The Good, the Bad, and the Ugly: Part VI

Okay, so here we are again, and our friend LOST is with us too, back with….

Fuck.

Why do I even bother writing these reviews? That is what LOST made me think about this week. And I mean it; I kept asking myself on the way home, amidst my thoughts and ideas for this review: why the fuck do I keep writing these?

Sorry, but this week I may come off a little more irritated than usual. I’m a little sick and I fucking hate feeling sick.

Anyway, let’s start over:

Okay, so here we are again, and our friend LOST is with us too, back with its usual consistencies. I actually missed the first five minutes of this week’s episode, because of callbacks for The Alchemist, in which the director decided to get done with a majority of the bit-part callbacks in the first hour-and-a-half but chose to shove the bit-part I was called back for until second-to-fucking-last. Luckily, Pete informed of what I missed, which kicks off the good section this week.

The good:

1. Locke did not stay dead! He’s vital to the show so I figured they wouldn’t kill him off; but I was still worried for a bit.

2. The “war” statement; the creators actually made a twist….genuinely surprising. However, that’s just one half of the “war” statement. Second half will be featured in the “bad” section.

3. Walt!

The bad:

1. This is more of an assumption than anything, but I get the feeling we’re going to see extraterrestrials make themselves known on this show in the future. The thing that triggered the thought this time was when Widmore said “my people protected that island for three decades”. Everytime Widmore or Ben say “my people”, it sounds more and more like they are talking about an alien species. Maybe that subject belongs more in “Purgatory” then “bad” but I’m getting sick of TV shows falling back on aliens.

2. What the fuck is up with J.J. Abrams? The man can’t seem to create a good television show unless it has a fucking war in it at some point. Really? There’s really going to be a fucking war in this one too? ::sigh:: okay, I need to tell you all a story about a little series known as Star Trek: Enterprise, which Abrams himself produced. In the first season, the audience is introduced to an Enterprise crew member named Daniels, who we find out is actually a time-traveler from the future. Daniels tells the Enterprise crew about something called the Temporal Cold War, which is a war that is being fought through space/time. The Temporal Cold War was featured in a few episodes over the first, second, and third season but then became the primary focus when the fourth(and final) season opened. In that premiere, the Enterprise crew returns to Earth, only to find that an enemy faction from the Temporal Cold War has gone back in time and helped the Nazi’s take over the world, thus threatening Star Trek’s entire future. And so on and so forth: the Enterprise crew rallies the defeat them and restore the timeline and Daniels ends up getting killed, an event that was celebrated by Star Trek fans everywhere. The point of all this is that it appears Abrams might be trying to do something similar here. I mean, we already have a time-traveling island, a good deal of aggressive conflict and some strange, STRANGE people. And the question now is why would he want to do this bloody…thing? I mean, sometimes war works in TV shows, but I just have a bad feeling about there being a war on LOST.

3. This episode reiterated just about everything. The reason why I asked myself “why do I write these reviews” is because if nobody saw at least a majority of the blatant, boring consistencies I’ve been pointing out for the last six weeks---in this episode---, than we are apparently not watching the same show.
Did we really need to see yet another fight between Jack and Locke? Yes, we know nobody is going to believe Locke; WE KNEW THAT BACK IN THE FOURTH SEASON! No, Locke is not just a lonely old man, there is a destiny for him that has to do with the island; we already fucking know that. Oh yes, and will he eventually succeed in getting everybody back to the island? Gee, I don’t know THAT one….
I get why the writers decided to write this episode, and yes the part with Ben at the end was interesting and very important, but these “fluff” episodes just get in the way.

The ugly:
1. Short ugly section this week. I find that as I reflect on these reviews; yes, I may be a little harsh, and am probably overthinking the show a little bit, but its because I like it so much that I criticize it so much. One of the many reasons why I decided to continue with these reviews after the first week is because of J.J. Abrams. Being a huge ST fan, I am very familiar with Abrams’s creativity, and I know he’s got more in him than this. And I know that these reviews will never reach his eyes and, even if they did, would not change a thing; but like I said, Abrams was just “one of many reasons”.

This week’s episode took a huge step backwards even though parts of it were really interesting. However, this was just a “fluff” episode, so I’m not too worried. But now its time to get prepared for the “war” that’s coming by dunking my head into a pile of kitty litter and screaming until the “war” is over, or until Abrams decides to stop continually beating his collection of dead horses.


Ciao.

P.S. Dharma Pus and Beans Industry.

No comments:

Post a Comment