Cees-Jan Kiewiet 
Attempting to get some PR's for @reactphp out, can't even rebase right now:
Just released v0.6.0-alpha.2 of bunny/bunny the #PHP #AMQP client powered by @reactphp. One bugfix and two new features added in this second alpha namely, Configuration object and DSN support. Full notes here: https://github.com/jakubkulhan/bunny/releases/tag/v0.6.0-alpha.2
JaapioI have built my first php webserver, using #ReactPHP . Because I'm experimenting with a new possible feature for @phpdoc hot reload, on your docs... To make it a better development experience.
What do you think? Would you use that, when writing #documentation?
Zuri (he/him) âī¸đ đ CET@darkghosthunter I'd imagine #PHP's never truly gonna be async by nature because the way it works is incompatible with that. Therefore, #ReactPHP, #Swoole, #amp_php, and #ratchedPHP being merely workarounds is just the natural conclusion of that.
But I might be wrong. Maybe, some smart person figures out a way to overcome PHP's limitations on that front while not breaking the language. That'd be awesome. I keep my fingers crossed for you đđģ đ¤đģ
Time for a release Friday release: Bunny v0.6.0-alpha.1 is out with a host of changes since v0.5: https://github.com/jakubkulhan/bunny/releases/tag/v0.6.0-alpha.1
It's been a lot of fun doing this major rework on Bunny's internals into a full @reactphp client while using fibers internally to simplify the public API.
Started preparing the Bunny 0.6 release post for later this year, GitHub sponsors get a preview in a few days:
Seeing the difference in numbers, 10 years apart, countless upgrades and changes to @reactphp, merged Sync and Async clients into one non-blocking (fiber) client, many improvements to PHP since, it hypes me up with excitement for what is next. Also added ext-amqp to the comparison: https://github.com/jakubkulhan/bunny?tab=readme-ov-file#comparison
Released v1 of wyrihaximus/react-opportunistic-tls for @reactphp: https://github.com/WyriHaximus/reactphp-opportunistic-tls/releases/tag/1.0.0
