The meme stacks you see every week on HN will come and go, but PHP will stay.
PHP Is Legacy, in 2024
11–20 of 26 posts
Re: PHP Is Legacy, in 2024
#12Kinda ironic that because of this post I went to check out php.net for the first time in like a decade, and it turns out the site is down. Doesn't exactly instill confidence that the project is alive and well.
and it's still down.
Re: PHP Is Legacy, in 2024
#13Kinda ironic that because of this post I went to check out php.net for the first time in like a decade, and it turns out the site is down. Doesn't exactly instill confidence that the project is alive and well.
maybe they are updating their php to 8.4
Re: PHP Is Legacy, in 2024
#14Stuff becomes legacy not because of the language, but because of outdated libraries or frameworks or unavailable/uninterested developers. For me PHP is legacy, because I refused to work on PHP codebases, except I find someone who's willing to do the job for me.
Re: PHP Is Legacy, in 2024
#15Of course it is not. I see more clients moving back to it or moving to it for the first time. People, rightfully so imho, are starting to hate nextjs (and react is getting a bit of that). It is so much easier to get something running without errors in the logs, for years at a time, and without weird frontend bugs with laravel than it is with nextjs/react. And people are starting to see that; usually after having mult…
> get something running without errors in the logs, for years at a time
This is something you only begin to appreciate if you've been through a couple of economic recessions. Not everybody has money and manpower to keep their website up to date every other month! A well-built app for a typical business should be able to coast along through the lifetime of, say, an Ubuntu LTS release without much effort.
Re: PHP Is Legacy, in 2024
#16One thing PHP got right is its 'PHP must die' mode of operation where every request spawns a new process (ok, not a process anymore but still an isolated execution environment that lasts until the response is served.
Java, Ruby, C#, etc are application servers and this massively complicates everything.
Re: PHP Is Legacy, in 2024
#17I guess the people who flagged the post have read just its title.
Re: PHP Is Legacy, in 2024
#18Should you re-submit it, put the original title within the quotes for "read interpreting, not literally" rhetoric,
"PHP is Legacy, in 2024"
This is an exception that calls to be editorialized. The original title is as-if a quote, which the original writers omitted to mark as such.
Re: PHP Is Legacy, in 2024
#19One thing PHP got right is its 'PHP must die' mode of operation where every request spawns a new process (ok, not a process anymore but still an isolated execution environment that lasts until the response is served. Java, Ruby, C#, etc are application servers and this massively complicates everything.
The one-process-per-request model, even with php-fpm and other optimisations, it’s incredibly expensive to scale.
Modern java on a recent jvm (>=17) is incredibly scalable in comparison.
Re: PHP Is Legacy, in 2024
#20One thing PHP got right is its 'PHP must die' mode of operation where every request spawns a new process (ok, not a process anymore but still an isolated execution environment that lasts until the response is served. Java, Ruby, C#, etc are application servers and this massively complicates everything.
Maybe I was holding it wrong but I found a new Laravel project out of the box takes notable time to respond to hello world HTTP requests, and to me it looks like all the time is spent loading code on each request