u/rc0604

This RFC is now in the voting phase. Lowkey, it could have a massive impact on PHP, especially by bringing more modern backend stream handling. It would also replace stream_select() and make async PHP libraries far more viable without relying on extensions like ext-uv to bypass file descriptor limitations and O(N) performance.

Hello everyone, I just wanted to share a past article I wrote about this topic. I’d love to hear your thoughts, feedback, or any questions you may have.

Hello everyone! I'm excited to announce that hiblaphp/postgres, built on top of ext-pgsql, is now available in beta, fully tested and can now be installed via Composer.

With this release, the core database drivers for Hibla are now complete alongside the Hibla MySQL client. My next goal is to build an asynchronous query builder with support for migrations and pagination before moving on to developing an HTTP server.

Some of the key features currently included are:

• Fully non-blocking query execution
• Name parameter and Positional parameter binding support like "?" and ":name" for prepared statements
• Server-side query cancellation
• Pub/Sub event-driven notifications with auto-reconnect support
• Streaming support
• Connection pooling

I'd really appreciate any feedback, whether it's feature suggestions, questions, or even harsh criticism. Every bit of feedback helps improve the project.

What if, as a compromise, a generics implementation in PHP supported optional runtime enforcement through a php.ini configuration, similar to how assert() works with zend.assertions? This would provide the best of both worlds: runtime generics during development for stronger validation and debugging, while still allowing static analysis tools like PHPStan and Psalm to handle compile-time type analysis and developer tooling. In production, the runtime checks could be completely erased for maximum performance.

bago lang tong account ,, skl