How does the PHP framework distinguish between good and bad?

How does the PHP framework distinguish between good and bad? It was strange to see different people commenting on different frames. I am a novice php, at present is just a simple use of the next thinkphp and CI, is not very useful, just understand the next curd, but I really do not feel what the essence of the difference, as a newcomer how to choose the right frame of their own?

Reply content:

How does the PHP framework distinguish between good and bad? It was strange to see different people commenting on different frames. I am a novice php, at present is just a simple use of the next thinkphp and CI, is not very useful, just understand the next curd, but I really do not feel what the essence of the difference, as a newcomer how to choose the right frame of their own?

The general design framework needs to weigh two points: development efficiency and operational efficiency. Some framework development efficiency is very high, many things are provided by the framework of a ready-made solution, many complex features only need to write their own configuration and a few logic, the cost of this framework is generally inefficient operation, many complex situations need to be encapsulated within the framework of the code processing, a large number of logic and pre-judgment you can not use in the framework Some frameworks can even be initialized for hundreds of milliseconds. Other frameworks provide only a few core features, and a slightly more complex situation requires the developer to code the implementation, a framework that generally pursues simple functionality and high operational efficiency.

Since is a novice, only write a simple program, it is not easy to find the pros and cons of different frameworks, at this time do not have to choose their own framework, direct use of the company's master choice of the framework, more accumulated experience is good.

Meet two points:

1. And your own code level is the best fit

2. And the projects to be developed are the best fit

is the best.

First thinkphp get started to do something with a sense of accomplishment, learning PHP has been developing new features

Not the best, only the most suitable

Direct pass with no unit test

Good or bad no absolute, the key is suitable for your =￣ω￣=

You think it's good to use. Just like the phone you like to buy. Android and iphone with you. No, absolutely.

I think it's good to be useful

1, the use of more people: problems are easy to solve
2, the document is comprehensive: if there is a Chinese document, the use is very handy, if the English super good, can ignore the advantages of Chinese documents.
3, easy to get started.

Bought a PHP book, read a few pages do not want to read. And then thinkphp began to look.
Missing a master who brought me in the door. /(ㄒoㄒ)/~~

Strong extensibility, low-level code structure and clear annotations, should be able to

It's not good or bad.

The higher the degree of abstraction, the more efficient you develop.

Framework first provides a standard second to improve development efficiency

When advanced, you may wish to learn how to use the world's first Laravel

As a novice, want to understand some concepts, you can now learn TP, because there are many Chinese documents, the community are people, the basic problem can be solved
CI is also available, the documentation is also very rich

When you have a certain development experience, and then try to laravel or yii this framework, it may be easier to understand

At first, it is good to not use the framework, to understand some basic principles, such as the principle of paging, many of these frameworks are encapsulated, many people do not know the principle of the inside

There is no good or bad points, as long as you like it is OK.
Like a girl, no good or bad points, as long as you like, she is the world's most beautiful woman.

Use more to feel the frame when it is more useful

