If you like the game, or if you just like a good action flick, go see the movie. The movie was great. There was a line by Karl Urban at the beginning that I kinda cringed at, but overall, it was a fantastic flick. The action was great. The suspense was nice. And it was true to the feel of the game (Doom3) if not the actual story line. But, let's face it. Who wants to see a movie version of the game's story line. We already know that story. But the basic elements of the story line was there. The Rock and Karl Urban did a great job. Though, to be honest, The Rock didn't start dropping the expletives where I thought a real special ops type of guy would have. Though, to be fair, he did light it up in places. I can tell I'm a parent of a small child, though. As an aside, don't take your kids to see this movie. Yeah, you may think your 8 year old is mature enough. He's not. You'll ruin the movie for yourself (if you have any soul anyway) and you'll ruin for everyone around you. And you'll probably traumatize your kid, you sick bastard. Anyway, back to my kid. When the guns started firing, I started reaching for the remote control to turn it down lest I wake the kid. Then I remembered that I left my little back at home and settled back down for some too loud action. A thoroughly enjoyable flick. I'll probably see it again. Made me wanna break out my xbox game...

Well I finally sat down to get my ipod syncing with linux. Using ipodslave and amarok, I can sync pretty easily. I can copy to the ipod and remove files fairly easily. I can't, apparently, update the tag information and affect the ipod database. And, files i copy over with amarok/ipodslave have strange names like kpod10580.mp3. I'd like to change that as that's completely useless unless i'm looking at the ipod itself. I'm going to try gtkpod but at least I have some level of syncing now.

CSS is the new javascript. Back when I started working with web based applications, we avoided javascript for fear of compatibility hell. I still tend to shy away from it for those same reasons though the world is slightly better these days. However, no sensible developer tries to build a web app without at least some CSS to help style the web page. For one recent contract, my colleague and I did very little actually design on the layout and instead just marked everything up because we knew the client had a web design guy working on the presentation. What we handed over wasn't pretty by any stretch, but the design guy had developed the CSS to make it look absolutely gorgeous. I didn't even recognize it when he was done.

But CSS has the same compatibilty problems. Not all browsers support all of the spec(s) and even then not necessarily the same way. And that's troublesome when you rely too much on CSS. But then I found this handy little tool. Seasickness aside, you can see at a glance (or two or three) the level of support these CSS elements have in which browsers and begin to make some informed decisions. It's a little sad to have to resort to such tools, but at least it's there for us to use while the browser makers figure out what spec compliance means. Kudos to the developers that put this chart together.