home.social

#reactphp — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #reactphp, aggregated by home.social.

  1. 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: github.com/jakubkulhan/bunny/r

    #ReactPHP

  2. 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: github.com/jakubkulhan/bunny/r

    #ReactPHP

  3. 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: github.com/jakubkulhan/bunny/r

    #ReactPHP

  4. 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: github.com/jakubkulhan/bunny/r

    #ReactPHP

  5. 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: github.com/jakubkulhan/bunny/r

    #ReactPHP

  6. @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 👍🏻 🤞🏻

    #OpenSwoole

  7. @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 👍🏻 🤞🏻

    #OpenSwoole

  8. @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 👍🏻 🤞🏻

    #OpenSwoole

  9. @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 👍🏻 🤞🏻

    #OpenSwoole

  10. @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 👍🏻 🤞🏻

    #OpenSwoole

  11. Time for a release Friday release: Bunny v0.6.0-alpha.1 is out with a host of changes since v0.5: github.com/jakubkulhan/bunny/r

    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.

    #php #amqp #reactphp #rabbitmq #bunny #async

  12. Time for a release Friday release: Bunny v0.6.0-alpha.1 is out with a host of changes since v0.5: github.com/jakubkulhan/bunny/r

    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.

    #php #amqp #reactphp #rabbitmq #bunny #async

  13. Time for a release Friday release: Bunny v0.6.0-alpha.1 is out with a host of changes since v0.5: github.com/jakubkulhan/bunny/r

    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.

    #php #amqp #reactphp #rabbitmq #bunny #async

  14. Time for a release Friday release: Bunny v0.6.0-alpha.1 is out with a host of changes since v0.5: github.com/jakubkulhan/bunny/r

    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.

    #php #amqp #reactphp #rabbitmq #bunny #async

  15. Time for a release Friday release: Bunny v0.6.0-alpha.1 is out with a host of changes since v0.5: github.com/jakubkulhan/bunny/r

    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.

    #php #amqp #reactphp #rabbitmq #bunny #async

  16. Started preparing the Bunny 0.6 release post for later this year, GitHub sponsors get a preview in a few days:

    #php #bunny #amqp #rabbitmq #reactphp

  17. Started preparing the Bunny 0.6 release post for later this year, GitHub sponsors get a preview in a few days:

    #php #bunny #amqp #rabbitmq #reactphp

  18. Started preparing the Bunny 0.6 release post for later this year, GitHub sponsors get a preview in a few days:

    #php #bunny #amqp #rabbitmq #reactphp

  19. Started preparing the Bunny 0.6 release post for later this year, GitHub sponsors get a preview in a few days:

    #php #bunny #amqp #rabbitmq #reactphp

  20. Started preparing the Bunny 0.6 release post for later this year, GitHub sponsors get a preview in a few days:

    #php #bunny #amqp #rabbitmq #reactphp

  21. 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: github.com/jakubkulhan/bunny?t

    #PHP #RabbitMQ #ReactPHP #AMQP

  22. 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: github.com/jakubkulhan/bunny?t

    #PHP #RabbitMQ #ReactPHP #AMQP

  23. 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: github.com/jakubkulhan/bunny?t

    #PHP #RabbitMQ #ReactPHP #AMQP

  24. 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: github.com/jakubkulhan/bunny?t

    #PHP #RabbitMQ #ReactPHP #AMQP

  25. 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: github.com/jakubkulhan/bunny?t

    #PHP #RabbitMQ #ReactPHP #AMQP

  26. Currently re-running benchmarks for Bunny to prepare for the first 0.6 alpha/beta. And hot damn, those numbers changed in 10 years. Also running them for php-amqplib to get a fair and proper update. But I'm so hyped for how much those numbers have improved!

    #php #amqp #bunny #reactphp #RabbitMQ

  27. Currently re-running benchmarks for Bunny to prepare for the first 0.6 alpha/beta. And hot damn, those numbers changed in 10 years. Also running them for php-amqplib to get a fair and proper update. But I'm so hyped for how much those numbers have improved!

    #php #amqp #bunny #reactphp #RabbitMQ

  28. Currently re-running benchmarks for Bunny to prepare for the first 0.6 alpha/beta. And hot damn, those numbers changed in 10 years. Also running them for php-amqplib to get a fair and proper update. But I'm so hyped for how much those numbers have improved!

    #php #amqp #bunny #reactphp #RabbitMQ

  29. Currently re-running benchmarks for Bunny to prepare for the first 0.6 alpha/beta. And hot damn, those numbers changed in 10 years. Also running them for php-amqplib to get a fair and proper update. But I'm so hyped for how much those numbers have improved!

    #php #amqp #bunny #reactphp #RabbitMQ

  30. Currently re-running benchmarks for Bunny to prepare for the first 0.6 alpha/beta. And hot damn, those numbers changed in 10 years. Also running them for php-amqplib to get a fair and proper update. But I'm so hyped for how much those numbers have improved!

    #php #amqp #bunny #reactphp #RabbitMQ

  31. Alright, next step in my #OTEL adventure for @reactphp was to add react/cache|dns|socket so I can trace any potential connection issues. Not sure yet what to do next:
    * Event loop
    * react/stream
    * Just add tests to what you have before adding more

    #PHP #ReactPHP

  32. Alright, next step in my #OTEL adventure for @reactphp was to add react/cache|dns|socket so I can trace any potential connection issues. Not sure yet what to do next:
    * Event loop
    * react/stream
    * Just add tests to what you have before adding more

    #PHP #ReactPHP

  33. Alright, next step in my #OTEL adventure for @reactphp was to add react/cache|dns|socket so I can trace any potential connection issues. Not sure yet what to do next:
    * Event loop
    * react/stream
    * Just add tests to what you have before adding more

    #PHP #ReactPHP

  34. Alright, next step in my #OTEL adventure for @reactphp was to add react/cache|dns|socket so I can trace any potential connection issues. Not sure yet what to do next:
    * Event loop
    * react/stream
    * Just add tests to what you have before adding more

    #PHP #ReactPHP

  35. Alright, next step in my #OTEL adventure for @reactphp was to add react/cache|dns|socket so I can trace any potential connection issues. Not sure yet what to do next:
    * Event loop
    * react/stream
    * Just add tests to what you have before adding more

    #PHP #ReactPHP

  36. Score! Managed to hook the cluster at home up to #Grafana #cloud over #OTLP for shipping #traces 🎉 . Next up:
    * Figure out how to do a better presentation in Grafana
    * Optimize OTEL collection deployment, work out all the issues etc

    Then the real fun begins. As I have two WIP packages to bring out:
    * One for @reactphp 's filesystem
    * And one for Bunny

    Both of those need to be refined, but with Shawn Maddock's (github.com/smaddock) initial push in this direction and help

    #php #reactphp

  37. Score! Managed to hook the cluster at home up to #Grafana #cloud over #OTLP for shipping #traces 🎉 . Next up:
    * Figure out how to do a better presentation in Grafana
    * Optimize OTEL collection deployment, work out all the issues etc

    Then the real fun begins. As I have two WIP packages to bring out:
    * One for @reactphp 's filesystem
    * And one for Bunny

    Both of those need to be refined, but with Shawn Maddock's (github.com/smaddock) initial push in this direction and help

    #php #reactphp

  38. Score! Managed to hook the cluster at home up to #Grafana #cloud over #OTLP for shipping #traces 🎉 . Next up:
    * Figure out how to do a better presentation in Grafana
    * Optimize OTEL collection deployment, work out all the issues etc

    Then the real fun begins. As I have two WIP packages to bring out:
    * One for @reactphp 's filesystem
    * And one for Bunny

    Both of those need to be refined, but with Shawn Maddock's (github.com/smaddock) initial push in this direction and help

    #php #reactphp

  39. Score! Managed to hook the cluster at home up to #Grafana #cloud over #OTLP for shipping #traces 🎉 . Next up:
    * Figure out how to do a better presentation in Grafana
    * Optimize OTEL collection deployment, work out all the issues etc

    Then the real fun begins. As I have two WIP packages to bring out:
    * One for @reactphp 's filesystem
    * And one for Bunny

    Both of those need to be refined, but with Shawn Maddock's (github.com/smaddock) initial push in this direction and help

    #php #reactphp

  40. Score! Managed to hook the cluster at home up to #Grafana #cloud over #OTLP for shipping #traces 🎉 . Next up:
    * Figure out how to do a better presentation in Grafana
    * Optimize OTEL collection deployment, work out all the issues etc

    Then the real fun begins. As I have two WIP packages to bring out:
    * One for @reactphp 's filesystem
    * And one for Bunny

    Both of those need to be refined, but with Shawn Maddock's (github.com/smaddock) initial push in this direction and help

    #php #reactphp