PHP 8.6 Deprecation Bundle Sparks Debate Over Impact Data and Array Syntax

·2 views

The PHP internals community is actively debating Gina P. Banyard's annual PHP 8.6 deprecations bundle, with a vote expected to open no earlier than July 21, 2026 after a mandatory 14-day cooldown. A heated exchange erupted over potentially deprecating array() syntax, with concerns raised that such a change could affect a large portion of WordPress core and its plugins, though the actual proposal targets list() rather than array(). Contributor Rowan Tommins threatened to vote against 27 of 35 proposals citing insufficient impact analysis, while Banyard declined to produce metrics without an agreed methodology. Juliette Reinders Folmer offered to generate real-world impact data using PHPCompatibility for roughly 25 of the 36 items, helping to ease tensions. Separately, the Time\Duration RFC for PHP 8.6 was declared feature-complete, with key design decisions finalized including method naming conventions and restrictions on negative constructor arguments.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

CSR vs SSR vs SSG: Why Your Rendering Choice Decides SEO Visibility

A website's rendering strategy — where and when HTML is built — fundamentally determines whether search crawlers index its content. Client-side rendering (CSR) sends browsers a near-empty HTML file that only fills with content after JavaScript executes, leaving many crawlers with nothing to read. Server-side rendering (SSR) and static site generation (SSG) both deliver complete HTML on the first request, making content immediately accessible to crawlers. Google's two-wave indexing process can delay CSR-rendered content by days, while social preview bots and other crawlers often skip JavaScript execution entirely. For sites dependent on organic traffic, choosing SSR or SSG over CSR is considered a foundational SEO decision that precedes any work on keywords, links, or content quality.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Playwright Automation Exposes Three Critical Bugs in LLM Long-Term Memory System

A developer discovered that their LLM-powered customer support assistant was failing to retain user information across sessions after real-world users reported repeated memory failures. Manual testing had masked the issues, prompting the team to build an automated end-to-end test suite using Playwright for Python. The tests simulated full multi-session memory flows — including login, session initialization, and cross-session recall — to make precise, repeatable assertions that human testers could not reliably perform. This approach revealed three framework-level bugs in LangChain's ConversationSummaryBufferMemory, including a memory leak that caused one user's data to bleed into another's session. The developer chose Playwright over Selenium and Puppeteer due to its native Python async support, auto-waiting, and ability to run multiple browser contexts simultaneously within a single script.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Pakistani SaaS Founder Loses Codebase After Buyer Pays $1K of Promised $200K

A Pakistani software founder who built a $100K monthly recurring revenue AI SaaS product over three years says he was defrauded during an acquisition deal in May 2026. He transferred his domain and full codebase to the buyer's AWS environment before receiving payment, based on six written commitments to fund a $30,000 deposit. The buyer, identified as James De Berardine, a Philadelphia nightclub director, ultimately paid only $1,000 and retained the code for two months while requesting extensive due diligence. When the founder pushed to finalize the deal, the buyer dismissed the transaction as illegitimate and claimed the code had no value. The founder has since filed complaints with the FBI Internet Crime Complaint Center and Pennsylvania authorities, and has published a documented timeline of the alleged fraud.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Cursor-Based Pagination Outperforms SQL Offset for Large-Scale Datasets

Standard SQL offset pagination becomes a serious performance bottleneck as databases scale to millions of rows, with deep page queries potentially spiking CPU usage to 100%. The core issue is that offset queries scan all preceding rows before returning results, giving them O(N) linear complexity. Cursor-based pagination solves this by using a unique identifier from the previous page to tell the database exactly where to begin, enabling constant O(1) query time regardless of page depth. Because the cursor leverages an indexed field for a direct pointer lookup, performance stays consistent whether loading page 2 or page 50,000. For engineers building read-heavy or large-scale systems, switching to cursor-based pagination is considered a straightforward way to reduce disk I/O and improve scalability.

0 comments Read more at DEV Community