I've decided to start a blog. I plan to pontificate on technical issues from time to time. OK, I can hear the response: "<yawn /> Everyone else has a blog. My cat would have a blog if she weren't so lazy."
Perhaps more interesting than the blog itself is the blogware I'm using, nanoblogger, or nb for short. It's small, lightweight, uses Unix command line tools like bash, cat, grep, sed, et cetera.
Also, nb produces static content. So I can edit locally, and only when I'm comfortable with the results do I push the changes out to the servers. Yeah, servers. I have a backup site as well as the main site.
I also like the elegance of crunching the data once and pushing it out to the server for the world to read. People will read this thing a lot more than I will modify it. OK, at least that's the idea of a blog. So dynamic creation of the content just doesn't make sense to me. It strikes me as lazy.
Dynamic blogging also strikes me as silly: most blogware programs are huge, therefore error prone. (Think office suites: bloatware par excellence and buggier than an ant hill, all of them.) nb is a set of bash scripts and most of its smarts are in the GNU utility programs that make up the standard Unix tool kit. Why reinvent the wheel?
Also, with dynamic blogging, the content is on the server. So you now have the problem of backing it up. With nb, backup is a non-issue: it gets backed up when your desktop or laptop gets backed up (you do back it up, don't you?). So that means one less step in creating a blog entry or article.