> the closest someone will probably give as an explanation is a massive rambling blog post written years ago
That blog post is long, but definitely not rambling, and unlike the above quote, is done in good faith. PHP night have improved, but if it has it will likely have used that blog post as a reference.
Of 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 multiple projects in nextjs over the years, teams changed and disappeared and then someone redeploys, nothing works and there we are.
> 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.
Kinda 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.
I cannot find a decent service to tell when the outage started. (One of those services has apparently the same exact problem - same interface and error - as php.net )
The best I found: it was up three days ago; unclear when it happened within the last ~70 hours.
One 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.
I have heard a lot of praise for both laravel and php and I still reserve judgement, but since trying it out I take all the performance claims one way or another with 100% my daily recommended intake of salt.
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
PHP has its warts, but it also has uses and it is often still my go-to language when developing for web. That is, when I do not go for OpenResty (Lua) or Elixir (Phoenix). Sometimes what I really want is PHP.
Stuff 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.
That blog post is long, but definitely not rambling, and unlike the above quote, is done in good faith. PHP night have improved, but if it has it will likely have used that blog post as a reference.
reply