Thoughts on the Framework

Most friends with experience in object-like programming often use their own solutions.
There are several projects XX. Framework (or XX. Framework. yy...). I cannot remember when so popular habit was available.

I am also chasing fashion, my ownCodeIs also very happy with the addition of a XX. Framework Solution
When I accidentally opened the design document to view this framework, I began to be surprised: When did my framework start to look beyond my imagination...

To verify that the framework is not the same, I checked the meanings of framework and framework.
Framework, framework, and structure
The framework means: 1. Providing a structure of shape or strength 2. representing the organization and structure of a thing
The role of the Framework in the entire solution is obvious.
My understanding of the framework: a project (solution) that provides the basic organizational structure and limits the entire set of software (or upper-level systems)
It is quite different from several component projects that provide various logical functions and business operations.
The framework should have a loosely coupled structure to provide flexible and rigorous calling, inheritance, and implementation mechanisms, rather than a util dedicated for other project calls.
My mind flashed several mature frameworks in the Java World and reminded myself never to write the framework like utils again.

You are welcome to discuss this and sincerely thank you for your correction...