Top
Best
New

Posted by netol 11 hours ago

What's New in PHP 8.6(www.php.net)
245 points | 119 comments
yabones 6 hours ago|
Appears the big scary vulnerability that was announced recently is in 8.5+, so definitely upgrade your stuff if you're on a new version... For the rest of us in "debian land" running 8.3-8.4, looks like there's nothing to worry about for now.

https://github.com/php/php-src/security/advisories/GHSA-8mjj...

https://github.com/php/php-src/security/advisories/GHSA-2fjv...

The other Critical CVE looks very very difficult to actually exploit, since it has to do with a very specific configuration during startup.

https://github.com/php/php-src/security/advisories/GHSA-gr4f...

burnte 4 hours ago||
This comment saved me an hour of searching and reading. Thank you!
lnxg33k1 2 hours ago||
Yeah but those two are not the only two

https://www.aikido.dev/blog/critical-vulnerabilities-in-php-...

https://www.aikido.dev/blog/php-security-release-19-november... ( from today)

beberlei 10 hours ago||
Most excited about the ZTS overhead reduction. If you are unfamiliar PHP can run either with or without thread safety (think using pthreads in PHP requests).

If 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
  }
jmyeet 7 hours ago||
Spawning threads in PHP is a mistake. The beauty of PHP is that a given request is single-threaded. Any IO/network bound calls allow off-thread code within that same async-await model. If you want to spawn threads, put it in an extension.
jofla_net 3 hours ago||
Amen.
gertop 4 hours ago|||
Async is about IO, you can already do that in PHP with generators.

Instead of let x = await func(); it's $x = yield from func();

Also ZTS is more about running in threaded servers like Apache worker or IIS, it's not about user threads.

beberlei 1 hour ago||
Yes you need to combine it with Fiber's API but it works, but cumbersome, especially integrating with existing libraries and things that are for the shared nothing world.

Most code in PHP would easily run in a thread, but working in Fibers requiring a complete rewrite.

calvinmorrison 9 hours ago||
That's certainly a use case but I worry async opens the door for all the non PHP to come on in
p4bl0 6 hours ago||
I'm a bit sad that there's still no way to limit the number of arguments of a user-defined function in the type system. The internal functions have that.

I know that introducing such a behavior by default could break existing code, but it seems relatively easy to introduce this feature in a backward compatible way by using the void type. For example :

    function foo (void) {}
    foo(42); // fatal error: foo() expects exactly 0 arguments, 1 given

    function bar ($a, $b, void) {}
    bar(1, 2, 3); // fatal error: bar() expects exactly 2 arguments, 3 given

    function baz ($a, $b=null, void) {}
    baz(1, 2, 3); // fatal error: baz() expects at most 2 arguments, 3 given
odder 2 hours ago||
What is their stance on breaking existing code?

I was testing some PHP ~5 code in 8.3 and there was some questionable backwards compatibility decisions. eg methods that previously returned true / false to indicate success now threw errors, same message signature and all.

krick 1 hour ago||
PHP is EXTREMELY backwards-compatible in general. All breaking changes are (i.e. were up to this point) usually introduced very gradually, first emitting Notices and Warnings and not without a very good reason.
abanana 55 minutes ago||
For a certain value of "gradually". Whether it's too fast or not comes down to opinion (and some of the changes themselves come down to a difference of opinion on how a given language feature "should" work), but it's the reason so many old sites are stuck on PHP5 - because it's not fully backwards-compatible.

A poster phrased it well on here recently¹: "in general lots of users being on unsupported releases should also cause some reflection why that is. E.g. maybe support periods are too short or there are too many breaking changes with new releases."

¹ https://news.ycombinator.com/item?id=50194270

duskwuff 2 hours ago|||
> I know that introducing such a behavior by default could break existing code

Specifically because older versions of PHP didn't have "..." arguments - variadic functions used func_get_args() to access their arguments.

Tadpole9181 2 hours ago||
Probably possible to just set up PHPStan or Mago to do this statically, no?
nticompass 7 hours ago||
I /finally/ just upgraded our PHP app from 7.4 to 8.3 (totally not just because of the PHP vulnerabilities). I can't wait to jump to 8.5, so I can use the pipe (`|>`) operator.

I'd love to upgrade to 8.6 so I can use function partials!

noir_lord 6 hours ago||
`|>` without PFA frequently ends up with longer code and isn't pretty because of the need to handle the first arg not been the one you want via closures which works but isn't really any better than just nesting them, so if I where you upgrading I'd get to 8.6 first and then start using pipes since you get both parts in that release.

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.

OkayPhysicist 1 hour ago||
It's definitely the kind of feature that you want to bake in before you start implementing user-facing functions. Elixir does this right (the first argument to a standard library function is damn near always the one you'd want to pipe in), but other languages I've seen it in are far more hit or miss.
asimovDev 6 hours ago||
a lot of stuff will require changes when jumping from 8.3 to 8.4 and above. Don't forget to use Rector[0] if you haven't already. Helped me tremendously when going 7.4 > 8.4

0 - https://getrector.com

nticompass 6 hours ago||
Rector is great! It's what I used to help migrate from PHP 7.4 to 8.3. I did still have to manually fix things and there was one spot where Rector broke the code, but I don't know what I'd've done without it.
petecooper 6 hours ago||
Source tagged:

https://github.com/php/php-src/releases/tag/php-8.6.0

ModernTimes 2 hours ago||
Got hit with the deprecated metaphone() function, but Gemini wrote me a PHP native drop-in replacement, wish me luck.
williamdclt 6 hours ago||
I can't make up my mind on FPA. On the one hand it's very elegant and I always feel like I need it when writing code, on the other hand it makes a function declaration look reaaaaally close to a function invocation, which is super confusing
jmyeet 6 hours ago|
So there are two potential problems being addressed by this.

1. The chosen example is for PHP versions. That might just be the example but this sort of thing is a real problem. Personally I prefer something like the polyfill method as seen in Javascript where possible. Python has to deal with this too since it seems like every 3.x release now makes breaking changes. That might be just be their trivial example; or

2. Closures. Looking at the linked doc that seems to be a use case. PHP suffers here (IMHO) from having a really poor type system. Having closure arguments as question marks seems... inelegant. I'd really prefer to be able to type those and also know that the variable I have itself is a callable of some kind. I always point to the Hack type system as a comparison here.

So I dislike the name "partial function arguments" because it's unclear what the purpose is. If they're closures, call them closures. If PHP's PFA's can't bind variables (I didn't look into whether they could or not, call them something else?

The word "partial" here is really what I'm having issue with. I'm reminded of partial classes from C#, which solved a problem of creating part of a class from, say, a config file. The first example I saw was WPF using XML to define UI elements where the framework compiled the XML into partial classes and you had to fill out the rest for it to compile. I guess it's a bit like declaring a header and then failing to link an implementation (in the C/C++ world).

kijin 10 hours ago||
Before you all get excited about the new version, patch the old version you're running now!

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.

TimWolla 10 hours ago||
The PHP 8.6.0 stable release will include the fixes for all applicable vulnerabilities.
Joel_Mckay 7 hours ago||
And add a few more unknown CVE, as perpetual Beta and DevOps culture does by design.

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

whoanoway 7 hours ago||
[dead]
beberlei 10 hours ago|||
There are two separate teams handling both, the Release Managers and website team do PHP 8.6 and the Security team works on the vulnerability. :)
40four 8 hours ago|||
”These releases are part of PHP’s regular four-week release cycle and will address security“

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.

bnycum 6 hours ago||
The notes say "The highest severity is CRITICAL.... Users are strongly encouraged to prepare to upgrade promptly once the releases become available. Technical details and fixed version numbers will be published alongside the releases."

I'd say this sounds pretty serious.

40four 5 hours ago||
No doubt, I’m sure they are indeed “critical”, my point is that this is part of the regular cadence of maintenance releases. Every PHP server SHOULD upgrade. But that’s no different than any other language, when a security/ maintenance release comes out, you upgrade.

The parent comment seemed to be mistaking this for another unplanned security release like we had recently for the 2 RCE vulnerabilities.

philipwhiuk 45 minutes ago||
There are critical vulns patched in the older releases at the same time.
faangguyindia 9 hours ago|||
we run serverpilot, it auto patches our php server.
PetahNZ 10 hours ago|||
Link to this?
moebrowne 9 hours ago|||
https://www.php.net/archive/2026.php#2026-11-18-1
40four 8 hours ago||
”These releases are part of PHP’s regular four-week release cycle and will address security”
r721 10 hours ago|||
https://news.ycombinator.com/item?id=50550111
1317 9 hours ago||
another one?
jmyeet 6 hours ago||
I'm honestly disappointed at the number of snark comments on HN about PHP. It's like posting 2007 memes. Yes, we all know the story of htmlspecialchars(). We can make fun of "global" when we don't realize "global" actually means "request scoped". We get it.

I've always viewed PHP as having these ideal features:

1. A stateless functional core. It's cheap to run and quick to start. Compare this to Java or even Python. There's no loading a bunch of class libraries;

2. Every request has an environment created then torn down. That means it's hard for a given request handler to leak memory or other resources. You compare this to, say, Java's servlet API (which only really existed because the startup costs were too high) where resource leaking is a real problem and then you get into GC and STW pauses; and

3. Every request is single-threaded. This is ideal. Async network/IO requests are handled via extensions. You should never need to spawn a thread in a request handler directly. You eliminate a whole class of bugs by doing this.

Is PHP perfect? No. The class separator as the backslash still offends me more than a decade later. I really wish Facebook's Hack had become PHP because it's got a vastly better type system, core collection classes (list, vec, dict) and it did things a decade ago that PHP is only added with this release (eg polling).

As for partial functions, the use case seems to be versioning? I actually prefer the Javascript polyfill method here where possible. Don't make users care about this kind of stuff.

idoubtit 5 hours ago||
My main worry with PHP is that its surface constantly grows. This means the language is

1. more complex to use (it took years for some parsers to implement the PHP 8.4 property hooks, and I suppose few people can explain how they work with inheritance and traits), 2. more costly to maintain (I remember when the developer of PHP's JIT left, the PHP foundation was worried because no one could understand the JIT code), 3. and has more security risks (critical security releases will continue).

I don't disagree with you, but the situation is more nuanced, and PHP's initial promises are now blurred.

> 1. A stateless functional core. It's cheap to run and quick to start.

Most modern codebases use a framework. And once you have to load Wordpress, Drupal, or even worse, Laravel, then it's no longer cheap and quick. So PHP added several layers of complexity to mitigate this: an opcode cache, a code-preload system...

> 2. Every request has an environment created then torn down.

That's no longer always true. When the code preload is enabled, a request can leak into another.

> 3. Every request is single-threaded. [...] Async network/IO requests are handled via extensions.

You mixing up two different things. The default PHP SAPIs have single-threaded request handlers (though IIRC the default deploy stack of Laravel differs). But the language has a native async feature through Fibers, from which coroutines can be implemented (see amphp/amp).

So PHP on the server side is usually like JS on the client side (except for workers): single-threaded with async. Though I haven't seen much use of Fibers in the wild, it's in the language.

moebrowne 5 hours ago|||
> once you have to load Wordpress, Drupal, or even worse, Laravel, then it's no longer cheap and quick

The frameworks aren't slow: https://tideways.com/profiler/blog/php-benchmarks-8.6-vs-8.5...

idoubtit 1 hour ago||
From your own source, a basic demo with Laravel peaks at 95 requests/s/core. It's worse with Wordpress at less than 20 r/s/core. That's slow.

The last round of TechEmpower web benchmarks computed the framework overhead. Depending on the task, the performance of Laravel was 5% to 20% of the native PHP code, i.e. 5 to 20 times slower. Source : https://www.techempower.com/benchmarks/#section=data-r23&tes...

ape4 4 hours ago||||
It would be nice if you could request that unused parts be disabled. Maybe in the first line of your file.
jmyeet 1 hour ago|||
> That's no longer always true. When the code preload is enabled, a request can leak into another.

That's in the same bucket (to me) as, say, L1/2/3 cache leaking between CPU threads. That's resulted in real attacks but it's not really the fault of my programming. I would rather the bug be in the language or the compiler/interpreter or even the framework because it's more likely to get found and fixed than if it was only code written by me for me.

As an aside, PHP eliminates a whole class of bugs that don't exist in, say, C/C++ eg string buffer overflows. Yes, the PHP engine can itself have buffer overflows but as per my previous point I trust the library developers and the volume of people who use and analyze it more than being totally correct with my own string handling.

> But the language has a native async feature through Fibers, from which coroutines can be implemented (see amphp/amp).

Only a single fiber runs your PHP request at any one time. This still fits the same model.

ryangittins 6 hours ago||
As they say, there are two kind of programming languages: the ones people complain about and the ones no one uses!
senfiaj 1 hour ago||
Some ancient languages have massive usage for historical reasons, but it doesn't mean we should use them for new projects. COBOL is still heavily used in US finance system, it doesn't mean it's a good choice for a greenfield financial system or enterprise application. PHP's situation is better than COBOL, but it's not the best especially for complex enterprise systems. I myself work on such system using PHP and I know what I'm talking about. Type safety kinda sucks, we heavily rely on PHPDoc annotations for complex types, still, in many places no guarantee that the returned thing will not be null, or the returned array is a normal array or a sparse array, or that array contains only integers, etc. It's really annoying. Arrays suck badly, why on earth I need some hybrid of a hash map and an array? And this is why it has so many issues. And why should this be true "0.1" == ".1" when 2 different strings are compared?
trippsydrippsy 9 hours ago|
[dead]
More comments...