PHP framework-Is it really important to make a website or app with PHP?

I want to do a SNS website, choose PHP Framework. Every time on the internet can see a lot of controversy, despise, say which frame is good or bad. What I want to know is, is the framework really important?

Reply content:

I want to do a SNS website, choose PHP Framework. Every time on the internet can see a lot of controversy, despise, say which frame is good or bad. What I want to know is, is the framework really important?

Not important. It doesn't matter what you do. The biggest impact of the framework is the development speed, which does not affect the core of code quality, post-maintenance, and business logic. For example, if you need restful, but you choose a framework that doesn't support restful, it's up to you to handle routing problems yourself.

No rules inadequate surrounding area, the framework is essentially a collection of rules. The framework is important, but not to say which frame is important.
Find one that suits your tastes, or you can write your own one that you think is the best. I believe you will benefit from it!

Frame is the accumulation of others ' experience.
"Others", that is, the experience is someone else's, not all suitable for you; "Accumulation of experience" means that there are a lot of good things, can be directly used.

So, whether you are willing to use the framework, you should study, compare, and finally choose the most suitable for their own, even if you do not have the last one, you can learn a lot of things.

In fact, a few years of writing programs usually have some problems (such as input filtering, image upload, verification code, etc.) of the general solution, this is your own "framework."

When you use a few to say, in fact, if you do not write much code to consider this problem is a waste of time, as I thought to learn which language.

Human and different for the people who do not use the framework can be caller, it is very important to be out of the frame despair, for not 3, 4 frames out of nothing to the people to pretend to be forced to be especially important

In fact, it is not important to say. It depends on whether you want to develop efficiency or operational efficiency.
The framework will sacrifice your operational efficiency, but it will greatly increase your development efficiency. Let me give you an example.
Now I'm going to write a www.xxx.com/api.
Taking Laravel as an example

Route::get('api',function(){    echo 'hello';})

This allows us to complete a page that accesses the WWW.XXX.COM/API and outputs the Hello character.
So there's no frame, Nikki? Well, I don't think this page should fit the code.

I'm not saying here how well the framework is, and today's silver bullet laws are still there, and we can't make development more efficient and efficient at the same time.
So it has to be in development efficiency and operational efficiency options. The framework is thus born.

As for the good and bad frame is entirely dependent on personal preferences, such as some people like thinkphp automatic controller routing, someone like the Laravel manual control route, so someone started ...

The framework of good and bad after all is not so easy to assess, after all, so many users of Nepal.

So choose the frame completely look at the demand, your boss said that you 1 hours without the framework to do a blog, if not the big touch, I feel really will collapse.
If you choose a frame, it is also estimated to be 10 minutes.

The main purpose of the framework is to help you save most of the boring code.

