Why is Yii/Yii2 not suitable for large projects?

Question

Yii

Hello. I study the Yii2 framework and in the process of learning very often on all sorts of forums I meet the opinion that Yii for large projects is pain and suffering. But I haven't found any clear explanation why this is so.
Some say that if you do everything right from the very beginning, knowing the weak points of Yii, then it will work for a large project.
Dear developers, please explain why Yii is poorly suited for large projects, what are its weaknesses and how to solve them?
Thanks in advance to all who respond.

Answer 1

We have 4 enterprise projects in Yii2 in our company. Including CRM. Including communication with telephony, 1C, bug tracker. Everything works great, no complaints. What "weak" places are you talking about? Stop reading - start doing!

Answer 2

There is a large project on Yii1, about 500 models and 300 controllers and 2000 views. No changes were made to the framework; if necessary, heirs were created, which are used by the project instead of the standard components of the framework. There are small problems associated with shitty code and a large amount of data (changing the afterFind model, for example, with unreasonable use of AR links), which led to brakes, but this is rare. Actually, a properly designed project eliminates many problems of shitty code. Unfortunately, I did not use other php frameworks in the enterprise and I can not compare the usability

Answer 3

Because the more powerful the framework, the easier it is to write something quickly on your knee, and in large projects, your own Wishlist appears that are not in the framework. As a result, pain is born in the form of your own microframework on top of the framework, which de facto will be crutches or climb into the framework, read and understand how it works and expand it with the necessary functionality in the same style as the entire framework as a whole. The latter is usually the most hemorrhoid.

Answer 4

Yii2 is suitable for large projects (wrong =D ) but if you don't like it, take another framework, language, whatever.
I don't like php for example .... no jokes about php programmers and so on, no real complaints, just don't like it. I order development on it if I need it, I don’t see anything terrible in it, but asp and Python are closer to me
. The market is huge. There are many solutions for every taste, nothing prevents you from choosing the right one.