The result looks extremely close to what I end up writing using CodeIgniter (<a href="http://codeigniter.com" rel="nofollow">http://codeigniter.com</a>). You should give it a spin sometime.<p>To me, CodeIgniter felt less bloated than CakePHP (which is also an excellent framework, just not my style). CodeIgniter seems to stay out of the way more, and aside from having to initially rely heavily on the documentation, the framework is laid out in a way that makes sense.
We looked at lightweight frameworks and went with Yii (<a href="http://www.yiiframework.com/" rel="nofollow">http://www.yiiframework.com/</a>). CodeIgniter is getting a bit long in the tooth. Yii is a modern object oriented framework.<p>Yii uses demand loading of classes to avoid the performance problems of object oriented frameworks which load all the files off the disk for every request (see <a href="http://talks.php.net/show/froscon08" rel="nofollow">http://talks.php.net/show/froscon08</a>). And it uses prepared statements for SQL, improving performance and avoiding SQL injection attacks.<p>It's nice for simple applications, but lately has been growing to include other features.
I like <a href="http://fuelphp.com" rel="nofollow">http://fuelphp.com</a> these days, it's like CodeIgniter (by some of the same people), but modernized. I liked Kohana too for a while, but they seem way to architect-y (the docs where never up to date, things kept changing etc.). Hope Fuel doesn't go there.
I like that your approach is clean, yet configurable. Then again, most web-friendly languages already have a grip of MVC frameworks to choose from. Nice proof of concept, but I don't think your blog post would convince someone who didn't use MVC to give it a shot, like the conclusion seemed to suggest.