Is PHP better to use or JAVAweb?

Is PHP or JAVAweb better to use?

Comparison:

1. PHP is ready to write and use.

That is to say, only one change is completed at a time, and the user sees the effect immediately, while Java is much slower. After the code change is completed, it needs to be recompiled and then the jvm restarted, which takes a lot of time. , and restarting the jvm process will interrupt user response.

2. PHP writes things quickly.

php can be said to be very agile. Given a requirement, as long as the later performance and user volume issues are not considered, it is quite fast. You can even write directly without a framework and it will be very fast. , writing an add, delete, modify, and check function may only take 30-50 lines of code. Java is much slower. First of all, you have to think about what framework to use, which is basically spring at the moment. Then you need to configure various databases, filters, and servlets, decide whether to use mybatis or hibernate, and then consider the transfer of codes, and then Think about business. . . Then keep debugging, and you can imagine that it may take several minutes to wait for the code to be changed.

Recommendation: "PHP Tutorial"

3. The surface ideas of php are clearer.

What is the superficial idea? What you see is what is actually made. For example, echo "hello world" is to output hello world, but Java is different. You may write it in response, or it may be Written in modelattribute, it may be that the string is returned, and then somehow it is displayed on the page.

4. php takes up less memory.

PHP handles problems in a process and takes up very little memory. It can be said that you have no problem deploying 50 projects on one machine, as long as the number of visits does not increase, it can be done. But Java doesn't work. Every time Java starts a project, it has to use up a lot of memory. For example, on a machine with 8g of memory, running two projects is usually enough.

5. Having said the benefits of php, doesn’t Java have any benefits? That is impossible.

6. There are many java components.

I personally feel that this point alone outweighs all other advantages, because the large number of components means that there are many people using it, and the public’s eyes are sharp. Therefore, Java must be good. It has accumulated too many things and cannot be easily replaced by a new language. Whatever you want to do, search carefully for java components, and you may have the functions you need. Especially for the most popular big data industry at the moment, java is even more dominant. PHP is a little helpless in this scenario.

7. Java thread pool, connection pool, and asynchronousization are convenient.

In fact, this point is very similar to the first point. Because there are many components, it is very convenient to use thread pool and connection pool. This is absolutely necessary for high concurrency and high performance scenarios. Because Java runs multi-threaded, there is no need to initialize many basic things every time. This saves a lot of time, and therefore everyone can tolerate the slow process of server startup because it only happens once. PHP, on the other hand, is multi-process and needs to reload all the required code every time. Therefore, some commonly used data cannot be saved in the memory. The connection pool is not easy to do, and asynchronous operation is a big shortcoming.

8. Java is truly logically clear.

Because, in Java, you can use IDE tools to analyze the deepest logical operations from one entry to the next. Each field can be clearly understood. This is actually an advantage of using interfaces and complete objects. PHP cannot do this, or very few people bother to do it. PHP can be said to be semi-object-oriented and semi-process-oriented development. Therefore, it is normal to insert several custom function calls during the calling process. Then it will not be so easy if you want to analyze the call chain through a simple IDE. For example, for interfaces provided by third parties, it is difficult for PHP to clearly see what the interface returns unless you print it out, but printing may not be correct because some return value data may not be reflected. This adds a big threshold to understanding the code.

9. Although java compilation is troublesome, it can detect errors for you in advance.

Java compilation is indeed more time-consuming, but if there are obvious errors, the compilation will not pass, which gives you an opportunity to recheck the code. But PHP will not. No matter how poorly you write, it will not give you any prompts. In many cases, it is often because you have written a missing semicolon, causing you to troubleshoot for hours.

10. Java remote calling is convenient, rmi, hessian, dubbo.

No matter what, remote and local calls are very convenient to know relevant information, and Java's same language calls do not use pure http calls, but maintain a certain connection, thus greatly improving performance. PHP also has remote calling, but it is relatively weak.

In fact, no problem is absolutely good or bad, and its existence is reasonable. It’s just that the application scenarios are different.

The above is the detailed content of Is PHP better to use or JAVAweb?. For more information, please follow other related articles on the PHP Chinese website!