PHP vs Node.js Smackdown: Right of Reply

SitePoint recently held a peak showdown between PHP and Node.js, and Craig Buckler puts these two development technologies into one of the ten challenges to determine the ultimate winner.

As Craig points out in the article, this comparison is always controversial. As an interesting follow-up, we invited Bruno Škvorc (PHP editor for SitePoint) and James Hibbard (one of SitePoint's JavaScript editors) to comment on each round.

The following is their round-by-round evaluation...

---

Key Points

• Because PHP is simple to set up and get feedback immediately when running scripts, it is easier for beginners to get started and win in the "Beginner" stage.
• Although Node.js is younger than PHP and less support is available, it is known for its vibrant and rapidly growing ecosystem, especially in the field of development tools at npm.
• JavaScript is used both in client and server development, giving it an advantage in syntax familiarity, although the latest updates to PHP have greatly improved the consistency and robustness of its language.
• Because PHP is widely supported in managed services, the deployment process is simple, and the barrier to entry for new developers is low, it remains the preferred choice for traditional web hosting and deployment.
• The performance battle between PHP and Node.js shows that both can be optimized for high performance, but due to the non-blocking nature of Node.js, it has advantages in handling concurrent processes and real-time applications.

First round: Getting started

The first round of challenge was to see how fast you can build a "Hello World" web page in each language. This includes the time it takes to set up the server environment.

PHP won the round in Craig's estimates, partly because it's "conceptually simpler" and "less intimidating for new developers".

Bruno:

PHP wins in "beginning" purely because more hosts make it so easy to get started. This is an adoption issue, not anything else. If more hosts bypass the command line using Node and go directly to the simple "Reload Application" button in the file upload and control panel, they will be equal. However, the actual syntax of showing something on the screen is much simpler in PHP – especially for programming newbies.

James:

I didn't see a big difference between the two when developing locally. To run PHP scripts in a browser, you need to install some kind of server stack; to run Node scripts, you need to install Node, and it is better to install a web framework, such as express. But, as Craig says, PHP is conceptually simpler. The entry barrier for Node is higher. There is no objection to this.

Round 2: Help and Support

The second round examined the difficulty of getting help and support in each language. PHP won the round mainly because of its long history.

Bruno:

Bruno remains silent about this

James:

I agree with this. Node.js is a newer technology, so there is less help available at the moment. However, as Node matures, this will become less important.

The third round: Language grammar

The third round compared the ease of understanding and use of the syntax of PHP and JavaScript. Craig awards this round to JavaScript.

Bruno:

I strongly disagree with this. While PHP does have some quirks, many of them have been corrected recently, and many of the quirky things will be removed in the latest version. On the other hand, there is this situation and this situation in the JS world.

About point 3 ( Your brain does not need to switch modes, because you can use JS on both the client and the server side), I disagree. The server environment is completely different from the client environment and requires switching brain mode. There are also some new syntaxes that you can't use in your browser and vice versa, so it's a bit like switching languages.

Point 4 ( Understanding JS will make you want to use it more) is also a point I disagree with. I've been using JS and PHP for years, and the more I use JS, the less I like it - but it's purely a personal preference.

James:

I like JavaScript. I know it has its quirks, I know it has some pitfalls, but ECMAScript 2015 will correct a lot of these issues and bring some exciting new features to the language. JavaScript is both powerful and flexible and can adapt to many different programming styles. Compared to PHP, I like writing JavaScript. Node deserves the victory in this round.

Fourth round: Development Tools

The fourth round considered the tools available for each technology, and Node narrowly won due to npm.

Bruno:

Although Composer was originally inspired by npm, it is now much better than npm, and if two versions of the same library have to be installed, it won't break your system, unlike npm. Unlike npm, Composer can install recursive dependencies, which is something that npm simply cannot do – but it is absolutely necessary and should be the first thing that comes to mind for those who are starting to build a package manager.

npm also has some really bad error messages that I like to call "core developer-friendly" - only those who write them can understand them. Finally, npm doesn't work well with Vagrant, effectively preventing you from starting properly – not to mention they don't have the desire to follow the user. This is a bug that has been around for years, making it essentially unusable on Windows – it is by no means a trivial user base. PHP also has its own stupid mistakes, but these mistakes won't alienate users of the entire operating system for years.

Granted, Composer is not bundled with PHP, but I don't think it should do that. A package manager that is actually a separate application should not be partial. If someone, one day, really made a good package manager for Node, then replacing it with the current package manager would be a bureaucratic hell, let alone let alone make people transition. Also, installing it is really just a line of terminal commands, or downloading an installer.

The statement that Composer has less impact is completely wrong. Since the development of Composer, it has affected all new PHP developers who have joined the ranks of PHP, and most of the great developers who have to add it to their current workflow. Just because there were a lot of PHP users before Composer appeared, it doesn't mean it has a smaller impact. It has had a huge impact since it was created. Absolute statements such as “less impact on the community” should not be made without factual basis.

I can't argue with the fact that most PHP developers end up installing Node, which is true. Sadly, many excellent tools are preferred to develop with Node, but I still want a Node-free development environment due to projects like BowerPHP.

James:

I am very happy that Node won this round.

I like npm. It is easy to install, easy to use, and can meet almost any need, with thousands of available packages. I also like that npm allows you to choose a global installation and a local installation package (as opposed to languages ​​like Ruby, where gems are usually installed with your Ruby version). The tool is also very good. Tools like Bower and Grunt take a regular place in my workflow and have increased my productivity many times.

It is also worth mentioning that npm v3 is in beta. This solves many of the problems raised by Bruno, such as nested node_modules method errors.

Introduction to the entire peak showdown:

PHP developers may eventually want/need to install Node.js. Otherwise, it is not the case.

Fifth round: Environment

The fifth round involves the use and deployment location of the technology, as well as which platforms and ecosystems are supported. Craig doesn't make clear what he said about the round, but it looks like a crushing defeat for Node.

Bruno:

Craig says he will compare the web advantages of PHP and Node (general web development challenges), and then says JS is everywhere. First, we compare Node.js instead of JS itself. Secondly, we compare the language and environments they can run. It is just stupid to say that monkeys are better than fish because fish cannot climb trees. But monkeys and fish can swim, so let's compare how much they swim.

PHP wins easily in a web development environment. There are some tools in PHP for desktop development – ​​yes, indeed, you probably won't use them. But you can definitely use the command line aspect of PHP.

James:

Similarly, I agree with Craig. Many of the features that make Node.js so popular (speed, scalability, affinity with JSON, low resource usage) also make it very suitable for many other types of applications, such as powering IoT devices. I mean, who doesn't like robots?

Node also gave birth to projects like NW.js (application runtime based on Chromium and Node.js), which allows you to write native applications in HTML and JavaScript. An exciting time!

Round Six: Integration

The sixth round examines integration with databases and drivers, and PHP wins mainly because of its long history.

Bruno:

Integration is a draw. PHP has an age advantage in this area, offering more options, but it also means it suffers from some seriously outdated integrations like the mysql extension - we only managed to get rid of it in PHP7, but it hasn't been able to do it for years use.

James:

I'm not sure I agree with this. The wording throughout the round seems vague, and I hope there is an example of "older, less popular technology". This can also be a great opportunity to emphasize a great advantage of Node - it uses JSON. JSON is probably the most important data exchange format on the web and is also a common language for interacting with many of the latest NoSQL databases. JSON is perfect for JavaScript programs, which means that when you use Node, data flows smoothly between layers without reformatting. You can use a syntax from your browser to your server to your database. Round 7: Hosting and Deployment

The seventh round examines the difficulty of deploying new applications to real-time web servers, and in Craig's view, PHP is a clear winner in this regard.

Bruno:

Again, Bruno remained silent, nothing to add

James:

This is an area that Node needs to catch up. Every economical web hosting company offers a PHP package containing MySQL. To see some kind of output, you just create a file with the .php extension, put some valid statements between ?, upload the file and point it to your browser. This is not the case with Node. Of course, there are a lot of Node hosting options, but they always require more settings and command line access, which can be deterred by beginners. PHP won the round without a doubt.

Floor 8: Performance

The eighth round focus on speed; although it usually depends on the experience and effort of the development team, Craig points out the advantages of Node in multiple ways.

Bruno:

Misunderstandings abound. First, this post makes all performance discussions pointless. Any and all performance gains/losses are entirely dependent on the developer's experience and the type of application. But even if this post doesn't convince you that performance discussions are stupid without context, here are some of my own arguments:

• PHP is getting a built-in multi-threaded server. This will make it possible to bypass external servers, but is not recommended (not yet). There are also some super fast servers, like Nginx, that make the whole process of starting PHP and delegating requests to it less obvious.
• Projects such as HHVM and Appserver add powerful asynchronous and multithreading aspects to PHP, and PHP7 itself has also received some powerful upgrades in the department.
• PHP's single request application lifecycle is the biggest burden, yes, if you're looking for raw speeds; but this can also be easily circumvented, not only using similar solutions as Memcached and Craig say, but also Use Ajax and other methods. By the way - server-side JS applications are also single-requested by default. More importantly – this single request lifecycle is also an advantage because it rebuilds the application every time it is used, thus avoiding memory issues, cleaning up garbage, and keeping it streamlined and clean. When was the last time you used a JavaScript application that was stable, long-term, and memory-free on the backend or frontend?

Performance discussion is, and will always be a draw. (Unless you are using Java - then Java always loses! ;))

James:

Node is touted as the preferred runtime for high-performance, low-latency applications and has entered the code stack of several Fortune 500 companies. It has become synonymous with "fast" and "scalable" thanks to its non-blocking I/O mechanism and Google Chrome V8 engine technology. There are many stories online about how Node brings significant performance gains to companies and improves developer productivity. I'm glad to see this round Node win, but I understand it's a controversial point.

Round Ninth: Programmer's enthusiasm

The ninth round examines how much enthusiasm Craig has shown to the developers currently on PHP and Node, and in his opinion, Node easily wins.

Bruno:

Craig, you must be looking in the wrong place. The PHP community is very enthusiastic and very active. There are more than 20 large conferences every year and some amazing topics are discussed. With the emergence of HHVM and PHP7, the water stepping has ended.

Also, I would like to say that after 6 years of development, the developers of Node still haven't learned how the version number works (v0.12.5 at the time of writing), which is strange. This immature and desperate "acting safely" (oh, you used unstable things, your fault caused your company to crash), coupled with the critical but overlooked ancient error, alienating users of the entire operating system group, which will keep any serious developer away from the programming language ecosystem.

I don't like Node. My dislike is based on negative experiences and mainly revolves around npm. This may change in the future, but for now, every time I have to use Node in any way, I get filled with fear and despair. We all have our own preferences, but it is important to stay objective and choose the right tools for the job. But it is also important to admit that sometimes choosing the right tool means choosing the wrong tool first, because you don't know yet. So don't listen to Craig. Don't listen to Jim. Don't listen to me. Give it a try – see what works, find out what feels good, and then use it. Ultimately, the environment that makes you feel efficient and great is the best environment, rather than giving you a shorter load time in milliseconds.

James:

Node is very popular. Now Nodeland is innovating a lot. While enthusiasm is subjective, I'm glad Node won the round.

Round 10: Future

The tenth round examines the future of both languages, and Craig declares this round a draw, as both languages ​​seem to have bright prospects at this stage.

Bruno:

Bruno had to hurry up and write more PHP code and edit incredible PHP articles for SitePoint

James:

James is also eager to return to his beloved JavaScript channel, but he offers these farewell words:

The draw is a fair result for this round. Node is a rising star, but it will take some huge things to replace PHP.

All in all, if your only tool is a hammer, then every question looks like a nail. Node is not the perfect choice for all scenarios, and in fact, it makes sense not to use it in many cases. But, what Node is good at, it does a really good job. It’s up to you to make an informed choice and choose the best tool for your job.

---

So, now that Bruno and James have expressed their opinions, what do you have to say?

FAQs (FAQs) about PHP and Node.js

What is the main difference between PHP and Node.js in terms of performance?

PHP and Node.js have different performance characteristics due to their different underlying architectures. PHP is a synchronization language by default, which means it performs one operation at a time, waiting for each operation to complete before continuing with the next operation. This can degrade performance when handling a large number of I/O operations. Node.js, on the other hand, is built on JavaScript, which is essentially asynchronous and non-blocking. This means it can handle multiple operations simultaneously without waiting for one operation to complete before starting another, potentially improving performance, especially in applications with a large number of I/O operations.

How does PHP's learning curve compare to Node.js?

Because PHP syntax is simple and has abundant online resources, it is often considered to be easier to learn by beginners. Although Node.js is not complicated, it requires a solid grasp of JavaScript and asynchronous programming, which can be challenging for beginners. However, if you are already familiar with JavaScript, you may find Node.js easier to get started.

For real-time applications, is PHP or Node.js more suitable?

Node.js is usually better suited for real-time applications such as chat applications, collaboration tools, or multiplayer games. This is because it has an event-driven non-blocking architecture that allows it to handle multiple concurrent connections and has high throughput, which is critical for real-time applications.

How to compare PHP and Node.js in terms of scalability?

Both PHP and Node.js can be extended to support large applications, but they scale in different ways. PHP is vertically scalable, which means you can increase its capacity by adding more powerful hardware. Node.js, on the other hand, scales horizontally by adding more machines to the server pool. Node.js also has a built-in module Cluster, which allows you to leverage a multi-core system to create child processes that share server ports.

How are they different in terms of community support for PHP and Node.js?

Both PHP and Node.js have a huge and active community that contributes and supports its development. PHP has a long history and has a large number of resources, libraries and frameworks. Node.js, although new, is growing rapidly and is supported by large companies such as Google and Microsoft. Both communities are actively developing and maintaining various open source projects.

How to compare PHP and Node.js in terms of security?

Both PHP and Node.js have powerful security features, but the security of an application usually depends more on the developer's knowledge and practice than on the language itself. PHP has been around longer and has a larger user base, which means it has been exposed to more security threats and has therefore developed more security features and best practices. Node.js is relatively new, with fewer known vulnerabilities, but also fewer built-in security features.

For SEO, is PHP or Node.js better?

Both PHP and Node.js can be optimized for SEO. PHP has been used for many years to create dynamic websites that are easily indexed by search engines. Node.js, on the other hand, can be used to build fast, scalable applications that can improve user experience and website performance, both of which are important factors in SEO.

How to compare PHP and Node.js in terms of database support?

PHP supports a wide range of databases, including MySQL, PostgreSQL, and SQLite. It also supports NoSQL databases such as MongoDB through third-party libraries. On the other hand, Node.js is particularly suitable for NoSQL databases such as MongoDB due to its JSON-based data processing. It also supports relational databases through third-party modules.

For server-side rendering, is PHP or Node.js more suitable?

PHP is designed for server-side rendering and has been used for this purpose for many years. On the other hand, Node.js can also perform server-side rendering, especially when used with frameworks such as Express.js. However, Node.js is often used to build APIs and backend services, and the frontend is handled by separate technologies.

How to compare PHP and Node.js in terms of development speed?

Development speed may vary depending on the complexity of the project and the developer's familiarity with the language. PHP can achieve rapid development with its simple syntax and rich built-in functions. Node.js also enables rapid development, especially in real-time applications or services with a large number of I/O operations, thanks to its event-driven architecture and non-blocking I/O.

The above is the detailed content of PHP vs Node.js Smackdown: Right of Reply. For more information, please follow other related articles on the PHP Chinese website!