Individual views of the PHP framework, there is no need to specifically promote which one, original aim

Some people say the frame is very complicated, very iffy,
But is it true that many of these frameworks are not patterns of routing + class libraries?
Give an example: there is a file index.php
Run http://www.xx.com/index.php
And
Run HTTP://WWW.XX.COM/INDEX.PHP/1/2/3/4/5
Is there anything different about the results?
Answer: no different

Well, if we take the 1/2/3/4/5 off the back,
Like 1 for the class name.
2 Method of representation
We new 1,
Is it called the 1 class file?

And then remove the index.php, it becomes
Http://www.xx.com/1/2/3/4/5

Well, the framework has been made to do this
Ordinary mind, do not tangle how to do the framework, the development of ideas is the most important,
All roads pass through Rome.

Reply to discussion (solution)

Framework, nothing more than a tool for developing applications

Like a hammer is used to beat the general
If you still need a nail, you should choose the one with the nail.
If you want to build a small iron bowl, you have to pick the ball.
Whichever you choose, the hammering property does not change
Of course, you don't have to use a hammer to pick up a slab of bricks.

Landlord said good, the moderator said is also true, the main or basic skills, the framework is a tool.

Agree!!!

Have their own methods and ideas, summed up a good, to create a suitable for their own, on the line.

No use of frames, slowly learning to use. Oh..

Agree with the version and landlord, the framework to consider a lot of other issues, the landlord is from the framework design and call the perspective of the framework of the work process, as a general framework for users from code reuse, easy maintenance, easy to expand, performance improvement, stability, learning costs these aspects to choose

The role of the individual person for the framework
1. Code Organization
2. Code Reuse

No need,,,,,

You just said what it is, but why is it designed like this? Why use routing? What are the benefits and drawbacks of a single entry? How do you enhance the scalability of your framework?

You just said what it is, but why is it designed like this? Why use routing? What are the benefits and drawbacks of a single entry? How do you enhance the scalability of your framework?

Single entry for easy control, right?
and other ideas.

The main analysis is very reasonable, it must be Daniel.

PHP people always like to say that PHP is simple, the pursuit of simple, not architecture and mode, I do not know like thinkphp with M,c,s,p,i as the function of the name is not what they call simple.

