Yes I know, it’s a blogger’s cardinal sin to post about why he hasn’t posted in a while. But live with it.
The irony is I’ve had so much to blog about. The reason I haven’t is because a while back I finally gave up on dasBlog and decided I’d switch to WordPress before I blogged again. dasBlog makes so many things difficult that are either easy or trival on WordPress, such as commenting and monitoring spam. After years of putting up with dasBlog I just finally got fed up and decided I’d wait to switch to WordPress. Sadly I’ve waited a long time, and it’s possible it may still be a while before I can move everything over.
Of course I could have tried upgrading dasBlog, but it’s so much harder to enhance dasBlog with it’s limited templating system that requires compiled .NET plugins vs. WordPress’ PHP scripting (reminiscient of classic ASP+VBScript, only better) that I was finally able to shed my programmer’s guilt for not learning how to write usable .NET plugins just as I was able to shed my guilt for never becoming proficient in x86 assembler back in the late 80’s.
I’ve got a huge backlog of posts that are anywhere from 10% to 99% complete, many of which will never see the light of day because they just won’t be appropriately timely enough by the time I’m ready to finish and post them. Ah well, story of my life; I can envision far more than I ever have time to complete.
Anyway, the reason for this post is to introduce the next post about a module I’m writing for Drupal. I’ve spend a lot of time recently with Drupal and am getting quite good at it, even if I do say so myself. I would have liked to have posted several Drupal related posts as a recursor but if I waited for that I doubt I’d ever manage to post about the module!
So without further adieu, on to the next post!
P.S. It may actually be a few days before I get that post finalized, but if it is not posted yes I am working diligently on it so just hold your breath… :-)