PHP 8.6 Enters Beta: A New Era of Cleanup and Modernization

Host: Hey everyone, welcome back to Allur. I’m your host, Alex Chan, and today we are talking about something that is honestly a little bit of a "spring cleaning" moment for the tech world, specifically for the PHP community. Now, I know what some of you might be thinking—"PHP? Again?"—but trust me, this one is a big deal. Host: I am so thrilled to have Marco Rossi on the show today. Marco is a veteran backend architect and a frequent contributor to various open-source PHP packages you probably use every day. He’s been following the internal RFCs for 8.6 since they were just ideas on a mailing list. Marco, welcome to Allur! It’s great to have you here. Guest: Thanks so much for having me, Alex! It’s an exciting time to be talking about PHP. I feel like we’re finally seeing the language shed its "old skin," if that makes sense. Host: It totally does! And honestly, when I saw the announcement for 8.6 Beta 1, the first thing that jumped out at me wasn't a new feature, but the word "Deprecation." Like, a lot of them. Over 30? That feels… aggressive, doesn’t it? Guest: It really does! But, honestly, it’s a necessary kind of aggression. For years, PHP has been this language that prides itself on backwards compatibility—which is great for business stability—but it also means we’ve been carrying around these weird, inconsistent functions from the late 90s. Host: I can already hear the collective sigh of developers looking at their error logs! But, realistically, why is this cleanup so important for the ecosystem? Is it just about making the manual look cleaner, or is there a performance side to this? Guest: It’s both, actually. From a performance side, every legacy edge case the engine has to support adds a tiny bit of overhead. But more importantly, it’s about "cognitive load." When you have three different ways to do the same thing, and two of them are "bad practice" but still work, it’s confusing for new developers. By pruning the core, we’re making the language more predictable. It’s about building a leaner, more developer-friendly core that actually follows modern standards. Host: That makes a lot of sense. It’s like clearing out a cluttered garage so you can actually find your tools. Speaking of new tools, I want to talk about some of the additions that *did* make it in. I saw the new `Duration` class. Finally! I feel like I’ve spent half my career fighting with `DateInterval` or just passing around integers representing seconds. What’s the "aha!" moment with the `Duration` class for you? Guest: Oh, man, the `Duration` class is a game-changer for clarity. So, here’s the struggle: `DateInterval` is great, but it’s relative. It represents the difference between two points in time, which can vary depending on things like leap years or daylight savings. Host: And it’s much harder to mess up, right? I can’t tell you how many times I’ve seen bugs because someone thought a value was in seconds but it was actually in milliseconds. Guest: Exactly! It’s those "subtle" bugs that keep you up until 2 AM. This class helps eliminate that ambiguity. Host: Another one that caught my eye—and it seems simple but I think it’s going to be used everywhere—is the `SortDirection` enum. We’re finally moving away from "magic strings" for sorting? Guest: Yes! Hallelujah, right? Think about how many times you’ve written a repository method where you pass `'ASC'` or `'DESC'` as a string. Maybe you accidentally type `'ascending'` or you forget if it should be lowercase or uppercase. Host: It’s interesting because, looking at both `Duration` and `SortDirection`, it feels like PHP is really trying to align itself with languages like Swift or Go, where the core APIs are very intentional and typed. Is that the vibe you’re getting from the core team? Guest: Definitely. PHP isn’t the "wild west" scripting language it used to be. It’s becoming a first-class language for serious, long-term enterprise architecture. The move toward native enums and standardized classes for common concepts like "direction" or "time" shows that the core team is thinking about the developer experience over the next decade, not just the next six months. Host: So, let’s talk practicalities. 8.6 is in Beta 1. If I’m a lead dev at a startup or a solo dev with a few projects, what should I be doing *right now*? Do I need to panic about my 30+ deprecations? Guest: No need to panic, but definitely start testing. The biggest mistake people make is waiting for the stable release in November or December to even look at it. Host: That’s a great tip. I’ve definitely been that person trying to fix 50 deprecation warnings on a Friday afternoon before a launch. It’s not fun. Um, are there any specific "gotchas" you’ve noticed in the beta so far? Anything that made you go, "Oh, I didn’t expect that"? Guest: Actually, yeah. Some of the changes to how certain internal functions handle nulls are getting stricter. PHP has been moving away from "silently converting null to an empty string" for a while, and 8.6 pushes that further. It’s great for code quality, but it can catch you off guard if your database allows nulls and your PHP code isn’t explicitly checking for them before passing them to core functions. Host: Oh, that’s a big one. The "null-to-string" ghost is finally being laid to rest. Guest: Exactly. It’s a good ghost to get rid of, but it’ll haunt you if you’re not looking for it! Host: Well, Marco, this has been incredibly insightful. Before we wrap up, if you had to give one reason why people should be excited about 8.6—despite all the cleanup work—what would it be? Guest: I think it’s the sense of momentum. PHP 8.6 feels like the language is finally confident enough to say, "We know what we want to be." We’re not just adding features for the sake of it; we’re refining the craft. It makes writing PHP feel… modern. It feels like we’re building on a very solid, very clean foundation for whatever PHP 9 ends up being. Host: I love that. "Refining the craft." That’s a perfect note to end on. Marco, thank you so much for joining me today and sharing your expertise. Where can people find you if they want to follow your work or see what you’re building? Guest: You can find me on GitHub at @mrossi-dev or on X at the same handle. I’m always posting about PHP internals and whatever Laravel package I’m currently breaking! Host: (Laughs) Awesome. Thanks again, Marco!