php[podcast] episodes from php[architect]

<span data-mce-type="bookmark" style="display: inline-block; width: 0px; overflow: hidden; line-height: 0;" class="mce_SELRES_start"></span><span data-mce-type="bookmark" style="display: inline-block; width: 0px; overflow: hidden; line-height: 0;" class="mce_SELRES_start"></span>

In this episode, Scott talks with Stanislav Khromov about his project bun-php, which allows PHP to be run through the Bun JavaScript runtime.

Subscribe to our magazine: https://www.phparch.com/subscribe/

This podcast is made a little better thanks to our partners.

OurCVEs

Your security posture, on autopilot with OurCVEs

CodeRabbit

Cut code review time & bugs in half instantly with CodeRabbit.

PHP Architect Consulting

Your PHP codebase deserves a partner, not a contractor

Music Provided by Epidemic Sound https://www.epidemicsound.com/

#phpc #php #communityCornerPodcast #podcast #phptek

The post Community Corner Podcast: bun-php with Stanislav Khromov appeared first on PHP Architect.

<br />

Hosts: Elizabeth Barron & Matt Stauffer

Welcome to the First Community Hour

The original concept was just a Zoom call where anyone could drop in and ask questions, but it evolved into something with a purpose and a theme. Big thanks went to the folks at PHP Architect for providing the platform and infrastructure, and to Joe Ferguson for producing behind the scenes.

Matt introduced himself and his work leading a PHP (and Laravel) consultancy that specializes in rescuing and modernizing legacy applications. He shared why he loves that space: PHP powers functional code spread across the internet doing real good for real people, which is exactly why he cares so much about the language and the Foundation.

The Blog Post That Started It All

Matt admitted he’d often found it hard, even as an experienced open-source contributor, to contribute to PHP itself. Digging into why, he found both truth and misconception. Some contributions happen in ways we don’t call “contributing to PHP” but should, and some pathways genuinely need better communication and community building.

His goal was a single canonical starting place — a short blog post that says “start here” for anyone who’s always wanted to contribute. It’s also a reminder to himself to know the current reality rather than criticizing PHP based on how it worked 15 or 20 years ago.

The Lowest Barrier to Contributing

The most important point Matt hammered home: contributing to any individual component, framework, package, or meetup is contributing to PHP. Working on WordPress, Laravel, or Symfony all counts. It does not have to be the language itself to matter.

Elizabeth agreed wholeheartedly that the definition of contribution should be broad. Every interaction, every engagement, every time someone shows up somewhere is a contribution. Newcomers are especially valuable — they can spot the gaps and holes that long-time maintainers no longer see. For those who do want to work on the language itself, Matt suggested reproducing other people’s bugs from the PHP source repo as the easiest onboarding point.

Everybody Matters in the PHP Community

Elizabeth shared that the Foundation recently started an onboarding special interest group where mentorship will be a topic, aimed at improving the overwhelming newcomer experience. They discussed the idea of a central hub or resource for contribution opportunities. Matt was cautiously supportive — worried programmers might over-engineer a tool instead of doing the work, but open to something that points people to where each community already lists its opportunities, while the Foundation creates that space specifically for the PHP language itself.

Matt shared his own contribution origin story: his first pull requests, back in September and October 2012, were to jQuery responsive-design plugins. Neither was merged, but the experience taught him that open source doesn’t need to reflect every person’s specific needs, and that most people online are genuinely kind and well-intended.

User Groups, SIGs, and Timezone Challenges

Matt debunked the perception that user groups are expensive to run. Food is usually the biggest cost — and you don’t need food at all. The most valuable thing is a host willing to donate space. He described a recent Atlanta PHP meetup with nothing but a few six-packs and some leftover pastries that worked out perfectly fine.

The conversation turned to the eternal challenge of timezones and async collaboration. Both agreed async is great for inclusivity, especially for non-native English speakers, but some things simply can’t happen asynchronously with the same quality. In-person and real-time contact build trust and relationships in ways text alone can’t, whether for a company, a user group, or the Foundation’s own special interest groups.

Designers, Docs, and Making It Easier to Contribute

On what the Foundation can do to help, Matt suggested more universally accessible, perennial resources rather than blog posts that go stale. PHP’s own “how to contribute” page is out of date and language-focused. He proposed the Foundation website host a broader contribution guide that links out to each community’s canonical resources.

He noted the reality that anything on php.net mentioning a sub-community risks drama, so the Foundation website is a better place to start, prove things out, and eventually propose polished changes to php.net. They closed by celebrating internals contributors, infrastructure heroes like Derick Rethans and Joe Ferguson, and every kind of skill — social media included — that the PHP ecosystem needs.

Looking to hire PHP developers? Email [email protected] – Joe and the team are available for consulting, infrastructure work, Ansible playbooks, and code review.

This podcast is made a little better thanks to our partners

https://www.epidemicsound.com/

Youtube Channel

Got feedback? Join us on Discord at discord.phparch.com

The post PHP Foundation Community Hour Podcast 2026.09.10 appeared first on PHP Architect.

<span data-mce-type="bookmark" style="display: inline-block; width: 0px; overflow: hidden; line-height: 0;" class="mce_SELRES_start"></span>

In this episode, Scott talks with Nia Luckey about her new book “Trust Hacked: What Firewalls, Failures, and the Frontlines Taught Me About Trust”.

Links:

Nia’s Links:

Scott’s Links:

PHP Architect Social Media:

Subscribe to our magazine: https://www.phparch.com/subscribe/

This podcast is made a little better thanks to our partners.

Put Your Technical Debt on Autopay with PHPScore

CodeRabbit – Cut code review time & bugs in half instantly with CodeRabbit.

Music Provided by Epidemic Sound https://www.epidemicsound.com/

#phpc #php #communityCornerPodcast #podcast #phptek

The post Community Corner: Trust Hacked with Nia Luckey appeared first on PHP Architect.

<br />

Hosts: Eric Van Johnson & Joe Ferguson

New Intro, New Scenes, and a Last-Second Co-Host

The pair caught up on client work: Joe pulled off an Elastic Beanstalk environment flip that nobody noticed (which is exactly how you want those to go), while Frank got thrown right under the bus for deleting the wrong database. Fortunately, it wasn’t production, and the conversation turned into an appreciation session for point-in-time recovery on AWS RDS and DigitalOcean’s managed databases, both of which have saved plenty of bacon during cowboy-hat coding sessions.

The PHP Foundation Community Podcast

Eric and Joe used the moment to clear up a common misconception: people often conflate PHP internals with the Foundation, but they are not the same thing. The Foundation pays people to work on internals rather than steering the language itself. Its whole reason for existing is to get structure and funding around an old open-source project that billion-dollar companies have built empires on while contributing little back downstream.

They also touched on recent Foundation board turnover: Roman’s term ended, and he’s rotating off, with Brent Roose joining as JetBrains’ representative — a great fit given Brent’s reach and the volume of PHP content he pushes out.

Unlocking the PHP Architect Magazine Back Catalog

Big news for existing accounts: John has opened up everything published before 2022 to anyone with an account on the system, even without an active subscription. Log in, head to magazines, and check what you now have access to. The team also reminded listeners that the magazine pays every contributor, that they’ve built a solid roster of regular columnists, and that PHP Architect is a consulting group available to augment teams, evaluate systems, and more.

Where Developers Fit in an AI World

But Joe was candid about his concerns too: AI feels force-fed in a way CSS or JS frameworks never did, with a real fear of being replaced by “a bunch of Claude agents in a trench coat.” He raised ethical and environmental concerns, pointing to accusations about his own city’s AI data center and the ripple effects on hardware — RAM prices spiking 400–500%, with Apple reportedly paying far more for iPhone RAM, a cost that always flows back to consumers.

Eric compared the AI moment to crypto: a genuinely good technology released to the masses too soon, leading to misuse and eventual regulation. He shared a concrete win, though — using Claude to single-handedly bring a Laravel project shelved since COVID up to date, then using it to generate effort estimates (roughly three years of work) that helped set realistic expectations with a client who didn’t want to hear it. The pair debated whether those estimates accounted for AI-assisted velocity and stressed the importance of guardrails — especially for juniors, since even skilled devs leave S3 buckets open and AI is dangerously confident in its word guessing.

TypePHP: Interesting, But Not for Everyone

Joe pointed out the bigger practical problem: there’s far more talk about TypePHP than actual code being written in it, and it’s clearly geared toward long-running CLI processes rather than web requests. That excludes the kind of PHP most developers actually write, and as Nuno noted in the chat, it isn’t going anywhere until it works with Laravel and the rest of the ecosystem. The hosts agreed the real value would be extracting any gains and folding them back into native PHP, à la HHVM/Hack, and noted transpiling already solves the “I want a different syntax” itch.

Joe also pushed back on the “runs everywhere” selling point, arguing that Docker and Podman containers already make PHP CLI tools trivially portable — better than PHARs ever were. Eric landed on a mature take: he wants PHP everywhere and is happy to see it evolve, but he’s come to terms with the fact that he won’t personally use every direction it grows, TypePHP included.

ElePHPants, Laracon Archives, and Free Talks

Eric also highlighted the new Laracon Archive project, which collects Laracon conference talks across regions (US, EU, Online, India) with a clean year-by-year interface — great work for anyone who tries to manage conference content. He closed by plugging phptech.tv, which hosts PHP Architect conference talks, including a batch of free talks and even a full free conference this year, with the same back-catalog-unlock model as the magazine.

Looking to hire PHP developers? Email [email protected] – Joe and the team are available for consulting, infrastructure work, Ansible playbooks, and code review.

This podcast is made a little better thanks to our partners

Displace

Infrastructure Management, Simplified

OurCVEs

Your security posture, on autopilot with OurCVEs

CodeRabbit

Cut code review time & bugs in half instantly with CodeRabbit.

PHP Architect Consulting

Your PHP codebase deserves a partner, not a contractor

https://www.epidemicsound.com/

Youtube Channel

Got feedback? Join us on Discord at discord.phparch.com

The post The PHP Podcast 2026.09.02 appeared first on PHP Architect.

<span data-mce-type="bookmark" style="display: inline-block; width: 0px; overflow: hidden; line-height: 0;" class="mce_SELRES_start"></span><span data-mce-type="bookmark" style="display: inline-block; width: 0px; overflow: hidden; line-height: 0;" class="mce_SELRES_start"></span>

In this episode, Scott talks to Ian Littman about Longhorn PHP 2026, a 2-day conference in Austin, TX, on October 15–16, 2026, at the Holiday Inn Austin Midtown.

Links:

Ian’s Links:

Scott’s Links:

PHP Architect Social Media:

Subscribe to our magazine: https://www.phparch.com/subscribe/

This podcast is made a little better thanks to our partners.

Infrastructure Management, Simplified

Put Your Technical Debt on Autopay with PHPScore

CodeRabbit – Cut code review time & bugs in half instantly with CodeRabbit.

Music Provided by Epidemic Sound https://www.epidemicsound.com/

#phpc #php #communityCornerPodcast #podcast #phptek

The post Community Corner Podcast: Longhorn PHP 2026 with Ian Littman appeared first on PHP Architect.

<br />

Hosts: Joe Ferguson, Sara Golemon & Holly Schilling

Zero-Downtime Environment Swaps in AWS

He explained that this was actually the second full rebuild of these servers in two months. The first migration got them off an aging Amazon Linux platform, and once everything was captured in CloudFormation templates and supporting scripts, swapping to an entirely new environment for an SSL certificate adjustment was suddenly no big deal.

Being able to swap whole fleets of application servers behind a CNAME or DNS record and have clients never know is, in Joe’s words, one of the coolest things about cloud computing that will never get old. It also spawned a new accidental buzzword: “infrastructure as cloud.”

3D Printing Trials, Tribulations, and Guitar-String Belts

This is Sara’s fourth printer that should have been her third — she detailed the multi-day kit assemblies, belts that had to be tightened like guitar strings before calibration would work, and a tiny plastic pulley holder that snapped apart. Apparently nobody in Lisbon has a working 3D printer to help print a replacement part, so she resorted to sanding wood into a makeshift holder before finally getting it running and printing spares of everything.

Holly admitted 3D printing is another expensive hobby she’d never follow through on, and Joe confessed he’d want the “Apple of 3D printers” that never jams — the same reason flying drones didn’t stick for him, since what he was actually doing was crashing and repairing drones. Sara later shared her first real project: little blue printed brackets that consolidate her monitor’s power and Thunderbolt into a single clean cord.

Old Tech Nostalgia: Radio Shack Kits, Punch Cards, and Hard Drive Platters

Holly recalled hacking on a third-hand 8088 laptop from a garage sale because her parents wouldn’t let her touch the family 486, and spending a full year in 1997 trying to get DHCP working across three Windows 95 machines before giving up and hard-coding IP addresses. Sara topped it with serial null-modem cables running between rooms in her first apartment, back when your serial port was your network.

Holly then held up hard-drive platters she keeps as wall decoration, prompting a genuinely fun tangent about whether you could manually write bits to a low-density platter with a needle and magnet — a “solvable problem” per Joe, complete with G-code and a printed robot housing. The group also swapped memories of building PCs when a video card was mandatory and Sound Blaster was king, plus punch cards still stacked in a university basement at the turn of the century.

Go Generic Methods, the PHPArch Archive Vault, and PHP 8.6

Eric dropped breaking news mid-show: anyone with a phparch.com account — even an old one from a lapsed subscription — now has access to the magazine archive going all the way back. Joe pulled up Volume One, Issue One, and dug up a November 2002 piece about PHP 4.3 RC2 — right around when Sara submitted her first PHP patch and gave the world unified streams.

They also covered Eric Van Johnson’s blog post on the PHP 8.6 soft feature freeze. Beta 2 shipped with a lot more deprecations landing that weren’t in beta 1, and the hosts encouraged listeners feeling froggy to grab it and test drive. Holly griped that one of her merged 8.6 changes didn’t even get a mention — thanks a lot, Eric.

TypePHP and Competing Runtimes

Holly framed it through history: the whole reason PHP, Perl, and CGI exist is to avoid the per-request cost of loading and launching a native binary, so she’s curious what tradeoffs a compiled approach makes — especially since people sensitive to raw performance often reach for Go in the first place. She also pointed out most PHP code is just reading a file, not running the billion-row challenge.

Sara pushed back on the “competing runtime” framing, recalling HHVM as more synergistic than antagonistic — it launched with PHP’s own code inside it, and PHP 7 hitting the speed of PHP 5 was directly informed by HHVM’s research. The real test will be whether TypePHP can run real Laravel apps and WordPress sites reliably enough for ecosystem adoption, the same way HHVM eventually powered Wikipedia’s front end with just a single WordPress patch.

PHP Foundation Speaker Accreditation & PHP BeNeLux Returns

The big excitement, though, was the announcement of PHP BeNeLux in Antwerp, Belgium in January 2027 — the first since January 2020 before COVID. Sara audibly lost it, partly because it lines up with FOSDEM and partly out of love for longtime organizer Michelangelo van Dam, whom Joe credited as a huge, welcoming reason he got involved in the PHP community in the first place. Both hosts are already thinking about submitting talks.

Looking to hire PHP developers? Email [email protected] – Joe and the team are available for consulting, infrastructure work, Ansible playbooks, and code review.

This podcast is made a little better thanks to our partners

Displace

Infrastructure Management, Simplified

OurCVEs

Your security posture, on autopilot with OurCVEs

CodeRabbit

Cut code review time & bugs in half instantly with CodeRabbit.

PHP Architect Consulting

Your PHP codebase deserves a partner, not a contractor

https://www.epidemicsound.com/

Youtube Channel

Got feedback? Join us on Discord at discord.phparch.com

The post The PHP Podcast 2026.08.27 appeared first on PHP Architect.

<br />

Hosts: Joe Ferguson, Sara Golemon & Holly Schilling

Shirley MacLaine, Green Room Shade, and the Show’s New Normal

Joe also lays out where the show is heading. Eric and John took over the podcast the previous week to relive their glory days, and the plan is for the old guys to step back to roughly one episode a month. Joe and Sara are working on something to fill one slot, another mystery show is in the works pending signed contracts, and Alive and Kicking is confirmed still alive and kicking after a great recent episode with Derek. Joe also plugs the PHP 8.6 Beta 1 tag and Scott Keck-Warren’s PHP Community Podcast interview with release managers Daniel Scherzer and Matteo Bacotti.

The RAM Apocalypse: 500% in Twelve Months

The ripple effects are everywhere. Console prices are going up instead of down late in their cycle, with next-gen consoles projected to start at $1,000 or more. The hobbyist single-board computer market is getting crushed — Pine64 announced they’re stepping back from making hardware, and a Raspberry Pi 5 that debuted cheap now runs over 100 pounds. Holly’s new PC, bought at the start of 2025, ended up shipped 3,000 kilometers the wrong way to California and is stuck awaiting import paperwork, leaving her leaning on a laptop and some now-precious Raspberry Pi zeros.

The nostalgia gets thick as the crew reminisces about DIP chips, EDO RAM, Pentiums, Epson 486s, Tandy 1000s, and the TRS-80. Special venom is reserved for Packard Bell (“utter freaking trash”) and Gateway 2000’s cow-pattern branding — which Sara confirms sold better in Wisconsin than anywhere, though hay bales in a Berkeley storefront still boggle the mind. A chat comment about technicians de-soldering and reballing BGA RAM chips becoming economically viable gets a hearty “absolutely.”

Memory-Aware Development and Why PHP 7 Doubled Down

Sara drops a great deep dive: a significant reason PHP 7 was roughly twice as fast as PHP 5 was changes in the memory layout. Every variable became referenced by one fewer pointer, and while eight bytes sounds trivial, every level of indirection adds time across every single instruction and access. Sara adds the CPU-level detail — one layer of indirection can be a single instruction on most architectures, but adding a second layer can push a lookup from one instruction to three.

That leads into a warm tangent about learning C to become game developers. Sara’s evergreen joke: “I’m going to be a game developer” is the programmer’s version of “I’m going to buy a bar.” Great people, brutal hours, endless competition, and the reality of hitting spacebar 400 times to figure out why you can phase through a wall. The cat-reading-the-paper “I should buy a boat” meme makes an appearance to seal it.

The GitHub Outage and the Monoculture Problem

The conversation turns to whether this is self-inflicted. Joe recalls GitHub’s pre-Microsoft, gold-standard reliability and wonders aloud how much the decline lines up with Copilot’s arrival and internal AI adoption, with uptime reportedly slipping below a single nine at points. Sara defends them somewhat — the number of actions, CPU cores, and pull requests has genuinely hockey-sticked, partly because AI has emboldened people who previously wouldn’t have opened a PR. But as Joe puts it, the call is coming from inside the house, since GitHub itself has been pushing AI.

On alternatives, Joe says the least-jarring migration for PHP Architect’s clients would be self-hosting GitLab, since GitHub Actions and GitLab runners are nearly identical in syntax — Atlassian’s Bitbucket, by contrast, is a bridge too far, mostly because the entire ecosystem assumes you’re on GitHub. Sara names this the core problem: monoculture. The crew discusses package mirrors, local caches, 12-factor thinking, and Composer’s support for custom mirrors, all while remembering the PHP repo intrusion years ago that came from an unmaintained self-hosted Git server. The takeaway: owning your pipeline end-to-end is the only way an outage can’t stop you — and Joe teases spinning up a self-hosted GitLab now that “the boss” (Sara) has signed off.

How to Contribute to PHP (and Handling Security Reports)

Other contribution paths include triaging and reviewing issues across PHP repositories — invaluable work that frees core developers from wading through AI-generated slop bug reports — and participating in internals via the well-documented mailing list process, up to and including running for release manager (8.7 managers will be needed before you know it). Sara points folks to discord.phpc.chat for the PHP Discord, with dedicated Internals and Foundation channels for anyone the mailing list intimidates.

Second, Sebastian Bergmann’s “So you received a security report. Now what?” is a jump-around reference for application developers rather than a front-to-back read, walking through roughly ten steps to triage, validate, and resolve reported issues the right way. Sara shares a real-world example from mobile: a flagged package that was only exploitable on a rooted device with an actively hostile package installed alongside it — a very different risk profile than a SQL injection on an API endpoint. Cue reminiscing about writing SQL against Access databases over ODBC from PHP (and Perl) back in the 90s, and Joe’s advice for handling any security report: don’t panic, and always know where your towel is.

Looking to hire PHP developers? Email [email protected] – Joe and the team are available for consulting, infrastructure work, Ansible playbooks, and code review.

This podcast is made a little better thanks to our partners

Displace

Infrastructure Management, Simplified

OurCVEs

Your security posture, on autopilot with OurCVEs

CodeRabbit

Cut code review time & bugs in half instantly with CodeRabbit.

PHP Architect Consulting

Your PHP codebase deserves a partner, not a contractor

https://www.epidemicsound.com/

Youtube Channel

Got feedback? Join us on Discord at discord.phparch.com

The post The PHP Podcast 2026.08.20 appeared first on PHP Architect.

<span data-mce-type="bookmark" style="display: inline-block; width: 0px; overflow: hidden; line-height: 0;" class="mce_SELRES_start"></span>

In this episode, Scott talks with Daniel Scherzer, release manager for PHP 8.5 and PHP 8.6, about the bug-fix release cycle, partial function application coming in 8.6, and his upcoming talks at Longhorn PHP on what’s new in 8.6 and building PHP extensions in Rust.

Subscribe to our magazine: https://www.phparch.com/subscribe/

This podcast is made a little better thanks to our partners.

Infrastructure Management, Simplified

Put Your Technical Debt on Autopay with PHPScore

CodeRabbit – Cut code review time & bugs in half instantly with CodeRabbit.

Music Provided by Epidemic Sound https://www.epidemicsound.com/

#phpc #php #communityCornerPodcast #podcast #jscpd

The post Community Corner Podcast: PHP 8.5 + 8.6 Release Manager Daniel Scherzer appeared first on PHP Architect.

<br />

Hosts: Eric Van Johnson & John Congdon

Stepping Back to Make Room for More Voices

Eric and John have committed to appearing at least once a month, since they have the most holistic view of what’s happening across the company. When they’re on, expect the “inside baseball” episodes — the behind-the-scenes look at what PHP Architect is up to. The rest of the time, this slot will keep going with other hosts, so the show never goes dark.

They also reminded listeners there’s both a live stream and an audio RSS feed. Some folks apparently only recently discovered the audio version, while longtime audio listeners never realize the show streams live. Either way, head to phparch.com, click on podcasts, and you’ll find every way to subscribe.

Eric’s Laracon Boston Recap

The venue was industrial and good-looking with a fantastic stage setup, but seating was a genuine problem this year. Eric arrived late to Nuno’s talk and there was nowhere to sit; the team scrambled to bring in more chairs. When it rained on day two, they ran out again. Despite that, staying in the same hotel as folks like Eric Barnes, TJ, Jake Bennett, and Michael Dorinda made for the kind of hallway-and-breakfast camaraderie he values most.

Eric also hit the social events he usually skips — he sat out dodgeball (bad knees, slip-on shoes, and being a big target), but went to the Laracon Prom, which required an RSVP and an approved request. It turned out to be way cooler than expected, with people fully decked out, DJs, and an after-party plus a VIP dinner where Laravel’s marketing team worked the room. He also caught up with folks like Matthew Weier O’Phinney of Zend/Perforce and had a chat with Taylor.

Running the Laravel Magazine Site and Taylor’s Blessing

At the after-party dinner, Eric took the opportunity to run the name past Taylor directly, since he wasn’t sure the original owner had ever gotten official approval to use the Laravel name for a magazine. Taylor’s response was essentially “that’s fine, don’t worry about it” — so Laravel Magazine lives on. Eric even set up a newsletter signup, though he admits he’s not sure yet whether he’ll actually send a newsletter.

CPX — A PHP-World npx

John pushed back a bit, pointing out that tools like PHP unit and Rector usually live in your vendor directory anyway because your CI pipeline depends on them. Eric agreed that’s a valid workflow, but framed CPX as ideal for the occasional-use tools and for lowering the barrier for people outside the PHP world who want to dip in without fully committing. Chat chimed in with Rector as a great CPX use case, and they walked through examples like spinning up a fresh Laravel app.

Laravel LSP and PHP Storm Light

He also spotted something called PHP Storm Light at the JetBrains booth: a trimmed-down, experimental build with faster startup, lower memory, and fewer features. It’s available through the Toolbox app as an EAP, so it’s free and explicitly experimental. John, who’d been hitting memory limits in regular PHP Storm, decided to install it on the spot, and Joe mentioned using it for one-off file edits — sparking a conversation about whether it fills the gap left by JetBrains’ old standalone editor.

PHP Tek CFP Extended + Ticket Options

On tickets, they’ve broken out a bundle that includes hotel nights so attendees can hand their boss a single lump-sum figure (airfare not included). There are also food-and-beverage-only tickets for partners and kids, single-day track options, and dedicated days for Laravel, JavaScript, and DevOps — one track each, with the other two tracks running the usual PHP Tek content. John flagged a possible issue with DevOps being the default CFP track, since it’s pulling in a flood of generic, seemingly AI-submitted talks he’ll need to sort through.

Looking to hire PHP developers? Email [email protected] – Eric, John, and the team are available for consulting, team augmentation, direction, code review, and even mobile development work.

This podcast is made a little better thanks to our partners

Displace

Infrastructure Management, Simplified

OurCVEs

Your security posture, on autopilot with OurCVEs

CodeRabbit

Cut code review time & bugs in half instantly with CodeRabbit.

PHP Architect Consulting

Your PHP codebase deserves a partner, not a contractor

https://www.epidemicsound.com/

Youtube Channel

Got feedback? Join us on Discord at discord.phparch.com

The post The PHP Podcast 2026.08.13 appeared first on PHP Architect.

<br />

Hosts: Joe Ferguson, Sara Golemon & Holly Schilling

Cats, Ice Cream, and Bobbleheads

The conversation spun into merchandise ideas after Eric dropped a photo of a bobblehead in the Discord. The crew riffed on 3D-printing speaker action figures and bobbleheads for the conference, with Holly getting Eric on record that it “would not be expensive” — a statement immediately screenshotted for posterity. Sara and Holly quickly reminded everyone that multicolor prints are their own painful challenge, and someone with Warhammer 40k painting patience would be required.

PHP 8.6 Beta on the Horizon

They also covered read-only property defaults (a natural follow-on to 8.4’s property hooks on interfaces), the new polling API that’s largely future-facing for threading and concurrency work, the new `clamp()` function, and a long-overdue `Duration` class. Holly repeatedly questioned why something like `clamp()` needs to be in the language at all, with Sara conceding the point but noting PHP is a “kitchen sink language” and that ship has sailed. For `Duration`, Sara made the case that it genuinely belongs in core because it’s tied to the timezone knowledge baked into the underlying date/time library.

Deprecations and the Two Populations of PHP

The `list()` deprecation came up as a sore spot: Holly would love to see it gone and never uses it in new code, while Joe worries the blast radius across legacy codebases is enormous. That led Sara to articulate the core tension: there are two very different populations of PHP users — the ones aggressively upgrading and adopting new features (the podcast’s audience), and the ones who just want to run their WordPress site without the language shifting under them. Both groups matter, and the language has to push forward without needlessly breaking the second group.

The Roadmap Debate

Sara, invoking her “lawyer’s advice” not to mention it was a recent meeting topic, pointed out the practical wrinkle: the foundation’s paid developers are largely self-directed, and no one is telling them what donors want them to build. Still, everyone agreed a shared set of goals would be valuable. Holly and Sara also gave a shout-out to the unsung, unsexy work — documentation, triage, bug fixing — that keeps the lights on, and to the foundation’s first quarterly progress report for showing what contractors are actually doing.

Longhorn PHP and Travel Logistics

The travel talk sprawled into a would-be road-trip convoy (picking up Joe in Memphis, A. Woods from New York, and even attempting to ferry Sara’s car across the ocean), plus a tangent on how absurdly expensive Amtrak is compared to flying — versus Sara’s 20-euro monthly rail pass in Portugal that covers the entire length of the country.

Don’t Be a Meat Proxy

Holly complicated it with real-world nuance: some coworkers ask questions they could’ve answered themselves, then call you rude when you give a condensed answer and keep poking at its edges. The crew acknowledged a whole gradient exists — from “let me Google that for you” territory to genuine “what’s the best way to approach X” conversations that aren’t fact lookups. Sara, self-professed AI hater, admitted the balance has shifted toward “just search it” because AIs are genuinely good at search — with plenty of deep irony noted about machines being good at reading and grokking information humans don’t want to. Bonus: Holly praised naming xAI’s bot “Grok” as genuinely clever.

Looking to hire PHP developers? Email [email protected] – Joe and the team are available for consulting, infrastructure work, Ansible playbooks, and code review.

This podcast is made a little better thanks to our partners

Displace

Infrastructure Management, Simplified

OurCVEs

Your security posture, on autopilot with OurCVEs

CodeRabbit

Cut code review time & bugs in half instantly with CodeRabbit.

PHP Architect Consulting

Your PHP codebase deserves a partner, not a contractor

https://www.epidemicsound.com/

Youtube Channel

Got feedback? Join us on Discord at discord.phparch.com

The post The PHP Podcast 2026.08.06 appeared first on PHP Architect.