upvote
None of those languages allow me to edit files directly via (S)FTP and see the changes go live within 2 seconds.
reply
For good reasons.
reply
sure they do, i’ve implemented script-based handlers in go, rust, etc!
reply
Flashback to the 90s!
reply
The real PHP way is actually ssh'ing to the server and editing with nano
reply
I have a small saas for construction companies. I run it on shared hosting with Cpanel. I have logged into namecheap, opened cpanel, gone to file browser, opened a php file via the file browser text editor, and fixed bugs in front of customers live. Only once did I forget to implement that same change on my actual official copy on my office computer.

There’s different skill levels out there. But if you can sell, you can still make a living with unsophisticated code and practices.

reply
Your comment will be objectionable to some, but you are living in the real-world, providing real value to customers.
reply
Yeah, because we all realized that's a cause of trouble and pain and is not a feature to laud.
reply
Until another language reproduces the whole WordPress, Drupal, Magento, Moodle etc ecosystems PHP isn't going away.
reply
Are those ecosystems so important these days? They're mostly for human developer re-usability and ergonomics, right?

When I asked Claude to create a simple online shop the other day, I suggested it use an open source shop framework. Claude explained that Stripe does most of the heavy lifting, and implementing the shop site would be simpler if bespoke. So I let it do that and the result was fantastic. And also highly customisable (with Claude).

Times are a-changing.

reply
There are a LOT of PHP shops and they aren't going to rewrite working sites tomorrow. Even when they do, there's a good chance they'll guide their agent to keep using PHP because that's what they know. It's simple tech for simple use cases, human knowledge is still an important factor if you still value understanding what you're putting out.
reply
> Even when they do, there's a good chance they'll guide their agent to keep using PHP because that's what they know.

Claude knows more about php than a random php shop. Or Go, Python etc.

reply
I never use it but my php hosting provider has this wall of icons for one click install. No developer needed on that layer. LLM has the same disadvantages as writing it yourself or the hosting provider writing something themselves. It might have more features, make a better fit and be more flexible, it isn't [say] wordpress.
reply
It has some historical warts but it's still a perfectly decent language with lots of modern features too. I quite like the semi-typed style, strong types for function arguments and returns, and duck typed within. Keeps things concise and well-checked enough. I just finished porting a 120kLoC project into php, and I'm quite happy with it. Using Slim as a micro framework, with a custom layer on top.
reply
I see where you're coming from and I agree to some extent, but having a language (or standard library) rich in features also means we don't have to rely on third party solutions that much. I think this is a pretty good thing/approach - as long as it's well tested of course.
reply
Obviously Go and Rust are more modern and performant languages, but they simply can't compete with the versatility of PHP and its ecosystem for a lot of use cases. Many web applications need a large part of the built-in functionality of PHP and one of its frameworks (Laravel or Symfony) in a tightly integrated application. Implementing one part at a time in Go or Rust is a viable option now for some, but far from all use cases. Time is better spent using that same LLM to use Laravel to its fullest.

Your career having moved on from CMS stuff in PHP is not really a good measure for what people actually need : )

reply
To be honest, the PHP "ecosystem" is on par, or even worse than npm (javascript) is. I rarely see as low quality code as i have seen in php, 90-95% of composer packages are just horrible, and most would never pass our QA.

There is a handfull of "ok i guess we can use this" packages, but they also tend to be slow and java-esque horrible class based needles abstarctions all the way down.

reply
I don't think the availability of low quality packages is an argument against either ecosystem. What counts is the availability of high quality packages like the PHP-FIG ones as well as Symfony components and the Laravel framework.
reply
im not very familiar with web dev, but from what ive seen, most web dev packages are total poo.

i feel like this is due to being a get (rich) web scheme. promising quick development so that the business can startup quickly.

anyone else feel the same?

also thoughts on a minimal php subset just for basic interactivity, so that ur not running such a complex environment with so many security avenues

reply
Laravel? Is that the pinnacle of PHP? Its abstractions upon abstractions with LOTS of lipstick. Thats why a vanilla Laravel hello world app gives you something ridiculous like 600 req/seq thruput. How is this even on the table?
reply
I've been maintaining (/suffering) a PHP project for ~25 years, which started with PHP because it was the most universally deployable runtime available on bargain-basement web hosts, where a novice user can upload a file over FTP and immediately have a running webapp. Has any other language even attempted to fill that niche yet? D:

(Has the world bifurcated into "point & click configuration of proprietary web hosting like squarespace" for simple sites and "full kubernetes deployments" for more technical things, and nobody cares about entry-level deployment any more?)

reply
I think the static site generators with static hosting have become that. When there's interactivity needed, for most purposes, you can today defer to client side logic, so there's no real need for a backend in 90% of the cases.
reply
What is a better direction in your opinion?
reply
I agree with you for the most part; I think PHP went into decline several years ago already.

TIOBE, while useless, has a trend (there it is somewhat useful; still overall useless, but not 100% useless):

https://www.tiobe.com/tiobe-index/php/

It shows two big hits, one in 2010, one in 2014. I myself switched to ruby in 2005. Ruby is now in a similar situation too. PHP is at rank #12, so that is still decent. I think it is declining only slowly though.

> Now with LLMs it is similarly cheap (if not cheaper) to write code in Go, Rust, or any performant languages that are much more sophisticated than PHP and have many other benefits. I don't see any reason anymore to start any new project in PHP.

Well, the problem with LLMs is that these users will become dependent on e. g. Anthropic, and Anthropic already showed it will censor at will, e. g. "you are not allowed to 3d print anything that looks like a gun" agenda.

I do not think LLMs are what killed PHP or will kill it. The language is simply poorly designed. Not all projects will become LLM though, this is the part I disagree with you. For instance wikipedia will not suddenly be rewritten in LLM-Rust.

reply
You're getting downvoted to oblivion but honestly I agree, I think the only reason anyone has for starting a new project in PHP in 2026 is familiarity. You cannot claim to be picking the best language for the job.
reply
What's a better language for "can easily be deployed to any random web host"?
reply
[dead]
reply
[dead]
reply