I just learned php, and it's completely a little white. I 've read a lot of tutorials and wrote php in html. I feel that there is no separation, so I am skeptical about the tutorial. Is that true, or is it possible to separate the framework? I just learned php, and it's completely a little white. I 've read a lot of tutorials and wrote php in html. I feel that there is no separation, so I am skeptical about the tutorial. Is that true, or is it possible to separate the framework?
Reply content:
I just learned php, and it's completely a little white. I 've read a lot of tutorials and wrote php in html. I feel that there is no separation, so I am skeptical about the tutorial. Is that true, or is it possible to separate the framework?
If you understand the history and essence of php, you will find that such mixing is actually the original usage of php, or is it an advantage. isn't it because of its rapid development? Later mvc and template engines were designed for collaborative development and management. If you ask me which one is faster than native mixed editing and framework mvc, I will tell you that it is definitely native mixed editing. Therefore, you can use hybrid editing for small projects. for larger projects, use the framework. As for the tutorial, he is right. As I said, php is like that. you can say that you use the framework for management convenience, coupling, and other reasons, but you cannot put it before the horse in learning, the basics are very important.
It should be said that it is written together for ease of understanding, or PHP can also be written like this. After the basic skills are solid, considering code maintenance and multi-person collaboration, there should be a "separation" method to ensure the code is "neat ". If you are a newbie, we recommend that you have this concept and "yearning" in mind. The most important thing at the moment is to follow the tutorial to lay basic skills.