Death Proof

I’m having a field day with writing stuff today aren’t I? I’ve obviously got nothing to do, or something else to do that I don’t want to do.

I saw Quentin Tarantino’s latest movie, Death Proof, the other day. It was good. Typical Tarantino. Not as much blood as Kill Bill.

Ok, I turns out I’m not very good at writing movie reviews. I don’t want to spoil it for anyone. Plus, I don’t usually have reasons for liking movies.

But most people know it had a kiwi, Zoë Bell, in it. She is a stuntwoman. Used to be on Xena. But she was Uma Thurman’s stunt double in Kill Bill. She had the thickest kiwi accent though. She did say "sweet as" though. That’s good. I was waiting for a "chur bro" but it didn’t eventuate. Two out of the other three people in the cinema left about 4 minutes after her arrival. I’m guessing it was because of the accent.

That’s the end of that little story.

I like LINQ

LINQ stands for Language Integrated Query, a new feature of the .NET Framework 3.5. And it’s cool.

I have used LINQ to SQL on the My Flatmates Facebook application, and it made things a lot quicker. LINQ to SQL creates classes out of your database tables. Then you can use LINQ statements to create instances of the classes from your data. I think that Ruby is similar in that you work directly against the database. But I’ve never worked with Ruby before and haven’t read anything about it (I think Siggy from SilverStripe told me about it, discussing the performance of PHP vs the ease of Ruby, but I digress).

It requires a change of thinking though. I’ve grown up believing that stored procedures are the way to go, for performance and security. But LINQ to SQL is more flexible when you don’t use stored procs. I did a bit of a search for what this means for best practice and it seems that best practice is changing. (And in the MySQL world, stored procs are only a new thing and most people don’t think they’re needed.)

That is why I like LINQ.