Write a PHP framework.

Certainly ask: Now the PHP framework is so many, why do you want to write a PHP framework?

1, Time: PHP7 come, now all the framework is based on php5.x. Then PHP7 formally promoted out, the existing framework can not play PHP7 maximum performance advantages, such as strong type and JIT. There will be a version splitting problem with many frameworks, and many frameworks need to maintain two sets of code at the same time, some of which may be out of the question. So now to write a PHP framework will be PHP7 as the minimum version requirements, although now PHP7 or beta version, framework development is a bit more difficult.

2. Length: How much does a framework develop? Personal point of view: from development to testing, to experimental projects, to the beta, it should take a year to two years time. From the launch to the public perception, it is estimated to take six months to a year. So the entire budget, such a framework from planning to enter the public view of the time will take two to 2.5, and this time, the prediction of PHP7 has generally entered the public platform.

3, Interface: Here said interface refers to the framework user's API, from the current domestic situation, thinkphp in domestic companies in the use of the situation occupies an absolute number of advantages. and its easy-to-use features are obvious to all. The user experience has always been the best thing that Chinese people are good at. So, it's compatible with the TP interface.

4, Architecture: MVC architecture must refer to foreign countries, but it is recommended to plan, then refer to, do not copy completely. A PHP framework is technically despised by almost all senior developers for not appearing the second time.

5, add: The existing PHP framework is pure PHP, but the development of the site is a whole, in the development process of this site, the front-end and the bridge between the background JS is particularly important. So in the newly developed PHP framework, we should develop the matching JS method library, the proposal is similar to the jquery-based extension of this category.

6. Community: Can you consider merging with existing communities? I suggest that the community with TP, because everyone's interface is the same. Another point is the TP community is very active, the user volume is very optimistic. Many people use TP is also at the level of use, and not very deep to the framework of how to achieve, so at the application level there is reason to consider the merger with the TP community. In the framework architecture and internal implementation, you can consider the TP community to open up a separate piece. May consider to be TP merger or merger TP →_→

7, Document: The document must be orderly! Clear! Beautiful! TP is definitely an example of this.

8, internationalization: Must have English version, GitHub suggested on the English version. To unite all the forces that can be united, the technology of crooked nuts is very cow, let them force their strength. TP is an example of a living failure in this respect, so its architecture has been despised by people of technology ...

So do it now! or TODO or let it go

Write a PHP framework.