
Sign up to save your podcasts
Or


<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.
<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 Andrey Kucherenko, creator of jscpd, about why copy-pasted code is an anti-pattern, how jscpd detects duplicate code across dozens of languages, and how the tool has evolved to work inside agentic coding workflows.
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: JSCPD with Andrey Kucherenko appeared first on PHP Architect.
<br />
Hosts: Chris Miller (standing in solo while Mike is on holiday)
From University Websites to Committing to PHP
His very first accepted contribution came from a practical need: everyone wanted centered Shockwave Flash films on their pages, back before CSS even existed. Centering meant knowing the width of a file, and while getimagesize() already existed (and still works today), it didn’t understand Flash. Derick added that support.
From there he fell into bug triage, spending several years working through the issue tracker alongside Jani Taskinen (whose “Sniper” name still shows up in commit logs). For a long time it was just the two of them reproducing and fixing bugs — an important task that gets neglected easily, which is exactly how backlogs of a thousand issues and pull requests build up.
The Eternal Problem of Date and Time
The core philosophical question is “what does adding a month even mean?” If it’s January 31st and you add a month, PHP historically just bumps the month number, producing February 31st, which overflows to March 2nd or 3rd. But most people who add a month really just want the next month and don’t care about day counts — so “next month” is conceptually distinct from “add a month.” Derick has been brainstorming better interfaces so people can’t make these mistakes, though it’s a lot of work.
They touch on Carbon as a unified interface people understand, but agree that making Carbon the language standard isn’t the right move. At the language level you need something that works for everybody and ideally doesn’t break existing code.
What’s Coming in PHP 8.6
Another highlight is partial function application. With the pipe operator from 8.5, piping into anything that takes more than one argument meant wrapping it in a closure (and extra parentheses because of how the parser works). Partials let you pre-fill some arguments so the resulting callable accepts just one — perfect for pipelines.
There’s also TLS session resumption support for streams, which lets OpenSSL shortcut the expensive session setup on repeated TLS connections. Bigger stream-layer work by Jakub Zelenka of the PHP Foundation is underway too, but that’s a huge job on old code and won’t make 8.6 — Chris and Derick both note the pain of keeping a year-and-a-half-long project in sync with the master branch.
Xdebug in 8.6 and the Xdebug Cloud
Derick also has a new code-coverage implementation that gives better, more correct results at roughly a 10% speed cost. He’d rather ship correct output than fast output — and points out that PHPCov may be quicker but skips path and branch coverage entirely. The pair discuss how branch coverage doubles your test count at every branching point, and how Xdebug has a hard limit (around 64K) to avoid running out of memory on pathological code.
Finally, Chris asks about Xdebug Cloud — a paid service that enables debugging where networking otherwise wouldn’t, such as remote teams sharing a single development machine (an SSH tunnel only lets one person listen on the debug port). It’s £15/month or £150/year for an individual, priced similarly to Packagist’s private packages, and helps fund Derick’s ongoing Xdebug work. He plans to do more marketing about it this year.
Deprecations, Consensus, and Two-Thirds Votes
The list() deprecation is another sore point — Chris uses it, and the vote is tied 21–21 with one abstention, so it won’t pass under the two-thirds rule. Derick reminds everyone that “yes” needs to be twice “no.” Returning from a finally block is another candidate that makes little sense to use but hurts nothing to keep.
Chris and Derick reflect on how voting was originally meant to confirm consensus reached on the mailing list, not to be the decision itself. A 50%+1 result isn’t consensus; two-thirds is the compromise, even if true 75–80% agreement would be ideal. Joe notes many deprecations are groundwork to reserve keywords for future RFCs — which raises the perennial question of how you measure real-world usage across Composer’s dependency chains.
Infrastructure, the Website, and the Next Generation
On the website side, everything currently lives in a single root directory of 1999-vintage code, and there’s a long-pending patch to restructure it. The PHP Foundation’s ambassadors program — with speaking, marketing, and research streams — aims to make the very techy php.net homepage speak to CTOs and newcomers about who uses PHP and why it’s a thriving project (only 31-ish years old, versus C’s 60).
The conversation closes on caretakers and the next generation of contributors. Triage, they stress, doesn’t require deep internals knowledge — just reading reports to see if they still make sense is hugely valuable. Security and infrastructure access necessarily stay gatekept for trust reasons, and both agree a bus factor of one (or even two) isn’t good enough. Chris admits he’s struggling to name people who are both nice and know infra.
Looking to hire PHP developers? Email [email protected] – the team is 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 PHP Alive and Kicking 2026.08.04 appeared first on PHP Architect.
<br />
Hosts: Joe Ferguson, Sara Golemon & Holly Schilling
Fahrenheit, Boiling Rocks, and Byte-Ordering Dates
From there the crew tumbled down a rabbit hole of measurement units. Joe planted his flag on Fahrenheit as the human-centered temperature scale, while Sara argued that if you stop being “speciesist” about it, water-based Celsius wins. The debate somehow escalated into whether rocks boil, with Google eventually schooling everyone that molten rock vaporizes north of 3,000°C (5,400°F), and a callback to British “stones” as boomer energy nobody younger than half a century actually uses.
Proper Logging with PSR-3
The big selling point of sticking to a PSR-3-compatible interface is minimal dependencies — instead of pulling in three or four packages and wiring up a pile of configuration, the upstream decisions are already made for you. Holly pushed back on the ergonomics of `$this->logger->error()` feeling heavy for every log call, which spun off a delightfully unhinged RFC pitch: built-in emoji functions where the emoji logs an error and logs a panic.
The Ecosystem Is Why People Stay
Holly cut to what everyone had glossed over: the ecosystem. You can write Swift on the server with Vapor, but you won’t have the libraries. Whatever you need in PHP, it already exists. A listener even pointed Joe at Brent Roose’s Tempest framework mid-stream to solve a code-highlighting problem on his blog. That gravitational pull of “whatever you need, it’s here” is what keeps people in the PHP orbit.
AI, Layoffs, and Graybeards
Joe brought up an Inc.com article claiming 55% of leadership now regret their major layoffs, with companies like Ford rehiring graybeards because nobody left knew how the software worked. Holly noted this cycle isn’t new, just operating at a terrifying new scale, and Sara emphasized that AI accelerates shipping crap just as easily as it accelerates shipping good work — you still have to fundamentally understand the changes you’re applying.
Codeberg’s Anti-AI Stance & the Slop Bug Report Problem
That led into Sara’s frustration with AI-generated security slop. Daniel Stenberg shut down Curl’s bug bounty program over reports where someone’s own test program deliberately creates RCEs and blames Curl. The fix, Sara argued, is a one-paragraph “elevator pitch” summary — and a plea to maintainers to mark every slop report as spam so GitHub eventually bans the account. The group riffed on adversarial AI (two Claude contexts checking each other, like Apple Intelligence verifying sports-game summaries) as a defensive triage layer, while acknowledging people are simply too dumb to run “double-check this before submitting.”
Laracon: Laravel Cloud Scale-to-Zero
Holly and Sara were skeptical about how you cold-start a MySQL instance that fast — almost certainly a pause/resume rather than a true cold start. Other Laracon news: a Laravel language server protocol for better autocomplete and code navigation, plus managed queues that also scale to zero and only wake when a job needs firing.
Looking to hire PHP developers? Email [email protected] – the team is available for consulting, infrastructure work, 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.07.30 appeared first on PHP Architect.
<br />
Hosts: Joe Ferguson, Sara Golemon, and Holly Schilling
A Show Without Pants: The Guest Takeover
There was plenty of housekeeping to get through: PHP Tek 2027 lands April 27th through 29th in Chicago, the CFP is open, and the call for papers closes August 31st. Holly, ever the deadline enthusiast, admitted she loves “the sound deadlines make as they whoosh by,” which set the tone for much of the episode.
And yes, the swag store now has PHP Architect socks. There was extensive debate about whether the socks are safe for large-footed individuals, whether banana-for-scale photos are needed, and whether Eric should post feet pics. DuckNizzle bought some socks. We are also, apparently, SOC 2 certified.
The Great Elephant Migration
Only six elephants are currently on hand, and technically none of them are PHP Architect elephants — though one is a PHP Roundtable elephant, prompting the recurring wish that someone should bring that podcast back. Spoiler: they might, more on that later.
Sara also shared she’s been in intensive foreign language classes every day, getting up at 7 a.m. while not falling asleep until 2 a.m., all while assembling a Prusa Core One+ 3D printer kit with roughly 300 pages of instructions and hundreds of tiny pieces.
SIMD and Data Science in PHP
Sara pushed back on how deep into the processor this discussion goes, noting that floating point math already flows through the SIMD registers — so in a very narrow sense, you’re already getting SIMD support in current PHP. Reordering instructions safely is another matter entirely (see: Intel’s history of getting it wrong).
The conversation tied back to Florian Englehart’s “One Billion Rows” talk at PHP Tek 2025, and Holly mentioned her monomorphic generics work now supports variadic types — meaning a typed vector structure could, with a bit of JIT work, make SIMD-style patterns possible in PHP’s near future.
PHP 8.6 Feature Freeze Is Coming
Sara, one of PHP’s previous release managers, was philosophical about people panicking at the deadline: you’ve had twelve months, your lack of planning is not the release team’s problem. An idea to move the feature freeze date was floated and quickly shot down — the cadence has been established for years, and one missed email doesn’t change that.
Larry got a shout-out for suggesting internals push all new business to September so 8.6 can get properly tested. And Holly declared, in full Benevolent Dictator mode, that the next release simply has to be 9.0 — too many big features to ship for a mere 8.7.
AI, Copyright, and Whether Machines Can Create
Holly described using AI to implement a new module dereference operator (colon greater-than) that exists nowhere but her own machine, arguing the AI isn’t stealing when it follows precise instructions to generate novel syntax. Sara countered that the LLM isn’t creating so much as blending existing functionality — following instructions rather than inventing.
The debate turned philosophical: how much truly new code have humans written in the last decade? We stand on the shoulders of giants, we’re “thinking meat sacks,” and Sara cheerfully accepted the label of “biased anti-clanker bigot.” The Terminator is coming for Larry first, apparently.
Foundation Transparency and Household Jira
This spiraled into a discussion of household project management — one host’s wife is a project manager, another family installed a Jira instance for their home that the programmer husband absolutely hates, and there’s a gamified house-cleaning app that Holly refuses to adopt for fear she’ll either become obsessed or start a fight over losing.
The episode wrapped with talk of finally reviving PHP Roundtable (scheduling permitting), Longhorn PHP acceptances, and gentle ribbing that Eric and John are “getting up in years” and can’t perform with their usual podcast consistency. There’s a pill for that.
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.07.23 appeared first on PHP Architect.
From the publisher's feed

38,617 Listeners

18 Listeners