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.<p><a href="https://github.com/php/php-src/security/advisories/GHSA-8mjj-2r7p-4hg2" rel="nofollow">https://github.com/php/php-src/security/advisories/GHSA-8mjj...</a><p><a href="https://github.com/php/php-src/security/advisories/GHSA-2fjv-p558-g82m" rel="nofollow">https://github.com/php/php-src/security/advisories/GHSA-2fjv...</a><p>The other Critical CVE looks very very difficult to actually exploit, since it has to do with a very specific configuration during startup.<p><a href="https://github.com/php/php-src/security/advisories/GHSA-gr4f-wgx5-jpfv" rel="nofollow">https://github.com/php/php-src/security/advisories/GHSA-gr4f...</a>
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).<p>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: <a href="https://github.com/krakjoe/parallel" rel="nofollow">https://github.com/krakjoe/parallel</a><p>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:<p><pre><code> $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
}</code></pre>
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.
Async is about IO, you can already do that in PHP with generators.<p>Instead of let x = await func(); it's $x = yield from func();<p>Also ZTS is more about running in threaded servers like Apache worker or IIS, it's not about user threads.
That's certainly a use case but I worry async opens the door for all the non PHP to come on in
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.<p>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 :<p><pre><code> 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</code></pre>
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.<p>I'd love to upgrade to 8.6 so I can use function partials!
`|>` 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.<p>It was a smart decision to roll it out incrementally but it did create a weird gap there for a little bit <i>but</i> they did <i>do it</i> so kudos to the team.
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<p>0 - <a href="https://getrector.com" rel="nofollow">https://getrector.com</a>
Source tagged:<p><a href="https://github.com/php/php-src/releases/tag/php-8.6.0" rel="nofollow">https://github.com/php/php-src/releases/tag/php-8.6.0</a>
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
So there are two potential problems being addressed by this.<p>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<p>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.<p>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?<p>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).
Before you all get excited about the new version, patch the old version you're running now!<p>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 PHP 8.6.0 stable release will include the fixes for all applicable vulnerabilities.
And add a few more unknown CVE, as perpetual Beta and DevOps culture does by design.<p>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.<p>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
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. :)
<i>”These releases are part of PHP’s regular four-week release cycle and will address security“</i><p>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.
we run serverpilot, it auto patches our php server.
Link to this?
<a href="https://www.php.net/archive/2026.php#2026-11-18-1" rel="nofollow">https://www.php.net/archive/2026.php#2026-11-18-1</a>
<a href="https://news.ycombinator.com/item?id=50550111">https://news.ycombinator.com/item?id=50550111</a>
another one?
CVEs!
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.<p>I've always viewed PHP as having these ideal features:<p>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;<p>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<p>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.<p>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).<p>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.
My main worry with PHP is that its surface constantly grows. This means the language is<p>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).<p>I don't disagree with you, but the situation is more nuanced, and PHP's initial promises are now blurred.<p>> 1. A stateless functional core. It's cheap to run and quick to start.<p>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...<p>> 2. Every request has an environment created then torn down.<p>That's no longer always true. When the code preload is enabled, a request can leak into another.<p>> 3. Every request is single-threaded. [...] Async network/IO requests are handled via extensions.<p>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).<p>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.
> once you have to load Wordpress, Drupal, or even worse, Laravel, then it's no longer cheap and quick<p>The frameworks aren't slow: <a href="https://tideways.com/profiler/blog/php-benchmarks-8.6-vs-8.5-8.4-and-7.4" rel="nofollow">https://tideways.com/profiler/blog/php-benchmarks-8.6-vs-8.5...</a>
It would be nice if you could request that unused parts be disabled. Maybe in the first line of your file.
As they say, there are two kind of programming languages: the ones people complain about and the ones no one uses!
[dead]
Can we not have animations that slow down my scroll on these kinds of pages? It's so pointless.<p>Edit: Thank you for pointing out the `prefers-reduced-motion` media feature, I did not have that enabled.
I know there were many "PHP is dead" posts in the past, but I think PHP now is really is declining.<p>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.<p>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.<p>Other than that this "borrow every single feature from other languages and add it to PHP" strategy is not really a good direction IMO.
None of those languages allow me to edit files directly via (S)FTP and see the changes go live within 2 seconds.
For good reasons.
sure they do, i’ve implemented script-based handlers in go, rust, etc!
Flashback to the 90s!
The real PHP way is actually ssh'ing to the server and editing with nano
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.<p>There’s different skill levels out there. But if you can sell, you can still make a living with unsophisticated code and practices.
Yeah, because we all realized that's a cause of trouble and pain and is not a feature to laud.
Until another language reproduces the whole WordPress, Drupal, Magento, Moodle etc ecosystems PHP isn't going away.
Are those ecosystems so important these days? They're mostly for human developer re-usability and ergonomics, right?<p>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).<p>Times are a-changing.
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.
> Even when they do, there's a good chance they'll guide their agent to keep using PHP because that's what they know.<p>Claude knows more about php than a random php shop. Or Go, Python etc.
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.
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.
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.
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.<p>Your career having moved on from CMS stuff in PHP is not really a good measure for what people actually need : )
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.<p>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'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:<p>(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?)
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.
What is a better direction in your opinion?
I agree with you for the most part; I think PHP went into decline several years ago already.<p>TIOBE, while useless, has a trend (there it is somewhat useful; still overall useless, but not 100% useless):<p><a href="https://www.tiobe.com/tiobe-index/php/" rel="nofollow">https://www.tiobe.com/tiobe-index/php/</a><p>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.<p>> 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.<p>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.<p>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.
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.
[dead]
[dead]
[flagged]
It powers more than half of the Internet's known websites (mostly thanks to Wordpress)
Everything works just fine<p><a href="https://phpbb.go-here.nl" rel="nofollow">https://phpbb.go-here.nl</a>
[flagged]
Gotta love all the "PHP bad" comments that appear on any PHP post (regardless of what it's about). I, for one, am I excited about this release. Modern PHP (php8+) is pretty nice and a lot of the old "PHP bad" issues from back in the day are non-existent.<p>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!<p>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.
Indeed, I started typing out a few replies only to delete them after remembering what you've articulated.<p>PHP (still!) rocks; I'm quite happy it's still relevant (and powers much of the internet.)<p>But I'm an old man who got into the language during the 3-4 migration around 2000.
Partial application in PHP? WOW.
I guess the clamp function really is needed, as even in their release notes, they did the clamping using min/max incorrectly.<p>Their PHP8.5 examples are written as:<p><pre><code> var_dump(max($value, min($lower_bound, $upper_bound)));
</code></pre>
but that should be:<p><pre><code> var_dump(max($lower_bound, min($value, $upper_bound)));
</code></pre>
/facepalm
> Their PHP8.5 examples are written as:<p>That 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 would actually write it like:<p><pre><code> $value = max($value, $lower_bound);
$value = min($value, $upper_bound);
var_dump($value);
</code></pre>
10 years from now I can thoughtlessly scan over that without having to think what is going on.<p>This is great:<p><pre><code> clamp($value, $lower_bound, $upper_bound);
</code></pre>
It's even more readable.<p>And since I cant stop typing... (sorry lol)<p><pre><code> $trucks = trucks($ordernum);
$boxes = $boxes_per_truck * $trucks;
$bananas = $bananas_per_box*$boxes;
$bananas = max($bananas, $lower_bound);
$bananas = min($bananas, $upper_bound);
var_dump($bananas);
</code></pre>
In stead of:<p><pre><code> var_dump( max($lower_bound,min($boxes*$bananas_per_box*trucks($ordernum)*$boxes_per_truck,$upper_bound)));</code></pre>
Ah yes the clamp() function good thats in
Why is this language still around?<p>I get the popularity and installed-base arguments, but I shudder when I see the code.
Perhaps it will contain something new that will come back to haunt us in six or so months.
> What's New in PHP 8.6<p>New CVEs/RCEs? <a href="https://www.php.net/archive/2026.php#2026-11-18-1" rel="nofollow">https://www.php.net/archive/2026.php#2026-11-18-1</a>
Still no builtin unicode support? What the hell is this? A web language that does not default to unicode, thats pretty weak for a language in 2026
The php convention is that strings are bytes, but we store utf8 in them. Convert or validate at ingestion, transform using the mb_* family of functions, and be happy.
The idea of UTF-16 strings in PHP 6 were a mistake. UTF-8 works in PHP just fine. New languages (e.g. Rust, Go, Swift) stick to UTF-8. UTF-16 is legacy that would be nice to get rid of where it's used (Java, C#, JS, WinAPI), but that is impossible because of backwards compatibility.
Hindsight is 20/20, it's easy now to say that if Unicode had been utf8 from the start, no 16-bit encoding would have been needed anywhere. But someone had to think of it first, and in the real world, 16-bit came first and became quite entrenched.
PHP6 was such a huge lol overall. The core devs seem so far gone its crazy. I see the odd php apologist every now and then, but luckily PHP use has been on the decline for the last decade and a half.
Obviously PHP 6 was a huge “lol”, they abandoned the version number completely. I didn’t start working with PHP until v7 so I missed all of that, but what does any of that have to do with v8.6? Seems like you just want to resurrect ancient buried arguments nobody is worried about anymore.
Don't forget the new vulnerabilities that AI will find :).
You say this and there are nginx, Java and Ruby RCE vulnerabilities in the news this week, so I am unsure you are winning points with the 1990s trope that PHP is more insecure than other projects or languages.
What's New in PHP 8.6?<p>- no RCE
Hopefully not another php2shell
[flagged]