The latest dev chat turned into an argument over whether WordPress Core should require PHP’s filter extension. PHPMailer uses it today. Here is what that costs you on hosts that compiled PHP without it.
A WooCommerce site broke because its new host had no bcmath extension. The proposed filter for the required PHP extensions list in core would catch that kind of gap before checkout starts failing.
Twenty near-identical buttons in one design file cost me three hours per border-radius tweak. Component variants in Penpot fixed that, and DTCG tokens made the handoff to CSS boring, which is exactly what you want.
The RTX 30-series has no hardware FP8, so I packed four FP8 values into one FP32 container and unpacked them inside a Triton kernel. On a client’s 3080s that cut the memory bottleneck and ran about 3.3x faster.
A core update took a client’s checkout page down at 2 AM. Reading the release retrospectives and controlling minor auto-updates per environment is how I stopped that from happening again.
WooCommerce 10.4 makes the Interactivity API mini cart the default, lazy-loads two REST namespaces, and takes HPOS caching out of experimental. Here is what to test before you update.
WordPress 6.9 beta ships the server-side half of the Abilities API. You can register and retrieve abilities in PHP, but the client-side JavaScript moved to the Gutenberg repo, so there is no native AI interface in the editor yet.
WordPress 7.0 pulls View Transitions into core, and ticket #64066 raises preloading eagerness when a proxy cache is detected. Here is what that changes for admin speed, and why blanket prefetching pinned my CPU at 100%.
The 2026 proposal moves WordPress back to three majors a year, roughly one every four months, with one to three minors in between. Freezing a client site at 6.7 is what taught me why that cadence is easier to live with.
WooCommerce 10.4.3 patches guest order data exposure in the Store API, throttles HPOS sync-on-read during heavy jobs, and restores the cart undo link that 10.4.2 broke.