Could ext-request become a drop-in replacement for Laravel/Symfony request classes? #53
Description
Hi Paul,
First of all, amazing work with ext-request — it's elegant, efficient, and clearly engineered for performance at the core level. I’ve been exploring how it compares to frameworks like Laravel or Symfony, which do a lot of the same request parsing, but with much heavier abstractions.
Given how fast and minimal this is, have you ever considered whether Ext\Request could serve as a drop-in alternative to framework-native request objects, like Illuminate\Http\Request in Laravel or Symfony's Request?
Imagine a world where Laravel's $request behind the scenes was powered by your C-level PSR-7 implementation — drastically reducing overhead for high-traffic APIs.
Have you ever thought about creating framework-specific adapters or bridges for ext-request? This could potentially open the door for performance-driven developers to swap out heavier components without losing functionality.
Would love to hear your thoughts — and if there's any roadmap in mind for something like this. I think it has huge potential.