Drupal 5 has been released for a while. It comes with lots of changes in APIs as well as in the core engine. One of the reason to drive changing the core engine of Drupal is performance. If you remember the performance comparision of Ruby on Rails, Django and Symfony (read here) last year, the performance result was Django, Ruby on Rails and Symfopy, respectively. Django was outperformed because Python is generally run faster than the rest. Moreover, PHP is always the slowest one even with any kind of accelerator.

Anyway, Drupal may break above results. It's just a matter of time. Drupal 6 is one of the promising CMS I imagine.

If you notice some weird in this site, there are something wrong since I used this theme. This theme is bluebreeze. It is nearly perfect especially for SEO except only one big problem regarding anchor (see issue). Well, it is also beautiful at least for me. The theme is good but the layout is too advanced for standard CSS. I found another good layout in Aberdeen. Anyway, the theme is not for me at all. So my solution is to use Aberdeen's layout with the bluebreeze's theme.

Dries posted about the review of Drupal 4.7 against other popular CMS, e.g., Joomla, Mambo, Midgard, Plone and Typo3. I don't have a copy but Dries took some photos to show Table of features. As a result, Drupal 4.7 has all features while others are missing some of them. Cool! That's just Drupal 4.7. We have Drupal 5 (Drupal 5.1) right now. I can't imagine what will be in next review of Drupal 5 against other CMS again.

The built-in Ping module bundled with Drupal is not as good as I expect to have on my site because it only notifies Ping-o-Matic. I just want to ping to custom list of pinging services. I have also found multiping which was initially referred in a thread. Actually, I patched the built-in Ping module to support custom Ping services, both ping and extendedPing. Anyway, it is not as good as multiping provide to me. Unfortunately, multiping has not been ported to Drupal 5 yet. That's why I have to do it today.

One thing I would like to track in my sites is how many query got 404 or 403 error. Sometimes, 404 means something wrong by me. Anyway, I have my hero, customerror module.

Another useful module for all content-based sites is gsitemap which interacts with efficiently. This module already has its branch for Drupal 5. However, it doesn't work properly on Drupal 5 yet.