There are certain things you should not attempt to do either drunk or while recovering from a serious night of drinking. These include, but are not limited to:

• Drinking orange juice. It will go right through you, and that is the last thing you’ll want to see/smell/experience,
• Debug 2 apache servers simultaneously. This is not recommended behaviour at any time, but it gets more fun when you can’t focus on which one you’re fixing. This leads to more problems and more debugging. Ad infinitum,
• Install mod_rewrite. Tracking problems online and offline to find some common ground, to get mod_rewrite working is NOT fun. Bastarding thing,
• Watch Sister Act 2. Actually, you should never do this.

There’s far more that could be added, but for sake of pride, I’ll leave it at that.

Attention to my UK readers! As I mentioned a few days ago, Final Flight Of Osiris is the only Animatrix short film currently showing that is not available from the website. However, Channel 5 is showing it tonight at 11:35 PM straight after they show The Matrix.

Anyone who hasn’t yet seen it should watch it tonight, rather than go see Dreamcatcher.

The new version of Phoenix Firebird has finally been released, and it’s been a long time coming.

I haven’t used it yet, but there’s an extensive list of changes including a new default theme, automatic image re-sizing, smooth scrolling and bookmark context menus (a much needed addition). I just hope that it runs ok on my computer; everything since 0.5 has caused massive drains on the available resources.

There’s been a lot of talk about APIs recently. Most of it can be summed up reasonably by Evan’s post on the API situation. For anyone bringing a CMS into the world around now, it’s a bit of a nightmare situation.

Everyone (Dave and Evan – the brains behind the two big APIs – included) wants a singular but fully functioning API to hook into. To be able to write once and only once, and forget about it for the near future. Currently, it isn’t possible.

Rather than get into the politics and technical reasons behind the split; I thought I’d say that as the developer of a new CMS, I currently implement neither API. I will, some day, implement one but as of yet haven’t. Why?

First of all, I’m the only person to use a remotely new version of Finetto (the aforementioned CMS). I’ve given other sites stable working versions (Finetto was actually written for a site that I was working on, where the owners didn’t have the knowledge to update manually), and it will be used on other sites (once I get a rather unique feature finished). But for now, it’s really just me, and I’m happy using the web interface for it. I know it’s secure enough to let me log-on from other computers without compromising anything.

Secondly, the browser window is the lowest common denominator of any net capable application. I’ve checked this from a number of devices, and they all allow access through the web interface (hooray for somewhat functional XML parsers embedded in devices). This kind of interoperability puts API interoperability further down the list. More devices support browsers than custom interfaces.

Admittedly, another reason is that there are 2 problems with Finetto stopping me implementing an API. One is trivial, and I could write code for in 5 minutes. I don’t because there are things much higher on my priority list (non-crufty URLs and a comment system have been on the list for too long to ignore now). The other reason is slightly more complicated, but I have the necessary script to remedy it, I just need a lot more time than I have to do so.

Finally, because there’s not enough time in the day. I’m a student. I have exams getting imminently close, a girlfriend, friends to do stuff with, alcohol that needs drunk etc. You get the picture. There’s not enough time to do all that as there is, without having to weigh up two APIs to implement. If there was one, then maybe, but until summer it’s just not going to happen.

I don’t know what the point of this post was if there was any. Hell, I’ll probably do a Zeldman and implement an API by this time tomorrow. But perhaps I’m trying to say prioritise, make sure you do things because you should rather than because everyone else is doing it, and don’t do drugs, kids.

I’m feeling kinda Matrix-y today, so I’ll finally attempt to recreate the essay on the background of the film which was cruelly deleted. I doubt this will be as good as the original (which took about 45 minutes to write), but I want it out of the way. In fact, it’s about a million times shorter and is really just a bunch of links now. For shame.

First up is Reloaded Questions, an article which focusses on the inspiration of the film, and how the sharp philosophy interestingly contrasts the less cerebral kung-fu moments. Keeping a balance between the ideas and the action, the thinking man and the mainstream, is difficult enough but in a sequel of this magnitude it must be damn near impossible.

Next is Tantek’s look at Burning Chrome, William Gibson’s seminal book of cyberpunk short stories. It introduced the concept of an abstract virtual world known as, you guessed it, the matrix. Lots of terminology found in The Matrix originated here and in the remainder of Gibson’s work.

Interestingly, The Matrix starred Keanu Reeves, who also starred in the awful film of Johnny Mnemonic, the first story in Gibson’s Burning Chrome. Gibson defends it as not being the version they shot, and with a writer like that, I believe him.

And that’s it. I did write a lot more originally but fate told me it was not meant to be.