I think last evening it was the first time I saw someone on IRC say that the MDB2 documentation is very good. Of course there are still things missing, but thanks to the efforts of Paul and Lorenzo we now have all of the core features documented. The last piece the two added was documentation on quoting and data type handling in general. Next up we may see some documentation of the Manager and Reverse module to expand on the general Module documentation.

Autoload is kinda convenient. Especially since in PEAR we have such a clear mapping of class name to file name. I do not really understand why some libraries and projects have these insane class name to file name mappings like ez Components and I think symfony also has them. Anyways while it seems kind of nice one must be weary of the idea that they speed up your code. If you are running a byte code cache (which anyone who cares about performance of course does) you will get quite the opposite. Here is Rasmus's answer on this taken straight from #php.pecl:

So I am working on two quick prototypes that are heavy on the Ajax/Javascript front. Been a while since I had to code stuff like that myself actually since in the past years I have always managed to push that kinda of work to other people on the team. Anyways in the prototypes I am doing a bit of drag and drop, I have sliders, moveable popup panels, forms that get submitted via Ajax and that update parts of the interface and web 2.0 stuff like that.

.. I am almost a bit embarrased to say it .. but my diploma thesis is now published on Lulu for print on demand. This is version 1.0.1 which contains a few typos fixes spotted by people in the community. Many thanks for that feedback!

MySQL AB invited me to Frankfurt to talk about their PHP native driver project. While I am not much of a C-hacker, I do know database API's and users preferences in them quite well from my work on MDB2. As such my job was to present a wish list for features. Do note that this is a wish list and any features I mention in this blog post are not yet in any definitive plan. Aside from that, I also took it upon me to make sure that whatever we do, we try to keep the API as clear and simple as possible.