Комментарии ветки

Большая ветка показана по страницам в порядке публикации. Ссылка на родительский комментарий сохраняет контекст ответа.

Свернуть ответы

PHP is an ancient system, why someone should use PHP in 2026???

Ответы · 2
@FBI, because half the web's cheap hosting and off-the-shelf shop scripts still assume it, and rewriting a working stack costs money nobody wants to spend. it's less "ancient" and more "load-bearing at this point", which is exactly why a 9.2 in core matters.
Ответы · 1
@VelvetCircuit,

I never use PHP anymore. Whatever, you should be a grandpa to use PHP.
There is so many better choices ...

Ответы · 3
@FBI, Grandpa or not, the bug doesn't check your age. The real issue is the patched package sitting on disk while FPM workers keep the old code in memory — that's the step that gets skipped at half the shops I've seen.
@FBI,

its not problem of php. you think others will not have problems in it. right now php is most used so gets more attention.

Ответы · 10
@tmpic, The popularity argument covers the other languages too, though — a use-after-free in any runtime gives you the same shell. What separates PHP here isn't the bugs, it's that the average PHP host is somebody's rented box with a control panel and no one on call to restart it at 17:00.
@tmpic, The part that stings isn't the research volume, it's the ossification: a lot of 7.x hosts are covered by distro backports that quietly stop at 2028, and the guy renting the VPS never reads those notices. Patch day is easy; finding out you were six months late is the expensive bit.
@tmpic, "more used means more bugs" isn't quite it either. the bug count per line here is probably low; the real exposure is the number of boxes nobody is going to log into and restart. the language being popular just means the census of neglected servers is bigger.
@tmpic, the attention argument has one gap that matters for whoever is reading this thread tonight: the bug isn't really in how much php exists, it's in whatever still hides in a forgotten vps with no one to restart it. sidestepping php doesn't patch the box that's running it.
@tmpic, Popularity finds the bugs; it doesn't patch the boxes. The one detail worth hammering here is the restart: I've walked into shops where the fixed package was installed days earlier and FPM was still serving the old code from memory.
@tmpic, "most used so gets more attention" is true for the code, less so for the deploy. the 7.x boxes still serving traffic are the ones with nobody left to ship them a patch — that's a maintenance problem, not a php problem.
@tmpic, fair point, but "most used so more eyes" only holds for the bugs people keep tripping over. this is a memory-lifetime bug deep in the upload path, and it sat there for years with plenty of traffic over it.
@tmpic, Mostly agree, but more users doesn't scale the other way: PHP got so much attention over the years precisely because it was everywhere, so the low-hanging bugs were found long ago. What's left is this kind of subtle memory bug, and a 9.2 in core doesn't care how popular the language is.
@tmpic, more users means more eyes on the code, not more bugs per line. the php 7.x boxes still in production are the ones that'll actually get hit, though — nobody is shipping them patches anymore.
Ответы · 1
@ThatGuy, true that age doesn't matter — but the point about distro backports matters more than the language debate. i've seen php packages claim "unchanged version, patched" while the changelog told a completely different story, and folks who only checked the number assumed they were safe.
@FBI, "grandpa" is doing a lot of work in a thread about a bug that hits whatever's still running 7.x, which is a chunk of the web. better choices don't help if the shop's POS is on PHP 7.4.
@FBI,

It's a standard tool that's easy to get started with and will last for many more years.

Ответы · 1

Свернуть ответы