Lead the development of their php framework, the main objectives of which is the compactness of the engine, the ease of use when developing sites in it, and of course, upload speed pages.
Each framework represents versatility.
When zarabotki universal solutions — we lose something. What the solution is universal, so it is less productive. For this when designing the bike to answer the questions:
— what are key tasks I'll be on it to solve
— on what hosting it will live
— what additional features I can use
— what more can I erode under its decision.
The more features I can manipulate, the more productive I will be able to construct.
As an example, can you recommend your bike
He sharpened for specific technical solutions, and its speed is superior to ZF in 4 times if you disable caching and acceleratori on addnotify Malorechensky queries. With other frameworks because of their ignorance I did not compare. The main feature featured in the blog "High performance".
As the Board can tell: to achieve the performance effect is necessary to develop a system so that the number of calls to the database was minimal, and better to not exist at all. Kal-joinnow reduced to zero, Not afraid to sgoniat and sort on the client, and not afraid of denaturalization, as the cost of quick return str more than the cost of disks. Looking for alternatives. Practice shows, all unsuccessful (brake) projects are poorly designed database and reference it.