Harry Potter & the Deathly Hallows

WARNING: This post contains spoilers. If you haven't read the book yet, don't read this post. You have been warned.

So yesterday I finished re-reading Harry Potter & the Deathly Hallows (HP&DH). Damn, it's a good book. And although Rowling didn't tie up all the loose ends of the plot (I'm dying to know what happens to Umbridge, for example), she did fill us in on most of the important details. The rest she discussed in various interviews and web chats. If you want to know more, here are some of the articles that you should read: 

I could talk about the book some more but, now that she herself can discuss it, Rowling has done most of the talking anyway.

By the way, if you want an incredibly concise summary of the book, check out the spoiler t-shirt at the Harry Potter Plot Enlightenment Project :)

The Movie

What I can talk about, however, is what the movie version of this book will be like. If you have read HP&DH, and have also read my post on Harry Potter & the Order of the Phoenix (HP&OTP), you will have noticed that, of the three items missing from the movie that I was unhappy about, two of them play a rather important part in the last book. Namely the fact that Harry's tell-all article doesn't get published in the Quibbler (which feeds into the Xeno Lovegood story arc) and that, in Snape's memories, we don't see the bit where Lily defends Serverus (which is needed for the final Snape story arc; "The Price's Story" as it's called in the book). The second omission can be easily fixed since, for the final movie, they'll probably just append that bit to scene they did show in the HP&OTP movie.

The first omission, on the other hand, doesn't bode well. At least for Xeno Lovegood because I'm guessing they'll cut him out of the final movie entirely. Instead, Harry, Ron, and Hermione will figure out the Hallows-Peverell connection themselves and the whole scene will be summed up in a short dialogue between Hermione and Ron. Oh well.

They'll probably also cut out the wedding. The trio will make a run for it soon after the Minister has given them the stuff that Dumbledore left them in his will. That whole time-in-the-wilderness bit will also probably be replaced by a montage. And they might skip the whole Ron leaving and coming back story arc as well. Yes, indeed, there's lots to cut out. If I had the time, I would write down a summary of the book's plot and would chip away at it until I came up with the smallest plot threat that could tell the whole story. I would then cut it down further to see what could be done (i.e. which parts of the plot could be told) quicker. And cheaper, which fewer special effects. And then I would wait for the movie to see how my version compared with what they came up with. Yes, that would be an interesting exercise. If I had the time. Oh well.

Harry Potter & the Order of the Phoenix

So I watched 'Harry Potter and Order of the Phoenix' a few of days ago and, I must say, they did a really good job with it. The special effects -- particularly the duelling scenes in the Room of Requirements and the Department of Mysteries -- were fabulous. And the way the members of the Order and the Death Eaters zipped around the place was cool, too.

They also did a good job with the new characters introduced in this movie, particularly Imelda Staunton as Dolores Umbridge, Helena Bonham Carter as Bellatrix Lestrange, and Evanna Lynch as Luna Lovegood. All of them rocked. Luna, who plays a pivotal role in this book, is also one of my favourite characters in the whole series and Lynch played her perfectly. Good for Rowling to insist that a first-timer be cast in this role. (Hmmm...having lived in Australia for a year I almost wrote "Good on Rowling..."!)

On the other hand, it wasn't good of Rowling to let the screenwriters do whatever they wanted with the script. I don't like the fact that they left out some, in my opinion, important parts of the book from the movie, though I do certainly understand the need for brevity and simplicity -- especially in a children's movie. As it is, as far as I'm concerned, only the Walsh-Boyens-Jackson trio (of the 'Lord of the Rings' fame) have done justice to a fantasy fiction book-to-film translation. That said, I guess everyone has their pet peeves about what was left from of the book. My top three are:

1. Making Cho be the one who tells on the D.A.

And, while it was nice of them (the film's producers, directors, and screenwrites) to explicitly point out that Cho was given veritaserum by Umbridge so it's not like she had a choice, dammit that wasn't enough. Of course, it was much easier to do it this way. In the book, Harry gets about as pissed off at her as he is in the movie but that's there to show us that he's human (and not the perfect hero) just like the rest of us. When you're reading the book, you have to decide for yourself whether Harry is being unreasonable or not (by remaining pissed off at her). It's bits like that that make reading books so cool. Unfortunately, that level of subtelty is difficult to communicate in a movie (let alone communicate it well). Oh well. Hollywood 1, Cho 0.

2. Skipping the bit in which Harry's tell-all interview is published in the Quibbler.

They go to some length to show that no one believes Harry about Voldermort's return when they first get to school. The same happens in the book. But in that, it's the publishing of that interview that really starts to change everyone else's minds (big, teary hug from Mrs. Weasely aside). And Seamus' apology to Harry in the Great Hall comes after that. Instead, in the movie the changing of everyone else's mind is left up to Seamus' uncalled-for apology (since the article hadn't come out over the holidays and changed his mind) and Fudge's "He's back!" line at the end of the movie.

3. Skipping the bit in Snape's memory in which Harry's mother, Lily, rescues Snape from Harry's father, James', hovering charm.

This was a pretty crucial bit to cut out. And not just because it's another important shades-of-grey point in the book. But...I won't get into the other reason since a lot of people still haven't read the last book and it contains a spoiler. Coming to the shades-of-grey reason, though: in this memory, Harry's father comes across as an egotistical bully, Snape comes across as weak and helpless, and Lily comes across as a good, strong person. While Harry expected that of his mother, he was shocked to see his father (and, of course, Snape) acting that manner. Seeing this (and know it's true since it is a memory) shakes Harry's faith in a lot of things (including himself) and it takes him a while to get over all this. Again (and I'm getting sick of saying this over and over) since that's difficult to show in a movie...snip, snip, snip. *sigh*

Of these three omissions, though, the last one was the easiest to show with just a little bit of good screenwriting. And, having read the last book, it was the most important of the three as well. Who knows, though. Maybe they did shoot it but it wound up (metaphorically) on the cutting room floor because addings its counterpart scenes (Harry getting back his faith) would have made the movie too long. I guess we'll have to wait and see which scenes they add in the DVD.

Overall, though, Goldberg and Yates did a pretty good job with the movie and I know they -- hopefully someone else! -- will find smart ways of working around those omissions. As long as it's not Goldberg who does the screenplay -- I still haven't forgiven him for changing some crucial parts of Carl Sagan's 'Contact' -- we should be okay.

Next time...a spoiler-full review of the last Harry Potter book :)

Transformers: Prime and Fox

If you expected great drama and a serious plot line from 'Transformers (2007)' then you must have been sorely disappointed. Though, of course, you would have been an idiot to have gone into the movie with that in mind. Dude, Michael Bay of the highly enjoyable 'Pearl Harbour', 'Armageddon', 'The Rock', and 'Bad Boys' fame produced and directed it...what did you expect? It was -- and was supposed to be -- a fun, big budget, special effects extravaganza. And boy did it deliver on those fronts.

On the other hand, if you watched the movie specifically for the special effects, Optimus Prime's voice, and Megan Fox (or Shia LaBeouf, whatever), then you must have been pretty happy with it. As was Jeremy Slater who says in his 'Big! Fucking! Robots!' review:
Bay knows he's making a movie about action figures, and this is how action figures behave: you set them up, then you make them fight. We don't need to know why the Police Car Robot is evil; he just fucking is. That's enough for me, and I'm guessing it will be enough for most audiences.

That's an awesome review, by the way. Make sure you read it.

Other people have had fun with the movie, too. Phil Plait (bless him) from the Bad Astronomy blog took the the time to talk about the differences between Hollywood physics and real physics in his review of the movie ("Still, there were a few things I want to point out, because they're fun to think about."). Fortunately, he's enough of a fan of movies to conclude:
Surprisingly, that's about it. There were lots of other little things, but nothing I remember worth noting. Despite my science review, I really do recommend seeing this movie since it was a lot of fun and the special effects were truly awesome. It's a dumb movie, don't get me wrong, but there is room in the world for dumb movies sometimes.

Nadia, of course, loved it as well. While General Motor's marketing team must have had...well, let's just say a very happy week.
Imagine you're a huge automobile manufacturing company. (Imagine harder! You're a complex of buildings, factories, offices and... Oh, never mind. Bad metaphor.)

OK, specifically: Imagine you're a marketing exec at GM. Now imagine the ginormous year-end bonus you're going to get as a result of your collaboration with Paramount Pictures and toy-maker Hasbro on this summer's Transformers movie. Are you imagining swimming in cash? Good job.

[Source: 'GM, Transformers' product placement marketing match' from CNET's Crave blog]

My conclusion, on the other hand, can be summed up into one word: damn!

Near-Term Goals for This Here Blog

There is a lot that I want to blog about.

For example, I have recently watched the following movies:

Read the following interesting articles:

Read or re-read the following awesome books:

  • Frank Herbert's first Dune trilogy: "Dune", "Dune Messiah", and "Children of Dune"

  • JK Rowling's "Harry Potter & the Deathly Hallows"


Started listening to some really good netcasts on TWiT, including:

Discovered a couple of really good musicians:

Bought tickets to a couple of great concerts:

  • The Cure: 12 August, 2007 at the Rod Laver Arena

  • The Police: 26 January, 2008 at the Melbourne Cricket Ground


All of which are blog-worthy items. I have also recently started extensively using the moste excellent Google Reader which is something that I really want to blog about.

Finally, aside from everything already listed above, I am now formally declaring the following topics as future postings of mine for this here blog:

  • Facebook (and social networking in general)

  • Living in Australia

  • Why blog?

  • The problem with this blog


All of which I will about write soon. I hope.

Huh?

Why have I just written all of this? Well, all this is thanks to first item on Web Worker Daily's '10 Ways to be Productive with Your Blog' which is: "Post goals". Tthat's step one done with. Let's see how the others go :)

Oh, and I have also recently added a new page to my website called '(Much) More About Me', the title of which is rather self explanatory.

Dakota Fanning

Dakota Fanning is one of my favourite actors. Unlike most other child stars that are considered to be "good actors", she's the only one I know who can act like and adult when she needs to and, importantly, can also act like a kid when she needs to. Actors like Haley Joel Osment, who plays great adult roles, and Macaulay Culikin, who played decent kid roles, don't seem to be able to pull that off. The coolest part in all this, of course, is that she's only 13 years old. That means we should expect many more years of awesome acting from her. I, for one, am really looking forward to that.

Speaking of Dakota, I should talk about two more things. First that Denzel Washington continues to reinforce how great an actor he is with every role that he plays. I watched "Man on Fire" (2004) yesterday -- which is what prompted this particular posting -- and, despite the occasionally distracting ("edgy"?) directing by Tony Scott, quite enjoyed the movie. I particularly loved the innovative way in which they displayed subtitles throughout the film.

Second, I really liked Tom Cruise in "War of the Worlds". It was refreshing to see him play a panicked, not-so-smart, insignificant individual set against the backdrop of a much larger story. His character does grow to find redemption reasonably neatly at the end of the movie but, overally, the film was a little too one-dimensional for me. Yes, the special effects were awesome, but both story arcs were just too simple for a modern action/sci-fi thriller. Part of the reason for that was the fact that Wells' book itself was rather simple when compared to modern stories. Particularly modern science fiction stories. And Wells' book was one of the first book in that genre so naturally it wasn't as developed. They did update the story quite a bit (and quite nicely too) but, in my opinion at least, they stuck too close to the original storyline (which, had they been overly true to, would have resulted in a pretty crappy movie).

The converting of books into movies is a whole other topic that I don't want to get into right now. So I won't. The topic of simple story lines versus more complex ones, specifically in science fiction, is another topic that I'll get into later. I particularly want to compare the original Star Trek TV series with the newer ones. That should be a fun post to write. Anyway, I just wanted to say those two things. And I have. Thus endeth this post.

Watching Movies/TV, Listening to Music

Since I've started talking about the different layers that make up a scene in a movie or television show (i.e. by talking about scripts), let me go ahead and tell y'all how I watch movies in the first place. No, not the obvious open-eyes-stare-at-screen type how I watch movies, but more like what my movie-watching philosophy is. Of course, calling it a 'philosophy' gives it a little too much credit, but it sounds much cooler that way so I'm going to stick with it. (Also, when I say just 'movies', I do actually mean both movies and TV. It's just that it's much easier to stick to the one word, which is exactly what I'll do for the remainder of this post.)

Levels & Layers

Simply put, I watch movies at multiple levels and often (usually when I really like a movie) I watch it at least twice. When I say 'multiple levels' I mean that, because I know a little about how movies are made, I can see and appreciate the inputs of various contributors to the overall product. Let me give you an example from the first part of 'The Lord of the Rings: The Fellowship of the Ring'. And from that let's take the scene in which Gandalf and Frodo are riding on Gandalf's cart towards Bag End (i.e. Bilbo's house). The scene seems to be reasonably straightforward but there's a lot going on in there. For example:

  • The two actors are actually sitting five feet away from each other on a specially designed cart that, when viewed from the side, uses perspective to make Frodo look much smaller than Gandalf. As it moves along, the bench they're sitting on adjusts to ensure that there is no break in scene continuity.

  • The actual jump that Frodo makes into Gandal's arms was made by Elijah Wood's stunt double, Kiran Shah.

  • This is an important scene for Gandalf because, first, it's the first time we're seeing him on screen and he has to look believable and, second, because Ian McKellen worked really hard to get Gandal's voice, humour, mischievous nature, concern for Bilbo, and hidden power all just right for this scene.

  • A lot of work went into Gandalf's costume. It comes from drawing by John Howe (created for the cover illustration of the one the book editions) and both he and Alan Lee worked extensively with the producers to get the look and feel of Middle Earth just right.

  • The firework effects were added later and, in the scene, the children are reacting to just audio (if that). One of the children in the scene is actually Peter Jackson's.

  • The location of the scene is a park in New Zealand and all of the construction that was done to make it look like Hobbiton was completely undone after filming was completed.

  • Howard Shore's musical score is currently on the hobbit theme. This theme will be played (sometimes intermingled with other themes) every time there's talk about hobbits and the Shire. Bits of the fellowship theme are thrown in throughout the first half of the movie, but that theme won't be fully developed (i.e. played) till the famous crossing-the-mountain-ridge scene later on in the movie.


Now it's true that I know a lot of this stuff because (a) there is a lot of production information available about the LoTR movies in the DVD extras as well as online, (b) I'm a Peter Jackson fan and so I keep up with his work, and (c) I'm a huge LoTR fan. But that's part of the point: it is because I know about all this stuff and have read about it that I know a lot about what's going behind the scenes. And it's that which helps me watch the movie at multiple levels.

The fun thing is that, even if I don't know a lot about the movie I'm watching, I can still see how it was made. For example, regardless of which movie I'm watching, I will consciously notice continuity mistakes, the score and what it is trying to convey, the lighting, the cinematography, the camera angles, the number of cameras being used, the cuts between takes and scenes, the work being put in by the actors, the effects added on by the visual effects people, the audio being added on by the folio people, and so on. This is in much the same way that an editor would look at a book and see spelling and grammar mistakes, different font faces, writing and editing styles and choices, printing and layout choices, etc. (Aside: Being a web developer and designer, I do the same when viewing web pages.)

Layers in Music

Being a musician, meanwhile, helps me do the same thing when listening to music. For example, I can usually tell what bit was recorded live and what was added on later, what the song structure is all about, what the time signature is, when the key changes are, how the song is arranged spatially, what is being done with the backing vocals (when, who, how many, higher/lower, how spatially arranged, etc.), which instruments are playing in which audio frequency areas, what melodies and counter melodies are being used, what exactly each instrument is contributing to the song (which individual melody they're playing, etc.), and exactly which drum component the drummer is striking at any given time.

The Benefit

All of this, for both movies and songs, does a couple of things for me. First, it helps me get a lot more from the movie I'm watching or the song I'm listening to. I end up appreciating them not just for what they are, but also for how they came to be that way. Second, it makes me doubly dislike badly done songs/movies and makes me really like those that have been well done. That doesn't seem like a big thing but, believe me, it is. Take Shakira's song 'Hips Don't Lie' for example. The song is really good and it's great to dance to but, dammit, its production could have been better. Or take 'Rock the Party' by the Bombay Rockers in which the chorus sound like "frack the part, frack the party" instead of "rock the party, rock the party".

On the other hand, it is thanks to this that I can appreciate just how awesome the band Dire Straits was because its production is just incredible. (Unfortunately, Knopfler's obsession with getting everything exactly right led to a high turnover of band members). You also start to appreciate different individual music producers -- like Steve Lillywhite, Daniel Lanois, Brian Eno, Butch Vig, Mark Knopfler, Rick Rubin, Mike Campbell, and Peter Gabriel, to name some of my favourites -- and what they bring to bands and their sounds. To get an idea of the same thing happening in a different context, ask Nadia how she likes Dan Brown's 'The DaVinci Code' and why she has never been able to get past the first page because the writing is so darned crappy!

To make my life a little happier, by the way, I have had to develop both the ability to separate content from production and the ability to enjoy something even if it's not all that well done. So I can still enjoy listening to 'Hips Don't Lie' and I can still enjoy reading 'The DaVinci Code' (without cringing all that much) and I can still have a great time watching 'Terminator 3' even though there are minor acting issues and storyline inconsistencies.

Let's Watch That Again

Last thing: I mentioned at the start of this posting that I like to watch good movies more than once. One of the advantages of doing this is that I can peel off additional layers with each new viewing. And when a movie is really good, you get something new from it almost every single time you watch it. It is especially useful to watch good comedies more than once because you don't always get all the jokes the first time round (presumably because you're laughing so hard the first time round). Another advantage of multiple viewings is that, at the first viewing, you can leave your technical eye at the door and simply enjoy the story and get caught up in the action and excitement (especially if you're watching it in the cinema). Once you've done that, you can think "that was cool, how did they do that?" and then watch it again.

So that, ladies and gentlemen, is how I watch movies, TV shows, and plays; view websites; read books; and listen to music. Yes, life is rich and life is fun.

Reading Scripts

I not only love to watch movies and TV shows, I love to read their scripts as well. And since there are lots of them available on the Internet, I've read quite a few. I used to read just film scripts but, over the last year or so, I've also started reading TV scripts and transcripts. In fact, I'm going through a TV script-reading phase these days: I finished reading all seven seasons of 'Buffy the Vampire Slayer' a couple of months ago and now I'm on season three of 'Star Trek: The Next Generation' (ST: TNG, or just TNG).


I really do enjoy reading this stuff. It gives you a whole new perspective on things. For one, you get to tap right into the writers' minds since (ignoring transcripts for the time being) you're reading their actual words. Because of this, you get to skip the layer of interpretation, presentation, and representation added on by the director, cinematographer, and actors respectively. You also don't get the soundtrack so there's no emotional augmentation from the music either.


Less Than a Book, More Than a Play


Reading a script is not like reading a book, by the way. Books are books -- they describe thoughts, feeling, and emotions in the text as well as through dialogue. With scripts, actors get cues from the scriptwriter, direction from the director, and they also bring their own abilities (and interpretation) to the delivery. Still, some pacing and acting cues help describe how things should pan out, like in this snippet from a TNG episode:




Worf, Korris and Konmel walk along.


KONMEL



The opponent that killed Kunivas
should have been an enemy -- then
his death would have been even
more glorious.

WORF
(stunned by the revelation)

If the opponent was not an
enemy... who was it?

For a beat, neither Korris nor Konmel answer.



WORF
(continuing)

Tell me -- what really happened?


Korris gives Worf a long steady gaze.



That's not like a book and not like a stage play script either. In the latter, a lot more is left open to interpretation -- aside from the fact that that's written for a wholly different medium, of course. The closest that books come to being written like movie scripts are when Michael Crichton writes them. His books come across like screenplays and the action almost plays out as if you're watching it on a screen. Most cool, that.


Scripts are sometimes doubly enjoyable when you've actually seen the episode/movie that you're reading the script of because you can have it playing in the back of your head while you read. This lets you see exactly what the actors, cinematographers, visual effects people, soundtrack people, producer, and director added on to the scene. Since I am a movie/TV buff, this is something that I really enjoy doing/seeing. Much in the same way that I enjoy browsing the web at a deeper level than most users because, since I used make websites for a living, I know how people have made the sites I'm seeing. And while bad sites irritate me more than they would irritate others, visiting good sites actually makes me happy! Yes, I'm a little weird.


Fun With Changes


Anyway, coming back to scripts: they're even more enjoyable when the script actually differs from what was in the filmed version of the movie/episode. I can, at this point, go off on a tangent and start talking about script versions -- i.e. drafts, originals, revisions, shooting scripts, and transcripts -- and how scripts evolve but, don't worry, I'm not going to get into that right now. Maybe in a later post. But still, it's fun when you read unfinished scripts that say things like (from another ST:TNG episode):


 




73 INT. EXECUTIVE OFFICE - DAY (TO BE WRITTEN)




Beata, Trent, the away team. Basically, Beata tells
Riker he's pretty smart for a man. She's given his
words a great deal of thought, sees his point, has
(with the help of her parliament) reached a decision.



...(stuff deleted)...


Beata urges them to be on their way. She strikes the
meditation crystal, giving in to its soothing warmth
as Riker belays the previous order to "kidnap" the
Ramsey group, and our away team DEMATERIALIZES.


In the filmed version, they've obviously added dialogue to that scene but it is interesting to note that someone else (the actors or the director, maybe) actually came up with the words that were said at that time.


Different Endings


It's also fun when the ending is different from what was in the movie, something that often happens in earlier drafts. For example, in an early 'Alien: Resurrection' draft, Ripley actually fights (and eventually crushes to death) the new, hybrid alien on the surface of the planet Earth while in the movie he gets killed before they enter Earth's atmosphere (the cool blow-out from the cargo hold, for those that have seen the movie). Sometimes scriptwriters write multiple endings, letting the directors or producers choose the one they like the most. And sometimes it doesn't end there either: the director and producer go ahead and shoot those multiple endings, delaying the final decision till the editing stage. (Some DVD extras show you these alternative endings too).


Tightening The Narrative


What's more subtly cool, though, is when you read a script and realize that the director and/or editor has deviated from the script in order to tighten the narrative up a bit. For example, in another ST:TNG episode, the second-last scene in the filmed version is much more appropriate than the one in the script. In this episode (1-08, 'Justice'), we're on an alien planet in which Wesley has unknowingly committed a 'crime' (tripped and broken some glass in a greenhouse). Unfortunately, all crimes on this planet have the same, single punishment: death. At the same time, the planet is "overseen" by a highly advanced being that can do pretty much anything. The locals call it "God". Anyway, everything boils down to Picard having to choose between saving the life of a crewmember and sticking with a strict interpretation of the Prime Directive (according to which he can't interfere with local laws and so Wes must die).


In the script, the second-last scene ends with Picard saying the line "I realize now that there can be no justice...no justice so long as laws are absolute. Life itself is an exercise in exceptions." just before they beam back up, taking Wesley with them and leaving the locals pissed off. In the actual episode, however, Picard actually gives the order to beam up before he makes that speech...but nothing happens. "God" is blocking their transporter. It is then that Picard makes the speech, soon after which the transporter kicks in and they start to get beamed up. As they phase out, Riker says something along the lines of "I guess God agrees with you"�. The difference between the two may be subtle -- and I know I haven't explained it all that well (you have to have seen the episode itself to appreciate this properly) -- but, trust me, it makes a big difference to the episode. In the original script, they've technically gone against the Prime Directive and have angered the planet's inhabitants with their flagrant disregard for their local laws. In the filmed version, however, they have successfully appealed to God, something that the inhabitants have seen and have understood. In a show like Star Trek, this makes a huge difference.


Read Scripts and Transcripts!


Anyway, I hope this encourages at least some of you to go out and read some scripts. They really are a lot of fun. Assuming, of course, you like that kind of thing. I haven't talked much about transcripts in this post. Instead of saving them for a later post (because there's not much to say about them), let me just say that I like reading those too. While they don't necessarily give you a deeper understanding of the production process, they do give you a deeper understanding of the story, various story arcs, writing styles, acting styles, and all of that other stuff. Their quality does depend on the person writing the transcript, though. So you do get spelling errors and there are different styles of describing the action seen on the screen in words but, for the most part, the transcripts I've read have been pretty darned good. I guess that's partly because they're written by fans of the show who really do care about the quality of what gets written down.


Damn that was a long posting. I'll stop rather abruptly now.

Terminator 3

How cool is the Terminator trilogy? The first movie was groundbreaking enough and the second is one of my favourite movies of all time. And then, just when you thought it was all over...they came up with Terminator 3: Rise of the Machines. Now I know that a lot of people had a lot of problems with this instalment (most of which I don't agree with, by the way) and yes, it did have its problems. But if that's all you get fixated on, then you've missed half the movie!

Ignoring all that, how cool was the fundamental story behind T3? At one level it has that whole feeling of futility in the complete undoing of the first two movies. On the other hand, it has the whole inevitability-of-it-all thing going for it -- something that Nick Stahl manages to pull of really well in the last scene, I think. And the fact that they managed to do it (the whole reversal, back-to-where-you-started thing) in just one movie made the whole thing even cooler. I wonder what they're going to do with T4?

I also really like Nick Stahl, though he was better in Carnivale, and I am an Arnold Schwarzenegger fan. I don't like Claire Danes too much (as Nadia pointed out, she does too many roles in which she cries all the time) but I thought she did a pretty good constantly-freaked-out job in this role. I really missed Linda Hamilton in this one, though. She made the first two movies, didn't she?