If someone can't keep their projects in shape and with good architecture, it makes sense to have a prescriptive framework. This is especially true for distributed teams with developers of different levels and habits, if you do not have organized styles, supervision and code reviews.

But to say that makes React somehow bad is a bit of an, err, exaggeration. Just make an effort to organize and follow standards and processes, and use less verbose state managers like Mobx (you will be surprised by NgRx, by the way). You always need to pay: if you put architecture into a framework, you will face serious problems in the future when you realize that your vision is not the framework's vision. If you speed up your development with chaotic 3rd party React components, you will constantly pay for refactoring and consistency.

And speaking of maturity and organization, the latest changes in Angular (standalone components, signal) make it more like React, what an irony =)