What's New in PHP 8.6
https://www.php.net/releases/8.6/en.phpIf the overhead can be further reduced (and people have ideas) then it could be that we only need ZTS mode anymore in the future and that can open up one avenue for PHP to get native async support similar to the existing parallel extension: https://github.com/krakjoe/parallel
More "hands-on" is the stream error handling improvements. This greatly improves the old file stream APIs to now allow throwing exceptions instead of returning false on errors:
$context = stream_context_create([
'stream' => [
'error_mode' => StreamErrorMode::Exception,
],
]);
try {
$config = file_get_contents('/etc/app/config.json', context: $context);
} catch (StreamException $e) {
// handle error
}I'd love to upgrade to 8.6 so I can use function partials!
It was a smart decision to roll it out incrementally but it did create a weird gap there for a little bit but they did do it so kudos to the team.
The PHP team announced that they're going to release a critical fix between 14:00 and 14:30 UTC today. Doesn't say whether 8.6 is affected too, but the vulnerability is probably at the top of their mind right now -- even more so than the 8.6 release.
The old approach of out-pacing adversaries though mutation rates is over, given an entire FOSS code-audit looking/fuzzing for 0-days can now be done in under a day. In retrospect, over 700 reported LPE and 280 kernel CVE were dropped in the past 3 months from "LLM". This is not going to stop anytime soon.
To be honest, its very nostalgic as kids would clown each others servers in the early days. Ultimately leading to a more robust OS for everyone. =3
So I’m not sure what you mean by “before you get excited”? This is their normal release cycle, not some new emergency patch release. Although based on recent events, I see how this could be confused.
I'd say this sounds pretty serious.
Edit: Thank you for pointing out the `prefers-reduced-motion` media feature, I did not have that enabled.
[1] https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/A...
There are mountains of evidence supporting the idea that people prefer animated UIs over static UIs going back decades. This is true even in the world of TUIs, again, going back decades. I genuinely don't understand how you can make this statement so confidently.
I started my career as a PHP developer, it was a popular language especially in web development and at web agencies, and the main reason was that it was relatively cheap to employ PHP devs.
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.
Other than that this "borrow every single feature from other languages and add it to PHP" strategy is not really a good direction IMO.
There’s different skill levels out there. But if you can sell, you can still make a living with unsophisticated code and practices.
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.
Claude knows more about php than a random php shop. Or Go, Python etc.
Your career having moved on from CMS stuff in PHP is not really a good measure for what people actually need : )
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.
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
(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?)
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.
Though, I guess I've been a PHP developer for a long time now. Professionally, since 2012 and has a hobby years before that. I refuse to stop learning/using PHP!
Yes, there are other web server languages. Yes, PHP had its issues. Yes, legacy PHP can be pretty awful (ask me how I know). But, it's not going anywhere and all the "PHP bad" comments are not helpful.
PHP (still!) rocks; I'm quite happy it's still relevant (and powers much of the internet.)
But I'm an old man who got into the language during the 3-4 migration around 2000.
Their PHP8.5 examples are written as:
var_dump(max($value, min($lower_bound, $upper_bound)));
but that should be: var_dump(max($lower_bound, min($value, $upper_bound)));
/facepalmThat is false. The bounds are [0, 100] in both examples and 0 is correctly put as the first parameter to max() in 8.5.
I get the popularity and installed-base arguments, but I shudder when I see the code.
New CVEs/RCEs? https://www.php.net/archive/2026.php#2026-11-18-1
Perl was famous for excellent native unicode support in its native string type, but the result was that you had to keep track of whether your variable was native unicode or octets, and many CPAN modules would try to transparently support both, in buggy ways. A richer system is not always an advantage.
- no RCE