this post was submitted on 18 May 2025
19 points (100.0% liked)

PHP

385 readers
1 users here now

<?

namespace lemmy\php;

/*

Welcome to the PHP community on Lemmy

#Rules:

1: Soon(TM)

#Helpful stuff:

PHP Documentation

Composer

PHP Standards

#Common frameworks:

Symfony

Larvel

*/

echo "Welcome";

founded 2 years ago
MODERATORS
[email protected]
19
Why PHP is Still Alive? Or Why Node Can't Kill It. (tadeubento.com)
submitted 1 month ago by [email protected] to c/[email protected]
2 comments fedilink hide all child comments
 

You may hate me for this, but this is what's really going on. I love JS/TS and Node but the world is built in economies of scale not in love for programming languages... and PHP is the best when it comes to cheap scaling.

Really hope someone at Node decides to make it fast-cgi compatible in a nice way.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 2 points 1 month ago (1 children)

I write PHP professionally, so I agree with his conclusion, but this is a strange take:

Enterprise developers are usually working in large teams with DevOps support, continuous integra- tion pipelines, containerized deployments, observability, and more. In contrast, web develo- pers building small business websites, forums, blogs, or landing pages have to prioritize and opti- mize for cost and simplicity.

This is where PHP shines: the deployment model is dead simple. Write code > Deploy via FTP > You're live.

All of the things in the first quoted sentence can be and are being done with PHP. And in the enterprise, cost and simplicity are still seen as high priority.

[โ€“] [email protected] 1 points 1 month ago* (last edited 1 month ago)

All of those things done in the enterprise avoid and fix issues that are specific to the enterprise and that freelancer making websites and running WP instances usually doesn't need to worry about. While they can indeed get CI/CD and a more complex stack the advantages for them don't outweigh the costs of not having them. In the enterprise is the other way around, if you don't have those solutions the costs are much bigger.

All of the things in the first quoted sentence can be and are being done with PHP.

Yes, but for eg. the other way around can't be said. Node isn't friendly when it comes to stacking thousands of websites on the same server because you'll be required to run a single process for each website. Node isn't friendly of a non-CI/CD deployment process because while you can upload your changes using FTP you'll still to at least go into the sever and restart node for that website... or compile the code if you're using TS.