The PHP Podcast 2026.07.09

🎙️ PHP Podcast – July 9, 2026

Hosts: Eric Van Johnson & John Congdon | Guest: Holly Schilling

A PHP RFC for extension methods that PHP definitely should have had by now.

👋 Holly Schilling, Uninvited but Welcome
Holly was originally just planning to heckle from the Discord chat room. She had about 45 minutes’ notice before the show that she’d be on camera instead, which she took in stride — minus the PHP swag shirt she would have worn if she’d known. Eric is happy to hand her the show; she’s been in the backstage feed and notes that the zero-latency view means she actually gets the jokes, unlike the 3–5 second delay that makes jokes land after everyone’s moved on.

📋 PHP Tek 2027 CFP: Now Open
The call for papers for PHP Tek 2027 is open, and the deadline is end of August. This year, PHP Tek is doing three tracks: two traditional PHP-focused tracks and a third rotating track that will change each day — one day dedicated to AI talks, one to Laravel talks, one to DevOps talks. The goal is to get submissions in and the schedule published early enough that attendees can put it in their budget before their fiscal year closes. Holly (who now manages the submission review) has a note for repeat submitters: if your talk was accepted and given at a previous PHP Tek, don’t submit it again. Also: bot submissions from automated systems that spam every CFP in SessionEyes are a real problem, and Holly’s job is to filter them out before the blind evaluation round begins. The evaluation process is designed to keep Eric and John out of the loop until after the first pass — so they can’t accidentally influence votes for speakers they already like.

🏨 PHP Tek 2027 Hotel + Conference Bundle
Brief reprise from last week: the hotel and conference bundle is available at phptek.io — one price that includes your conference pass, hotel nights, and conference lunches and breakfasts, designed to make the ask to a manager or CFO as simple as possible. Eric is working on a short video to explain it rather than just dumping pricing on the homepage.

🎤 Joe Ferguson at Merge PHP — Today
Joe Ferguson — PHP Architect team member and co-release manager of PHP 8.6 — is presenting at Merge PHP immediately after this podcast wraps. His talk: “Ansible for PHP Developers: Configure, Deploy, and Update Your Infrastructure.” Eric was trying to reach Joe for an hour before the show (Joe was apparently already in the Merge PHP stream watching the podcast). If you’re listening after the fact, the recording may be available.

🔩 Holly’s RFC: Class Extension Methods
Holly has spent the past week doing a caffeine-fueled deep dive into PHP internals C code and has come out the other side with a draft RFC and working proof-of-concept code for class extension methods — a feature she kept assuming PHP had, tried to write, and found didn’t exist. The idea: you can add methods to an existing class without subclassing it. Swift has this, Kotlin has it, C# has it. The canonical PHP example is something like adding isWeekday() or isWeekend() to DateTimeImmutable — you get to call it as an instance method on the native class, not on a subclass you’d have to propagate everywhere. Under the hood it’s syntactic sugar: the implementation in C# is a static method with the class passed as the first parameter, and Holly is taking a similar approach. No performance penalty — a few people have already tested it. Early concern about performance impact has not materialized.

The feature naturally extends to scalar methods, which Laracon’s Levi Koop and others have discussed: the ability to write $str->length() instead of strlen($str). This part is harder because $this in PHP must always be an object, so scalars need special hooks to work as receivers. That complexity is why Holly broke the implementation into three phases. She has posted GitHub Gists rather than a formal PHP wiki RFC so far — she submitted for a wiki account yesterday and is waiting to hear back. Outlook has been eating her PHP internals mailing list emails (treating new posters as spam), so she’s in the process of switching to a new email address. Joe Ferguson is in the chat offering to help expedite the wiki account. Feedback is coming in, changes are being made, and this is moving toward a formal RFC.

Holly’s motivation is pure: she built this for herself because she needed it. Eric quoted himself from the “PHP Ugly Days” era, telling the community that if there’s a feature you want and nobody’s building it, it’s on you. Holly has resented and credited that line in equal measure ever since.

🏗️ NativePHP Mobile: Holly Is Building the Longhorn App
Holly has started building a conference app for Longhorn PHP using NativePHP Mobile. Eric’s reaction ranges between excitement (someone’s doing it!) and mild betrayal (it’s not for PHP Tek). Holly also submitted a talk to Longhorn PHP about what actually distinguishes a real native mobile app from a website wrapped in an app shell — and the answer isn’t the language, the transitions, or the scroll animations. It’s state management. Native apps treat the local device copy as authoritative or at minimum authoritative enough that you’re not reaching the server for every interaction. Web apps don’t do this; native apps have to. Holly has real-world context here: one of her earlier jobs was building the Chicago Sun-Times native app and then white-labeling it for 70+ publications across the country. She says she’d never do that again. Every single publication has brand style guidelines, logo clearance zones, and color adjacency rules. Multiply that by 70 and you start to understand why white-labeling at scale is a nightmare.

📅 Longhorn PHP CFP — Closes Tomorrow
The call for papers for Longhorn PHP is open through tomorrow night (July 10). It had been briefly reported as closed last week; it got extended. If you want to speak at Longhorn, head to cfp.longhornphp.com now. The conference is in Austin at the Holiday Inn.

🖥️ WordPress: Stewardship, Backward Compatibility, and the Laravel Fork Question
Holly’s experience white-labeling apps prompted a broader conversation about WordPress — specifically a genuine acknowledgment of how technically impressive it is that a WordPress installation can look completely different from any other, at the scale WordPress operates. Eric respects the technical accomplishment but has longstanding criticism of how WordPress positioned itself in relation to the PHP community. His view: WordPress was the Laravel of its day, arguably the thing that kept PHP relevant for a decade. But rather than leaning into the broader PHP ecosystem and pushing the language forward from the inside — the way Facebook tried to (even if it eventually forked into HHVM/Hack) — WordPress was laser-focused on backwards compatibility. The result was that PHP internals couldn’t move as fast as it might have because WordPress’s enormous install base created a de facto veto on any change that would have required sites to update. Holly pushed back gently: WordPress’s backwards compatibility constraint wasn’t really a choice they could have made differently given the scale of self-hosted installs and third-party plugins. Eric acknowledges the constraint while still wishing they’d engaged more with internals. The Hack language comes up as a counterpoint: HHVM/Hack, whatever its ultimate fate, was the provocation that woke up PHP internals. PHP 7’s massive performance improvements and modern type system features largely came out of internals saying “Hack has a point, let’s do this properly.” Almost every good idea from Hack eventually got ported into PHP. Eric’s darker hypothetical: if Laravel today had an existential need for a PHP feature that internals kept rejecting, and Taylor Otwell forked PHP — that could be a genuine death blow to the ecosystem. Holly thinks the community would survive; Eric thinks the math on maintaining a language fork is nastier than it looks.

📦 Composer, Supply Chain Security, and the 48-Hour Question
A viewer asked whether Composer has a way to skip packages released in the last 48 hours when running an update — the motivation being supply chain attacks, where a compromised package gets published and immediately picked up by the next composer update run. Eric’s short answer: not natively, and the real mitigation is to not run composer update blindly. Holly points out the harder version of this problem: languages like Swift allow pre-compiled binary packages, which are far scarier than source packages because you can’t even do a code review. Eric mentions that Packagist and Composer have been doing real work on supply chain integrity (covered on the show a few weeks back). If you want the deeper treatment, Eric Mann’s upcoming Security Corner column in the July issue of PHP Architect covers exactly this — Composer and the PHP supply chain. Look for it in the next few weeks.

🔄 Eric’s Laptop Saga, Chapter N
The new “clean install” MacBook Pro that Eric has been using to solve his connectivity issues dropped partway through the show. Eric switched to his older laptop (which was still running and still connected), but couldn’t get his camera to re-appear in the stream source list, couldn’t add himself back, and eventually gave up and wrapped up audio-only. John and Holly carried the last few minutes. The older laptop that never dropped is now, apparently, the better one. Eric is running out of explanations and considering a career in farming.

Links from the show:

Host:

Eric Van Johnson

John Congdon

Guest:

Holly Schilling

PHP internals contributor; author of the Surfaces RFC and now Class Extensions RFC
Primary mobile developer; built the PHP Tek 2026 conference app; building the Longhorn PHP app in NativePHP Mobile
Based near Chicago, IL

Streams:

- Youtube Channel
- Twitch

📬 Connect & Hire

Looking to hire PHP developers? Email support@phparch.com – Joe and the team are available for consulting, infrastructure work, Ansible playbooks, and code review.

Partner

This podcast is made a little better thanks to our partners

Displace

Infrastructure Management, Simplified
Automate Kubernetes deployments across any cloud provider or bare metal with a single command. Deploy, manage, and scale your infrastructure with ease.
https://displace.tech/

OurCVEs