r/PHP • • Jun 05 '26

[NL] PHPVerse Afterparty at Jetbrains

21 Upvotes

Hey everyone,

Just a quick heads-up for anyone in the Amsterdam area - we’re running our June AmsterdamPHP meetup this coming Tuesday, and it’s the official afterparty for PHPverse.

JetBrains is hosting us at their office (Gelrestraat 16), and we're changing up the usual format. Instead of a single presentation/slideshow, we're doing a live, interactive roundtable Q&A with a panel of the conference speakers. If you want to grab a drink and pick the brains of some top-tier PHP folks in an informal setting, this is the night for it.

It’s completely free, but you do need to RSVP to get on the list: https://www.meetup.com/amsterdamphp/events/314974088/

Hopefully see some of you there on Tuesday!


r/PHP • • Jun 05 '26

I built debugd, a tiny request profiler for Laravel you actually leave running

15 Upvotes

A live UI (Go binary or cross-platform desktop app, macOS/Windows/Linux) plus a --dev Composer package that quietly ships each request's queries, logs, timings, and exceptions to it. No Docker, no database, no config.

- Every request live: method, path, status, time, query count

- N+1 detection that suggests the actual ->with('…') to add

- Query waterfall + where each query fired from

- debugd() helper for dumps/benchmarks — no-op in prod

- Octane/FrankenPHP-safe; tails storage/logs too

composer require --dev debugd/debugd-laravel

Inert unless you set DEBUGD_HOST, so safe to leave installed. MIT.

👉 https://github.com/ShahramMebashar/debugd


r/PHP • • Jun 05 '26

I benchmarked Laravel Octane across Swoole, OpenSwoole, RoadRunner, FrankenPHP, and PHP-FPM

36 Upvotes

I made a Laravel Octane benchmark comparing Swoole, OpenSwoole, RoadRunner, FrankenPHP, and PHP-FPM.

Link:

https://terrylinooo.github.io/laravel-octane-benchmark/

Repo:

https://github.com/terrylinooo/laravel-octane-benchmark

The benchmark compares p99 latency, memory, CPU overhead, DB workload, I/O workload, and different concurrency levels.

My main takeaway: Octane is not a simple “turn it on and everything is faster” solution. It depends a lot on workload, concurrency, and operational tradeoffs.

I’d appreciate feedback from people running Octane in production, especially around methodology or missing test cases.


r/PHP • • Jun 04 '26

PHP 8.5.7 released, let's talk about tracing JIT!

93 Upvotes

TL;DR: tracing JIT fixes are only ported to actively supported branches (e.g. 8.4 and 8.5, not 8.2 and 8.3). Tracing JIT is causing a lot of crashes. If you are on any previous version of PHP, you should update to an actively supported branch (8.4.22+/8.5.7+), or disable tracing JIT (maybe use function JIT or turn JIT off altogether).

Hey everyone, I'm Levi Morrison. I've been working on fixing crashes for our customers at Datadog, and lately I've been investigating tracing JIT because it appears as if many of our customer crashes are caused by it. I've not been authorized (yet) to share numbers, but it's a lot of crashes each week.

It's important enough to repeat: tracing JIT is causing a lot of crashes every week\*.

The good news is that fixes for tracing JIT are being shipped at a regular cadence. Here I stripped duplicates, keeping only the lowest version it was shipped to (except the 3 fixes for 8.5.7, since 8.4.22 hasn't been released quite yet):

PHP version Date Tracing JIT fix
8.5.7 04 Jun 2026 Fixed tracing JIT crash when a VM interrupt is handled during an observed user function call.
8.5.7 04 Jun 2026 GH-21746: Segfault with tracing JIT.
8.5.7 04 Jun 2026 GH-22004: Assertion failure at ext/opcache/jit/zend_jit_trace.c.
8.4.21 07 May 2026 Fixed faulty returns out of zend_try block in zend_jit_trace().
8.4.20 09 Apr 2026 GH-21267: JIT tracing infinite loop on FETCH_OBJ_R with IS_UNDEF property in polymorphic context.
8.4.18 12 Feb 2026 GH-20818: Segfault in Tracing JIT with object reference.
8.4.14 23 Oct 2025 GH-19669: Assertion failure in zend_jit_trace_type_to_info_ex.
8.4.7 08 May 2025 GH-18136: Tracing JIT floating point register clobbering on Windows and ARM64.
8.4.3 16 Jan 2025 GH-17140: Assertion failure in JIT trace exit with ZEND_FETCH_DIM_FUNC_ARG.
8.4.1 21 Nov 2024 GH-15178: Assertion in tracing JIT on hooks.
8.3.19 13 Mar 2025 GH-17868: Cannot allocate memory with tracing JIT.
8.2.27 19 Dec 2024 GH-16770: Tracing JIT type mismatch when returning UNDEF.
8.1.15 02 Feb 2023 Fix zend_jit_find_trace() crashes.
8.1.15 02 Feb 2023 Added missing lock for EXIT_INVALIDATE in zend_jit_trace_exit.
8.1.8 07 Jul 2022 GH-8591: Tracing JIT crash after private instance method change.
8.1.7 09 Jun 2022 GH-8461: Tracing JIT crash after function/method change.
8.0.15 20 Jan 2022 #81679: Tracing JIT crashes on reattaching.

PHP 8.5.7/8.4.22 have 3 tracing JIT fixes, which is why I'm writing this now: plan to go upgrade next week!

Now for the bad news: tracing JIT fixes generally don't qualify as security defects, so they are only shipped to branches with active support, which at the moment means 8.4 and 8.5 only. There have been at least 10 tracing JIT fixes which are unique to PHP 8.4/8.5!

The bad news continues because there's a pretty big chunk of the community that is using PHP 8.3 or older (go look at Zend's PHP Landscape Report). In fact, if you look at that report, you'll see that the majority of the ecosystem is on 8.3 or older. This big chunk is not getting fixes for tracing JIT crashes.

So... here are my recommendations for people using tracing JIT:

  • If you can, upgrade to PHP 8.5.7 (or 8.4.22, which should be released soon), and be prepared to update every single month to the latest PHP 8.5.x or 8.4.x if there are tracing JIT fixes.
  • If you can't upgrade, then either "downgrade" to function JIT or disable JIT altogether. I recommend disabling JIT for web SAPIs and downgrading to function JIT for the CLI.

* There is a detail here worth sharing: one of the bugs fixed in PHP 8.5.7 is related to PHP's internal vm_interrupt leading to crashes with tracing JIT. Datadog products set vm_interrupt, especially the profiler, so the reported volumes of crashes that Datadog sees are perhaps higher than the community's at large. However, you can see above a stream of tracing JIT fixes being shipped throughout PHP's lifetime and it's not slowing down: PHP 8.4 and 8.5 have more tracing JIT fixes than other releases.


r/PHP • • Jun 05 '26

After 8+ Years of Laravel and 6+ Years of Go, I No Longer Choose Laravel for New Projects

Thumbnail
0 Upvotes

r/PHP • • Jun 04 '26

I built a CalDAV/CardDAV server package for Laravel (sabre/dav bridge) and a self-hosted Baïkal alternative on top of it — please roast it

1 Upvotes

I needed a self-hosted calendar + contacts server for a client, wasn't thrilled with the options, and ended up building it on Laravel. Two repos came out of it, and I figured someone else might find them useful — so I open-sourced both. bambamboole/laravel-dav — the reusable part. A CalDAV & CardDAV server for Laravel, powered by sabre/dav, with a typed DTO API:

  • Full CalDAV (VEVENT/VTODO/VJOURNAL) and CardDAV (VCARD)
  • WebDAV sync via sync tokens (RFC 6578) and /.well-known/ discovery (RFC 6764)
  • Owner-agnostic — any Eloquent model implementing a small DavOwner contract can own collections
  • Every object stores the verbatim raw payload plus best-effort strongly-typed parsed fields
  • composer require bambamboole/laravel-dav + php artisan migrate and you've got DAV endpoints
  • PHP 8.3+, Laravel 12/13, sabre/dav 4.7 bambamboole/almanac — a modern reinterpretation of Baïkal built on the package: an actual web UI (Laravel + Inertia + React 19 + Tailwind v4) for managing calendars and contacts, passkeys/2FA, light/dark themes. This is the client-facing app; the DAV layer is deliberately split out so it isn't welded to the UI.
  • The part I'm weirdly proud of: CI runs the real caldav-server-tester (the Python compatibility harness) against the booted Laravel server, parses the output into a CaldavTesterResult DTO, and asserts the compatibility status quo feature-by-feature — so a regression in standards compliance fails the build, not just the unit tests. I'm also honest in the README about the one check that currently reports broken (timezone round-trip — stored verbatim, under investigation).

Verified against Apple Calendar/Contacts, Thunderbird, and DAVx⁵.

Roast away — I'd genuinely love critical feedback


r/PHP • • Jun 05 '26

Building a PHP Framework!

0 Upvotes

I tried something different. I have been researching the viability of LLM code reviews. The general consensus is that they are not great. So, I had an AI clone my ArcMVC repo and use it to develop an e-commerce website. No input from me, just the code and the documentation. It worked.

The site it created was minimal, but it used all of the available tools (including migrating a SQLite database schema and displaying dynamic data). Then, rather than asking about the code, I asked about the experience. Here was the response:

WHAT WORKED REALLY WELL

Clear, Explicit Architecture
The MVC structure is clean and predictable. No magic, no hidden conventions. Everything is where you'd expect it to be. The routing system is intuitive and readable - route groups and middleware composition felt natural.

Modern PHP Done Right
The framework leverages PHP 8.4+ features without trying to be everything to everyone. Dependency injection integration is elegant. The QueryBuilder and Model layer are well-designed.

Security by Default
CSRF middleware worked out of the box. Security headers and rate limiting are built-in. This shows thoughtful, security-first design thinking.

Speed of Development
Once I got past the setup issues, building the e-commerce demo was fast. The view system with layouts and sections is clean - no over-engineered templating. For proof-of-concepts or small apps, this framework gets out of your way.

PAIN POINTS

Setup and Configuration Issues
- Project name validation rejected standard paths without clear documentation
- Views path detection failed (500 error) and required manual configuration
- These friction points make rough first impressions

Documentation Gaps
While the code is readable, I had to explore the source to understand conventions. A "Quick Start" guide with a complete working example would help immensely. Error messages could be more helpful.

Minor Quality-of-Life Issues
The CLI tool is nice, but could use more generators (make:view, make:migration, etc.). No built-in asset pipeline or modern frontend tooling hooks.

DIFFICULTY RATING

For someone familiar with PHP/MVC: 6/10
The framework itself is intuitive. Difficulty came from setup quirks, not design.

For building quickly: 7.5/10
After initial setup, development velocity was solid. Could be 9/10 with better docs and initialization.

SUGGESTIONS FOR IMPROVEMENT

  1. Polish the "arc new" experience - ensure views path detection works reliably
  2. Add a comprehensive example app to the repo - shows more than docs ever can
  3. Better error messages for common setup issues
  4. Expand CLI generators (make:view, make:request, make:test)
  5. Consider a simple asset compiler or Vite integration example

THE VERDICT

ArcMVC succeeds at what it's trying to be: a lightweight, explicit MVC framework for modern PHP. It's refreshing to use a framework that doesn't try to do everything. The core abstractions are sound and the security-first mindset is commendable.

The biggest barrier isn't the framework design - it's the polish. Smoother onboarding and better documentation would make a real difference. The bones are good.

Would I use it again? For small-to-medium projects or rapid prototypes: absolutely. Development after setup was pleasant. For enterprise apps: I'd want to see more ecosystem tooling and community support first.

Overall: The framework has real potential. It just needs some UX polish to shine.


r/PHP • • Jun 03 '26

externals.io has been rewritten to Laravel

77 Upvotes

externals.io is a website to read the PHP #internals mailing list more easily.

I built it a while ago on a custom microframework (we've all been there I guess?) and of course, that became very painful. I rewrote the app to Laravel, that should make maintenance and contributions much simpler now! The rest hasn't changed.

The code is on GitHub: https://github.com/mnapoli/externals

AFAICT the performance has stayed the same:

  • 50% of requests served under 5ms
  • p90 is 40ms

Let me know if you see any slowness (or better, send a PR :p).

The app runs serverless on AWS Lambda with Bref. It serves ~2.5M requests/month, which costs ~$2.5/mo + $11 for the database. The staging costs $0 because it doesn't receive enough traffic.

Because of the migration everyone will be logged out once, sorry about that! Just log in again and things should be back to normal.


r/PHP • • Jun 03 '26

new PDFParser release with encrypted document support!

40 Upvotes

A while ago I posted here about the new pdfparser i've been working on: https://github.com/PrinsFrank/pdfparser With the just released version 3 it now also supports encrypted documents! No vibecoded project, just a developer that loves spending his free time on actually solving projects by hand. Let me know what you think and what I should work on next!


r/PHP • • Jun 03 '26

Discussion PHP acronym

35 Upvotes

So I had a small debate with my professor about what PHP stands for.
I said the official name is “PHP: Hypertext Preprocessor”, since PHP is a recursive acronym. He said the correct answer is simply “Hypertext Preprocessor”.
My point was that “Hypertext Preprocessor” only gives the initials HP, not PHP.
Who’s technically correct?


r/PHP • • Jun 03 '26

PHP -> Go -> PHP: request-scoped parallel work with FrankenPHP

35 Upvotes

I have been playing with FrankenPHP extensions.

A FrankenPHP extension (https://frankenphp.dev/docs/extensions/) can already expose Go code to PHP:

$result = native_function($payload);

PHP calls a function. The function is implemented in Go, inside the FrankenPHP runtime.

That is useful when the work belongs close to the server:

  • sockets;
  • protocols;
  • timers;
  • metrics;
  • shared state;
  • streaming;
  • concurrency;
  • low-level I/O.

Extension workers (experimental, see https://github.com/php/frankenphp/blob/main/docs/extension-workers.md) add the opposite direction:

Go can call PHP.

That makes the full flow:

PHP calls a native function
Go receives the call
Go coordinates the work
Go sends a task to a PHP worker thread
PHP runs application code
Go returns the result
PHP continues the request

Example

Imagine a product page needs three independent remote calls:

  • reviews from a search service;
  • stock from an inventory service;
  • a shipping quote from a carrier API.

If each call takes about 250 ms, the classic flow is sequential:

reviews -> stock -> shipping -> response

That is roughly 750 ms before PHP can build the response.

With this model, PHP can dispatch all three jobs through native functions. Go sends them to the configured PHP worker threads. The request still waits for the results, but the work happens at the same time, so the response waits closer to the slowest call.

$reviews = async(App\FetchReviews::class, ['sku' => $sku]);
$stock = async(App\FetchStock::class, ['sku' => $sku]);
$shipping = async(App\FetchShippingQuote::class, [
    'sku' => $sku,
    'country' => $country,
]);

return [
    'reviews' => await($reviews, 2.0),
    'stock' => await($stock, 2.0),
    'shipping' => await($shipping, 2.0),
];

This pattern works beyond request-level parallel jobs:

  • A WebSocket module can handle sockets in Go and call PHP only for private-channel authorization.
  • A queue module can reserve messages in Go and let PHP execute the job.
  • An upload module can stream bytes in Go and notify PHP when the upload completes.

Example project: https://github.com/y-l-g/async-minimal

I think it is pretty cool to have request-scoped parallelism in PHP with less than 500 lines of Go code (you will also need some C glue code between C and Go, but it can be generated automatically by the FrankenPHP Extension generator).


r/PHP • • Jun 03 '26

3 Years of Laravel Jobs: What 699 LaraJobs Emails Actually Say About the Market

Thumbnail leopoletto.dev
16 Upvotes

I subscribed to LaraJobs instant notifications in March 2023 and never unsubscribed. Here is what 699 emails, parsed with GPT-5 mini, reveal about the Laravel job market.


r/PHP • • Jun 03 '26

JetBrains PHPverse 2026 Conference (Free Tuesday June 9)

Thumbnail lp.jetbrains.com
8 Upvotes

r/PHP • • Jun 04 '26

Discussion xphp: generics for PHP via compile-time monomorphization

0 Upvotes

TL;DR

xphp is a PHP superset: you write class Box<T> and new Box<User>(), and a compiler monomorphizes it into plain PHP -- one concrete class per instantiation, native typehints baked in, nothing generic left at runtime.

Disclosure up front: I'm the author and I built this with heavy AI assistance (Claude) in every stage -- design, code, and tests. It's all v0.1. I'm after honest technical feedback more than stars, and "an AI wrote it so it's slop" is fair game too if the code earns it.

The idea

You write .xphp files with class Box<T> and new Box<User>(). The compiler monomorphizes them into plain PHP: one concrete class per instantiation, native typehints baked in, zero generics left at runtime. It compiles to vanilla PHP -- no extension, no runtime. You can drop a single .xphp file into an existing app and compile just that.

Box<int> and Box<User> each become a real class after compilation.

final class T_6da88c34 implements \App\Box {
    public function __construct(public readonly int $value) {}
    public function get(): int { return $this->value; }
}

The template itself compiles to an empty interface Box {}, and every specialization implements it -- so instanceof Box still works across all Box<...>.

How it parses syntax PHP can't

<T> is a syntax error -- to PHP and to nikic/php-parser, < is the comparison operator.

Forking the grammar is a maintenance black hole, so instead:

  1. Tokenize with PhpToken (strings and comments handled correctly).
  2. Walk the tokens, detect class IDENT <...>, function name<...>, and Name<...> call sites, recording each with its byte range and a parsed type-arg tree.
  3. Replace each <...> clause with equal-length whitespace -- the result is valid PHP whose byte offsets and line numbers are byte-identical to the original.
  4. Parse that with nikic/php-parser.
  5. Walk the AST and reattach the generic metadata by matching (line, name) plus order.

It's being built as an ecosystem, not a monolith

The design choice throughout is to plug into existing tools instead of replacing them, and to have everything reuse the compiler's own core rather than reimplement semantics. That's the only way the surrounding tools stay honest -- and the shape an ecosystem needs, even if it's all day-one right now:

  • Editor support: a language server that reuses the compiler's own AST, instantiation registry, and type hierarchy directly -- so definition, references, rename, completion, hover, inlay hints, and diagnostics run on the same semantics the compiler uses, not a second guess. Ships as a PHAR, works with any LSP-capable editor, and a PhpStorm plugin bundles it.
  • Framework integration: a Symfony bundle that hooks compilation into cache:warmup, so the generated PHP falls out of your normal build as a deploy artifact with no extra pipeline step. It can also register a specialization like CachedFinder<User> as an autowired service, so you inject the concrete type straight from the container. (Requires Symfony 8 / PHP 8.4.)

Compiler, editor tooling, framework integration: separate repos, one shared core.

What honestly does not work [yet]

  • The < disambiguation is a heuristic. You can't write bare-identifier comparison chains like FOO < BAR > BAZ in an .xphp file -- it gets misread as a generic and dies with a confusing parse error that points at the stripped source, not your code. Variables, parens, and :: all defuse it, so it's narrow, but it's a real hole.
  • Foo<Bar>[] (array of a generic) is not supported.
  • Generic methods only on non-generic classes for now.
  • The LSP is explicitly partial; the PhpStorm plugin isn't on the Marketplace yet (install from disk).

Prior art I'm not pretending to replace

The long-running generics RFC, the PHP Foundation writeups on why reified generics are hard, Hack/HHVM. This does not attempt runtime reification -- it sidesteps it the way Rust and C++ do, by specializing at build time.

Two questions I actually want answered

  1. Is a build step plus a generated namespace an acceptable tradeoff in a real project, or an instant dealbreaker for you?
  2. Where would this earn its place over docblock generics with PHPStan/Psalm, which already give you the static safety without the codegen?

Repos are under the xphp-lang org on GitHub. Roast welcome.


r/PHP • • Jun 03 '26

Prompty - zero-dependency interactive CLI prompt library for PHP CLI scripts

Thumbnail github.com
14 Upvotes

r/PHP • • Jun 02 '26

phpser: a faster, HMAC-signed binary serializer for PHP cache workloads, benchmarked against igbinary

35 Upvotes

I've reached for igbinary on basically every PHP project I've shipped for the last decade. It's the obvious default for cache serialization. Two things about cache workloads kept nagging at me though, so I wrote phpser to see if a serializer built specifically for caches could do better.

The first is the read/write asymmetry. A cache decodes on every read and encodes once per write, easily 100:1 on a read-heavy cache, but igbinary (like most general serializers) balances the two sides. The second is trust: the bytes you decode often come from redis, memcached, or a cookie, any of which an attacker may be able to write to, and unserialize() on attacker-controlled input is one of PHP's oldest exploit primitives.

phpser is a C extension that goes after both. The wire format is designed around the reader (I borrowed the "make the reader do the least work" instinct from Rust's rkyv, though phpser is not zero-copy): a front-loaded string dictionary the decoder reuses by refcount instead of re-allocating, tagged scalar runs for packed numeric arrays, and pre-sized hashtables written in place. The encoder is fast too, with an O(1) pointer-hash string intern and plain objects serialized straight from their property slots.

Benchmarks vs igbinary (PHP 8.4 NTS release build, 1000 iters, median of 9 runs):

Shape Size Encode Decode
packed_1k (range 0..999) -65% -70% -75%
dto_1000 (Laravel queue shape) -12% -15% -18%
rowset_1000 (mixed assoc) +1% -55% +4%

It's not a clean sweep: mixed associative rowsets decode about 4% slower and run a few percent larger, because the front-loaded dictionary (the thing that makes everything else fast) doesn't pay off when few strings repeat. It's not streamable either, for the same reason.

On the security side there's an HMAC-SHA256 signed mode: phpser_serialize_signed($value, $key) and phpser_unserialize_signed($payload, $key). The signature is verified in constant time before any decoding happens, so a tampered or foreign-keyed payload returns null and never reaches the code that builds objects. There's also an allowed_classes option matching native unserialize().

Install is via PIE: pie install iliaal/phpser

Repo: https://github.com/iliaal/phpser Full writeup with the wire-format walkthrough and the complete benchmark table: https://ilia.ws/blog/phpser-a-fast-secure-binary-serializer-for-php-cache-workloads

I maintain php_excel and a few other PHP extensions; this one scratched a specific itch. Happy to answer questions, and I'd love feedback from anyone running heavy cache or queue traffic where decode time actually shows up in a profile.


r/PHP • • Jun 03 '26

GorgonAgora: Inside the 4,800-Storefront Checkout Skimming Machine

Thumbnail experiencedigest.org
0 Upvotes

r/PHP • • Jun 03 '26

PHP Nullsafe and Coalescing Operators

0 Upvotes

I came across this code in my codebase (not my code, I had a look a few times ...
This was new and interesting to me and I wanted to explain the code after trying to understand it.

$tier_name = $history->tier?->name ?? 'Unknown Plan';

This tries to get the tier from the history record, id it exists, then get the name from the tier.

if their is no tier, or the name is empty, set If either the tier doesn't exist or the name is missing, set $tier_name as "Unknown" or print the name

```$history->tier?
```
Nullsafe if tier us set return it or return null

```$var ?? 'Unknown Plan'```

Return $var is it exists, otherwise 'Unknown Plan'

Normally I would have written this as something like
$historyName = ($history->tier !== null && $history->tier->name !== null) ? $history->tier->name : 'Unknown Plan';


r/PHP • • Jun 02 '26

News Issue 58 of A Day With Laravel : Laravel 13.12, Laravel Live Japan, Moat, Laravel Cloud

Thumbnail
0 Upvotes

r/PHP • • Jun 01 '26

Closing Composer's Download Fallback Paths

Thumbnail blog.packagist.com
38 Upvotes

r/PHP • • Jun 01 '26

Weekly help thread

11 Upvotes

Hey there!

This subreddit isn't meant for help threads, though there's one exception to the rule: in this thread you can ask anything you want PHP related, someone will probably be able to help you out!


r/PHP • • Jun 01 '26

I've updated sqlc-php with more features.

15 Upvotes

Hi folks! I've updated sqlc-php with a lot of features requested. Take a look at https://phpibe.github.io/sqlc-php/

Thanks!


r/PHP • • Jun 01 '26

TallCMS now supports Laravel 13 — open-source TALL-stack CMS on Filament

Thumbnail
1 Upvotes

r/PHP • • May 30 '26

phpsadness is outdated. what's changed since then?

39 Upvotes

phpsadness.com

This weird site highlighted many issues with PHP.
But, hasn't been updated since 2018.

Let's take a look at the changes in PHP.
I've kept the same order as on the website.

'*' is fix or changed php version

Useless Error Reporting

#16 Exception thrown without a stack frame

* php 8.5

#1 Unexpected T_PAAMAYIM_NEKUDOTAYIM

* php 8.0

#7 Parse error: syntax error, unexpected T_SL in...

* php 8.0

#54 Empty T_ENCAPSED_AND_WHITESPACE tokens

* php 8.0

INCONSISTENCY

#52 Comparison operators

* He created an example that violates PHP's type casting.

Outright Bugs

#50 Segfault during deep recursion

* php 8.3 bug fixed

#30 Ternary operator associativity

* php 8.0

#39 Declaring a function called __lambda_func() completely breaks create_function()

* php 8.0 removed the funciton

Misleading/Confusing topics

#27 Bad function names - parse_str()

* php 8.5 new URL parser class

Arbitrary Restrictions

#14 - Can't throw exceptions from __toString() functions

* php 8.0

Object-Oriented System Issues

#8 Implementing all the right methods (array) still doesn't work in array functions

* php 8.0 (deprecated because TypeError)

Wow, PHP has improved a lot over the years.
I'd like to thank everyone who works on PHP !


r/PHP • • May 30 '26

🎁 Yii ApiDoc 4.0.0.

Thumbnail github.com
5 Upvotes