We’ve examined ZFI from the view point of its architecture, as well as the use cases developers have ADOPTED. In many cases, we simply cannot support existing use cases, or the architecture needs to change in order to do so. Additionally, since ZFI grew very organically, there are many PLACES where similar solutions to similar problems are inconsistent, leading to difficulty educating developers. In Zend Framework 2 we’ve used a consistent set of coding patterns and practices and we’ve TAKEN into account the GENERALLY acknowledged best practices for writing efficient reliable, and high-performing software.

We’ve examined ZFI from the view point of its architecture, as well as the use cases developers have adopted. In many cases, we simply cannot support existing use cases, or the architecture needs to change in order to do so. Additionally, since ZFI grew very organically, there are many places where similar solutions to similar problems are inconsistent, leading to difficulty educating developers. In Zend Framework 2 we’ve used a consistent set of coding patterns and practices and we’ve taken into account the generally acknowledged best practices for writing efficient reliable, and high-performing software.