CodeIgniter's Future

[eluser]nmweb[/eluser]
Adding features or changing current behaviour I deem more important than php4 support. CakePHP and WordPress are still going strong and support php4.

However, the lack of OOP patterns seen in the storing of the instances of libraries in the singleton super object and thus losing all advantages of OOP and returning to procedural code. Why can I not have multiple instances of the Mail class by having a factory instead of storing the one instance in the super object. ->factory('Mail') or something. CI is easy to learn since there hardly is any OOP. Just usage of classes to emulate namespacing of some kind. Php5 wouldn't help anything here.

Other features like reverse routing (better routing in general), internal forwards, layouts, before/after filters, action that is called when no matching action is found, matching views to actions. I know some or perhaps most of this can be achieved by hacking into CI and many have done so, still having this sort of stuff in the framework is preferred to having to pick a solution from ten repositories spread around the internet. Php5 may be nice, the magic functions are certainly cool for syntactic sugar and me personally can't wait for 5.3 to ship with lamda functions but lack of php5 is not the problem of CI. I loved CI and have learned a lot from it but long since have moved on.