MovableWordTypePress

I’ve been considering switching weblogging software recently. MovableType 2.6 has been good enough for a while, but it’s stagnated, even with the release of version 3.0. (There’s also the whole freedom issue, although that’s been less of a factor in my thinking.)

I’m most interested in WordPress. However, it relies completely on PHP, which I have an extreme (and perhaps undeserved) dislike for. Call me crazy (you’re crazy!) but I prefer to not introduce a lot of CPU, RAM, network and database overhead just to serve what is, 99.9% of the time, static content; I’m also not a big fan of the single point of failure. Disk space is cheap: my web hosting provider has increased the allocation given to every user by over 150% since I signed up less than a year ago. And I’ve never had an HTML-based site go completely offline due to a typo in a template; sure, comment posting or entry searching may not work for a bit, but the content of the site still exists.

What I’d really like is a form of funky caching, where pages are generated only when they (or their associated resources) change. A request to view any page would retrieve the HTML source directly from disk, not go through the page generator or even a script that redirects to the page.

So, pending a change of heart, I’m going to stay with MovableType 2.6. To slightly paraphrase Weird Al Yankovic,

You’re sort of everything I ever wanted
You’re not perfect, but I love you anyhow
You’re the software that I always dreamed of
Well, not really, but you’re good enough for now.

Published by