What's New in PHP 8.6

(php.net)

234 points | by netol 9 hours ago

29 comments

  • yabones 4 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...

  • beberlei 9 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 6 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.
    • gertop 3 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 21 minutes 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 7 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 5 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
        • duskwuff 50 minutes 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.

          • odder 1 hour 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 8 minutes 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.
            • Tadpole9181 1 hour ago
              Probably possible to just set up PHPStan or Mago to do this statically, no?
            • nticompass 6 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 5 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 24 minutes 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 5 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 5 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.
                • ModernTimes 1 hour ago
                  Got hit with the deprecated metaphone() function, but Gemini wrote me a PHP native drop-in replacement, wish me luck.
                  • petecooper 4 hours ago
                    • williamdclt 5 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 4 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 9 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 8 hours ago
                          The PHP 8.6.0 stable release will include the fixes for all applicable vulnerabilities.
                          • Joel_Mckay 5 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

                        • beberlei 9 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 6 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 5 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 3 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.

                            • faangguyindia 8 hours ago
                              we run serverpilot, it auto patches our php server.
                              • PetahNZ 9 hours ago
                                Link to this?
                              • 1317 7 hours ago
                                another one?
                              • jmyeet 5 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 4 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 4 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 10 minutes 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...

                                    • jmyeet 19 minutes 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.

                                      • ape4 3 hours ago
                                        It would be nice if you could request that unused parts be disabled. Maybe in the first line of your file.
                                      • ryangittins 5 hours ago
                                        As they say, there are two kind of programming languages: the ones people complain about and the ones no one uses!
                                        • senfiaj 37 minutes 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?
                                      • m4rtink 6 hours ago
                                        CVEs!
                                      • trippsydrippsy 8 hours ago
                                        [dead]
                                        • vdanielpop 9 hours ago
                                          Can we not have animations that slow down my scroll on these kinds of pages? It's so pointless.

                                          Edit: Thank you for pointing out the `prefers-reduced-motion` media feature, I did not have that enabled.

                                          • PetahNZ 9 hours ago
                                            I didn't notice any animations?
                                            • TimWolla 9 hours ago
                                              The page respects the `prefers-reduced-motion` media feature [1]. You might have enabled that preference.

                                              [1] https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/A...

                                              • gregoriol 7 hours ago
                                                Designers should not design things that users want to disable
                                                • Timon3 6 hours ago
                                                  The vast majority of people prefer animations. If everything got left out that anyone wants to disable, we'd be left with `return 0`, if even that.
                                                  • mrob 6 hours ago
                                                    The vast majority of designers prefer animations. Without animations, there would be less jobs for designers. But I haven't seen any evidence that ordinary people prefer animations. Most ordinary people aren't even aware that it's possible to turn animations off, because the designers make this difficult.
                                                    • jasonlotito 6 hours ago
                                                      > But I haven't seen any evidence that ordinary people prefer animations.

                                                      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.

                                                      • simondotau 5 hours ago
                                                        Maybe if the question is “hey was that fancy animation really cool?”

                                                        Animation, used judiciously to communicate valuable information about the UX, is good. Most of the rest is only tolerable so long as it doesn’t slow anything down or change how scrolling works.

                                                        • mrob 4 hours ago
                                                          A UI should be reactive rather than proactive. Any state changes should be explicitly requested by the user, who naturally knows what they requested, making "informative" animations redundant.

                                                          However, there is one legitimate use for UI animations: making it easier for spectators to follow what's happening. Spectators aren't the ones making the requests, so they can be confused if things happen too fast. Most computer use is not done for the benefit of spectators, so animations should be disabled by default, but it's beneficial to have the option of enabling them.

                                                        • edoceo 5 hours ago
                                                          Where can I find this evidence?
                                                    • nchmy 5 hours ago
                                                      i despise most animations. Its only something that "product people" want
                                                      • Timon3 16 minutes ago
                                                        Again, the vast majority of people prefer animated UIs to non-animated ones. My own anecdotal experiences in building UIs and talking to end users over both short and long time frames supports this.
                                            • pryanshu89 7 hours ago
                                              [flagged]
                                            • tivatech 7 hours ago
                                              [flagged]
                                            • zsoltkacsandi 9 hours ago
                                              [flagged]
                                              • ExtremelyFat 8 hours ago
                                                None of those languages allow me to edit files directly via (S)FTP and see the changes go live within 2 seconds.
                                                • throw1234567891 6 hours ago
                                                  For good reasons.
                                                  • slopinthebag 8 hours ago
                                                    sure they do, i’ve implemented script-based handlers in go, rust, etc!
                                                    • phplovesong 8 hours ago
                                                      Flashback to the 90s!
                                                      • fabioborellini 8 hours ago
                                                        The real PHP way is actually ssh'ing to the server and editing with nano
                                                        • minierpthrowawa 4 hours ago
                                                          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.

                                                          • ModernTimes 49 minutes ago
                                                            Your comment will be objectionable to some, but you are living in the real-world, providing real value to customers.
                                                        • evilduck 5 hours ago
                                                          Yeah, because we all realized that's a cause of trouble and pain and is not a feature to laud.
                                                        • cutler 8 hours ago
                                                          Until another language reproduces the whole WordPress, Drupal, Magento, Moodle etc ecosystems PHP isn't going away.
                                                          • cbeach 7 hours ago
                                                            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.

                                                            • speed_spread 7 hours ago
                                                              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.
                                                              • fg137 7 hours ago
                                                                > 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.

                                                              • 6510 5 hours ago
                                                                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.
                                                            • downsplat 5 hours ago
                                                              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.
                                                              • ulimn 8 hours ago
                                                                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.
                                                                • abujazar 8 hours ago
                                                                  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 : )

                                                                  • phplovesong 8 hours ago
                                                                    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.

                                                                    • abujazar 7 hours ago
                                                                      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.
                                                                      • br0ceph 6 hours ago
                                                                        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

                                                                        • phplovesong 3 hours ago
                                                                          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?
                                                                    • Shish2k 8 hours ago
                                                                      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?)

                                                                      • mariusor 7 hours ago
                                                                        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.
                                                                      • ahofmann 8 hours ago
                                                                        What is a better direction in your opinion?
                                                                        • shevy-java 8 hours ago
                                                                          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.

                                                                          • rowanseymour 5 hours ago
                                                                            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.
                                                                            • Shish2k 2 hours ago
                                                                              What's a better language for "can easily be deployed to any random web host"?
                                                                            • stevelacey 5 hours ago
                                                                              [dead]
                                                                              • trippsydrippsy 8 hours ago
                                                                                [dead]
                                                                              • krick 16 minutes ago
                                                                                Ok, let's see what do we have in here.

                                                                                Not a huge fan of partial function application syntax. Was it really necessary when you already have short anonymous function? What does it cost you to write that explicitly? Like, 10 extra characters? It is way more readable and clear what you mean when a variable has a name, not just `?`. WTF is `?`?

                                                                                Pretty much the same for DocComments for params. Uh... why? I don't see anything wrong with the old way.

                                                                                Duration class... well, we all already had duration classes in our projects, didn't we? It looks alright, but it's a real pity operator overloading isn't a native part of the language still. Why do we still have to `->add()` instead of `+`?

                                                                                Similarly harmless but not hugely exciting are `clamp()` and `SortDirection`. The former isn't that hard to implement, but I don't think I ever did somehow, so thank you. SortDirection is literally just a built-in enum, not a huge deal. Libraries will still use their own implementations for a long time just to preserve back-compatibility.

                                                                                Polling... Well, I'd usually opt for some other language instead of using PHP like that, but sometimes you need it.

                                                                                Stream Error Handling and Readonly Defaults are great and overdue.

                                                                                All in all, doesn't look to be a terribly exciting update.

                                                                                • nticompass 6 hours ago
                                                                                  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.

                                                                                  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.

                                                                                  • DJBunnies 5 hours ago
                                                                                    Indeed, I started typing out a few replies only to delete them after remembering what you've articulated.

                                                                                    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.

                                                                                  • pwmglenn 7 hours ago
                                                                                    Partial application in PHP? WOW.
                                                                                    • shdon 7 hours ago
                                                                                      I guess the clamp function really is needed, as even in their release notes, they did the clamping using min/max incorrectly.

                                                                                      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)));
                                                                                      
                                                                                      /facepalm
                                                                                      • TimWolla 7 hours ago
                                                                                        > Their PHP8.5 examples are written as:

                                                                                        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.

                                                                                        • 6510 4 hours ago
                                                                                          I would actually write it like:

                                                                                              $value = max($value, $lower_bound);
                                                                                              $value = min($value, $upper_bound);
                                                                                              var_dump($value);
                                                                                          
                                                                                          10 years from now I can thoughtlessly scan over that without having to think what is going on.

                                                                                          This is great:

                                                                                              clamp($value, $lower_bound, $upper_bound);
                                                                                          
                                                                                          It's even more readable.

                                                                                          And since I cant stop typing... (sorry lol)

                                                                                              $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);
                                                                                          
                                                                                          In stead of:

                                                                                              var_dump( max($lower_bound,min($boxes*$bananas_per_box*trucks($ordernum)*$boxes_per_truck,$upper_bound)));
                                                                                          • tosti 2 hours ago
                                                                                            Yes. Write code like how you would do math on paper. Code should be readable without syntax highlighting. Turn it off and it's easy to tell where readability is poor.
                                                                                        • origini 9 hours ago
                                                                                          Ah yes the clamp() function good thats in
                                                                                          • AuthorizedCust 5 hours ago
                                                                                            Why is this language still around?

                                                                                            I get the popularity and installed-base arguments, but I shudder when I see the code.

                                                                                            • rarisma 7 hours ago
                                                                                              Perhaps it will contain something new that will come back to haunt us in six or so months.
                                                                                              • HackerThemAll 8 hours ago
                                                                                                > What's New in PHP 8.6

                                                                                                New CVEs/RCEs? https://www.php.net/archive/2026.php#2026-11-18-1

                                                                                                • phplovesong 8 hours ago
                                                                                                  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
                                                                                                  • downsplat 5 hours ago
                                                                                                    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.
                                                                                                    • phplovesong 3 hours ago
                                                                                                      I have heard this exact answer for decades. The mb_slop_uppercase() is not, and should not be acceptable for any modern language.
                                                                                                      • downsplat 3 hours ago
                                                                                                        It's a big world out there, it's not like you don't have a choice. I quite like the model.

                                                                                                        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.

                                                                                                    • vrubleg 7 hours ago
                                                                                                      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.
                                                                                                      • downsplat 3 hours ago
                                                                                                        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.
                                                                                                        • phplovesong 3 hours ago
                                                                                                          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.
                                                                                                          • 40four 3 hours ago
                                                                                                            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.
                                                                                                      • majestic5762 9 hours ago
                                                                                                        What's New in PHP 8.6?

                                                                                                        - no RCE

                                                                                                        • durmusk 6 hours ago
                                                                                                          Hopefully not another php2shell
                                                                                                          • skeledrew 9 hours ago
                                                                                                            [flagged]
                                                                                                            • beberlei 9 hours ago
                                                                                                              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.
                                                                                                              • skeledrew 2 hours ago
                                                                                                                Well I'm a Python person, so I'm just watching and laughing at it all. I'll be contrite if/when a big news RCE pops up for it that has people similarly scrambling. But until then... :)
                                                                                                            • shevy-java 8 hours ago
                                                                                                              [flagged]
                                                                                                              • beberlei 8 hours ago
                                                                                                                Unsure how that is a useful comment where there is literally an nginx RCE out released yesterday that allows the same thing.
                                                                                                                • michh 8 hours ago
                                                                                                                  And a Ruby RCE today. There’s been plenty of Node and Django security vulnerabilities in the past too. And simply demanding everyone rewrites everything in Rust isn’t reasonable - even in “the agentic era”.