It wasn't until just now that I realized how different people's usage of PHP is.

The cause of a series of tragedies is that everyone has different native languages ​​(of course, I am talking about the native language of the program).

For early PHP users, most programmers were already familiar with programming before coming into contact with PHP. Therefore, when they come into contact with PHP, what they care about is not what PHP can and should do, but PHP and what they have mastered before. How languages ​​differ, and how to eliminate them.

For example, Smarty is the thing that puzzles me the most. I can’t understand why I need to use this kind of thing that takes off my pants and farts. And I think there were so many template classes at the beginning, but today I understand that basically every language has template classes. , so when they use PHP, they naturally think that they need to build one, but they have been avoiding the most basic issue: PHP is a template language. So they used PHP to implement another language called Smarty. It makes me feel very inferior because I have never been able to use Smarty, so when I recruit people, I always ask if they know Smarty. What I think is that as long as someone knows it, it will be fine.

Another thing, I don’t know whether I should criticize Controller alone or MVC as a whole. After I wrote PHP for a few years, suddenly everyone started to parse $_SERVER["REQUEST_URI"] and require the corresponding files by themselves. This is called a unified entry. This also surprised me. I believe that too many people have encountered the situation of having to modify the PHP file in order to add a Google Webmaster verification file and the like. This is really asking for it. Later I realized that in many languages, the entire web server has to be implemented by itself, so parsing the URL is part of the job. But PHP is parasitic on the web server, so there is no need to worry about this problem. At most, the url writer of the web server is used for beautification, not for functionality.

There are also some wrong optimization directions. For example, some people proposed not to use require_once but only use requrie, because the former will add an operation like in_array(), which is really frustrating. Maybe this overhead will be in the kernel of the operating system. It is amplified by loops, but for web overhead, it is not even a drop in the bucket. How many machines can be saved by letting Facebook programmers make such substitutions in their code? For your actual application, can you save two pieces of memory? Is it enough for you to pay for one morning?

These are too far gone. In view of the various strange ways in which PHP is used, I can only guess that this phenomenon reflects the different understandings of PHP by programmers of too many different languages. Many people who have written some C or Java use C or Java to write PHP. And teach new programmers to write PHP in this way. In their eyes, PHP is slightly worse than C or Java, because PHP cannot implement certain features, but they rarely think about why they should use it. PHP, maybe just out of compulsion, not a choice?

Receive LAMP Brothers’ original PHP tutorial CD/"Essential PHP in Detail" for free. For details, please contact the official website customer service: http://www.lampbrother.net

PHPCMSSecondary development http: //yun.itxdl.cn/online/phpcms/index.php?u=5

WeChat development                                                                               

Mobile Internet Server Side Development http://yun.itxdl.cn/online/server/index.php?u=5

JavascriptCourse http:// yun.itxdl.cn/online/js/index.php?u=5

CTOTraining Camp                                                                                             5