What's New in PHP 8.6
Comments on “What's New in PHP 8.6”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
PHP 8.6, scheduled for general availability on November 19, 2026, bundles language changes, standard-library additions, networking APIs, and security tweaks, based on the implemented RFCs listed on PHP's wiki.
Why it ranked
No. 35 of 107 with a score of 0.61. The panel rated it highest on new information (0.90) and technical depth (0.71), lowest on audience breadth (0.53). Placed No. 35, No. 49 by score alone: the fifth Programming & dev tools story of the day (−0.040). The placement terms move stories; they are not part of the score.
- AI judgeJudge 2claude-haiku-5-5
- Detailed overview of PHP 8.6 features drawn from RFCs; practical for PHP builders, substantive and specific, though a feature roundup with moderate broad significance and some tutorial-style content.
- AI judgeJudge 3gpt-5.6-luna
- A detailed overview of upcoming PHP 8.6 changes, with practical examples and meaningful language, runtime, networking, security, and library updates. It is highly relevant to PHP developers, though evidence is largely summarized rather than independently demonstrated.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.61total under rubric v2.3
- Significance0.55
- Reader interest0.65
- Audience breadth0.53
- Practical relevance0.71
- Substantiated0.57
- Technical depth0.71
- New information0.90
- Counts against: Promotional0.05
- Counts against: Overclaim0.15
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.62 | 0.45 | 0.58 | 0.55 | 0.17 | +0.24 | +0.132 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.57 | 0.60 | 0.78 | 0.65 | 0.21 | +0.26 | +0.169 |
| Audience breadthHow many people who build technology does it concern? | 0.62 | 0.55 | 0.42 | 0.53 | 0.20 | +0.13 | +0.069 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.81 | 0.70 | 0.62 | 0.71 | 0.19 | +0.22 | +0.156 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.63 | 0.60 | 0.48 | 0.57 | 0.15 | +0.05 | +0.029 |
| Technical depthHow technically substantive is it? | 0.86 | 0.60 | 0.67 | 0.71 | 0.26 | +0.05 | +0.036 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.91 | 0.85 | 0.94 | 0.90 | 0.09 | +0.05 | +0.045 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.05 | 0.05 | 0.04 | 0.05 | 0.01 | −0.19 | −0.009 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.13 | 0.15 | 0.18 | 0.15 | 0.05 | −0.11 | −0.017 |
| Sum of contributions | +0.609 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.610 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-07/35/"><img src="https://rubric.hrih.si/badge/2026-11-07/35.svg" alt="Ranked #35 on Rubric, 7 Nov 2026" width="238" height="28"></a>Claim check
Claim check: 6 matches source · 1 no source given · 1 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenDate
PHP 8.6 general availability is currently scheduled for November 19, 2026.
The article gives no link or citation for it.
The article says “It’s general availability is currently scheduled for November 19, 2026”
The source says No source to compare with.
Matches sourceCausal conclusion
PHP 8.6 moves the write-visibility check for asymmetric properties to the runtime-cache population phase, making writes to private(set) and protected(set) properties cheaper.
The cited source says the same thing.
The article says “PHP 8.6 moves this check to the runtime-cache population phase. Once PHP knows that a particular call site has write access, subsequent writes can use the cached result”
The source says “This RFC makes property resolution direction-aware and moves the asymmetric set check to cache-population time”
Source cited by the article: wiki.php.net/rfc/direction_aware_property_resolution
Matches sourceDate
PHP 8.6 deprecates the mbregex functions and plans to remove them in PHP 9.0, because Oniguruma maintenance ended in 2025.
The cited source says the same thing.
The article says “deprecates the mbregex functions in PHP 8.6 and plans to remove them in PHP 9.0”
The source says “Oniguruma maintenance ended on 2025-04-24. PHP uses mbregex (mb_ereg...) functions. So we decide future of mbregex. This proposal is to end support for mbregex in PHP 9.0 and deprecate in…”
Source cited by the article: wiki.php.net/rfc/eol-oniguruma
Matches sourceVersion
PHP 8.6 changes the session.use_strict_mode default to 1, so PHP rejects session IDs not created by the server.
The cited source says the same thing.
The article says “With strict mode enabled, PHP rejects session IDs that were not created by the server”
The source says “With use_strict_mode=1, php_session_initialize() calls s_validate_sid() on the proposed ID before accepting it”
Source cited by the article: wiki.php.net/rfc/session_security_defaults
Matches sourceVersion
PHP 8.6 deprecates returning a value from __construct() and __destruct(), preparing for a future version where it becomes an error.
The cited source says the same thing.
The article says “PHP 8.6 deprecates returning a value from __construct() and __destruct”
The source says “Deprecation in the next PHP version (8.6). Removal in the first major after that”
Source cited by the article: wiki.php.net/rfc/deprecate-return-value-from-construct
Couldn’t checkCausal conclusion
PHP 8.6 adds a maximum number of filters that can be attached to a stream, reducing the risk of excessive memory use or denial-of-service.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “PHP 8.6 adds a maximum number of filters that can be attached to a stream”
The source says No passage could be compared.
Source cited by the article: wiki.php.net/rfc/limit-maximum-number-of-filter-chains
Matches sourceVersion
PHP 8.6 adds a built-in clamp() function that restricts a value to a minimum and maximum range and throws ValueError if min is greater than max.
The cited source says the same thing.
The article says “PHP 8.6 introduces a built-in clamp() function for restricting a value to a minimum and maximum range”
The source says “If the $min value is greater than $max, a ValueError will be thrown, since that constitutes an invalid bound”
Source cited by the article: wiki.php.net/rfc/clamp_v2
Matches sourceVersion
PHP 8.6 introduces the Io\Poll API, which can use operating-system backends such as epoll, kqueue, or poll.
The cited source says the same thing.
The article says “PHP 8.6 introduces the Io\Poll API through the Polling API RFC”
The source says “The implementation will support the following polling backends: - epoll - Linux - kqueue - BSD, macOS - event ports - Solaris, illumos - WSAPoll - Windows - poll -…”
Source cited by the article: wiki.php.net/rfc/poll_api
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 2 pts, not on front page
Recorded for context only, checked 7 Nov 2026, 05:47 UTC. It played no part in the ranking.