this post was submitted on 22 Oct 2026
740 points (96.8% liked)
Programmer Humor
33823 readers
1273 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
- If the mod doesn't find it funny, you're banned. Ha-ha!... For real: do not use the community for "statements". There are other places for such content. Keep it chill and funny.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
If its so antiquated why is it still used? For a lot of things its perfectly fine. Even this vulnerability is just a case of run the update command for your package manager.
It's still used because momentum is a powerful factor. That doesn't make PHP better, but it can make it a more expedient choice.
PHP is a preprocessor that grew too big for its britches. It's a monolithic monster that runs only one thread per request in an interpreter. It works well enough if you need to manage the data of an internet forum, but it becomes increasingly unsuitable as the task's complexity grows. If you need threading or background tasks, or if scalability is important, PHP is not it; just read any number of Nextcloud vs OpenCloud comparisons.
"one thread per request" , "interpreter"
(Looks confusingly) That's JS and Python as well
PS: being obtuse on purpose, but PHP lends itself well to typical requirements of web hosting and you can always call out to a diff process if needed
Fair, but a lot of sites don't need anything more complex than an internet forum, often less than even that.