First, the raw material is good: it is based on the best components in the world. As long as you have good components, you don’t reinvent the wheel. Therefore, good raw materials reduce the risk of using unknown components.

Second, good architecture: it adopts Facacde, Contract and other architectures, so that all components can be replaced. That is, if you think mine is bad, you can change it, and this approach opens up the whole framework of development interfaces to people, so that it can be used in a variety of combinations. For example, Route, you can use Dingo/ API. So, well structured. You always have the quickest way out of a problem.

Third, good workmanship: Laravel developers have done a great job in programming, single responsibility, convention over configuration, opening and closing, etc. And by doing so, not only is the user experience programmer friendly, but the code reading experience is programmer friendly as well. It’s hard to find functions with hundreds of lines in Laravel. Most importantly, easy-to-read code allows you to quickly understand and modify it. So, let you rest assured that you are not afraid of problems.

Fourth, good functionality: development efficiency, Facacde, dependency injection, etc., almost eliminates the need to create objects in New. It’s not just lines of code. A lot of times it’s architecture. Dependency injection abandons a lot of CTL C CTL V. Also, the Artisan command lets you batch create models, controls, and extend them to create repositories, services, and so on.

Fifth, good experience: user experience first, the documentation is quite comprehensive and excellent. At the same time, it provides quite good logging (Mono Log) and debugging tools (DD). There are also automated tests in PhpUnit. Facilitate test-driven development. Reduce release risk.

Sixth, good components: Good built-in components: The Blad template engine of the year was probably the best PHP template engine in the industry. Eloquent Orm is not a complete Orm on the surface, but it’s an excellent, almost the greatest solution to the problem of object mismatch, and therefore the most fundamental: user experience. At the same time, the built-in components are comprehensive, routing, messages, events, queues, broadcasts, and so on.

Seventh, community is good: active community, in Laravel, is more or less: there are only things you can’t think of, and there are few things that nobody does. So, in this case, many of you just install components, or copy components (which you can’t trust to use if they don’t conform to open source specifications). As such, this is another factor that allows you to develop quickly. A good community, with easy access to technical support.

Eighth, good performance: Laravel has a large amount of code is used to make you easy to debug during development, write code fast, run, easy to monitor, and truly secure and efficient in performance. Laravel is one of the PHP frameworks with the fewest security vulnerabilities, and the bug repair rate is 100 percent, and the bug repair rate is super fast. Think what the user thinks.

To sum up, Laravel allows you to: use it with confidence, use it with ease, use it with ease.