Problems existing in common PHP frameworks such as ZF

Starting from Zend Framework v0.13 version, I began to learn to use Zend Framework. One of the company's projects at that time also happened to use Zend Framework. After version 0.6, I no longer paid attention to details. I heard a few days ago that Zend Company will officially launch Zend Framework in May. Today I specially asked my classmates to download it and test it.
The latest version is 0.93. The test found that the Zf framework is becoming more and more fool-like. Many things are directly packaged in ZF's library. As long as you know how to call it, it's OK. There are indeed major changes from the previous version, and more functions have been added.
First of all, Zend.php is gone, replaced by a Zend_load class, placed in load.php.
Second, loading library classes is more convenient. The previous ZF was more troublesome to use in subdirectories. It can now be used directly in subdirectories, and it can now be used without mod_rewrite. It can be accessed through http://path/to/site/controller/action, similar to what I wrote in "Answering several questions on PHPCHINA: URL Mapping" talks about URL mapping.
Third, the view is directly integrated into the Controller for easy calling. However, one disadvantage is that the directory structure of the program must be standardized according to the requirements of the government.
In addition, many functions have been added, such as access control and so on. All in all, a lot has changed. I only took a brief look at it tonight.
For frameworks such as ZF, cakephp, etc., I think it is best for everyone to understand the basic principles of the framework when learning. The so-called "everything is inseparable". The framework itself is very simple, not as complex as ZF and the like. They just handle the details very well, and at the same time they have to be universal, standardized, and powerful, so they are complicated. Regarding the basic principles of the framework, I recommend you to read an article on phpit.net about how to use PHP5 to build a simple MVC framework (translated on Joy International Village), or you can read several of my articles "PHP The easiest way to implement MVC development" series of articles.
There was a post on chinaunix before, discussing the advantages and disadvantages of using objects and procedures in PHP projects. The discussion was very good. Some support objects, while others believe that non-object development is more in line with the characteristics of WEB development and has better performance.
I personally strongly support object-based development, especially in the PHP5 environment (because the objects of PHP5 and the objects of PHP4 are completely different, just look at the Zend engine to know this). But the points mentioned in the post are also very reasonable: for example, "the form of OOP has to be loaded with many irrelevant functions for no reason."WEB development places great emphasis on performance, and PHP is an interpreted language. If too much code is included, performance will be greatly affected. This problem exists in Zend Framework, CackePHP, Fleaphp and my framework PHPbean.
For example, an indexController, here we use Zend Framework as an example. The code is as follows:

class indexController extends Zend_Controller_Action {
function init(){
$this->initView();            //echo 'index/index';                                                   ->view->title='hello World!';
                                                                                                 Action(){
echo 'index/show';
}
}
?>
For example, if we access index/index, then the contents of the testAction() and ShowAction() methods are completely redundant. In actual development, according to this idea, a functional module generally corresponds to a controller. For example, a user corresponds to a userController, and there are many methods such as login, logout, registration, list, detailed display, etc. When a project is large, a controller may only have a few K to more than ten K. Then this model is very bad.
In JAVA’s struts, a completely different approach is adopted. One action corresponds to one file. I think this is a good reference method.
I think in PHP5, it is better to use object-oriented. It can be said that what can be achieved when facing processes can be achieved when facing objects, and it can be achieved even better. But the important point is: use object-oriented thinking to use object-oriented thinking, rather than using process-oriented thinking to write object-oriented programs!​
The above introduces the problems existing in common PHP frameworks such as ZF, including aspects of the content. I hope it will be helpful to friends who are interested in PHP tutorials.