home.social

#mezzio — Public Fediverse posts

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

fetched live
  1. @Crell @sean @michael Insert shameless plug for #Mezzio middleware microframework ;)

  2. @Crell @sean @michael Insert shameless plug for #Mezzio middleware microframework ;)

  3. @Crell @sean @michael Insert shameless plug for #Mezzio middleware microframework ;)

  4. @Crell @sean @michael Insert shameless plug for #Mezzio middleware microframework ;)

  5. @Crell @sean @michael Insert shameless plug for #Mezzio middleware microframework ;)

  6. Many devs use Laminas and Mezzio, but unfortunately few contribute behind the scenes. We have stepped up, so you should too!
    #PHP #Mezzio
    getlaminas.org/blog/2026-01-14

  7. Many devs use Laminas and Mezzio, but unfortunately few contribute behind the scenes. We have stepped up, so you should too!
    #PHP #Mezzio
    getlaminas.org/blog/2026-01-14

  8. Many devs use Laminas and Mezzio, but unfortunately few contribute behind the scenes. We have stepped up, so you should too!
    #PHP #Mezzio
    getlaminas.org/blog/2026-01-14

  9. Many devs use Laminas and Mezzio, but unfortunately few contribute behind the scenes. We have stepped up, so you should too!
    #PHP #Mezzio
    getlaminas.org/blog/2026-01-14

  10. Many devs use Laminas and Mezzio, but unfortunately few contribute behind the scenes. We have stepped up, so you should too!
    #PHP #Mezzio
    getlaminas.org/blog/2026-01-14

  11. @shochdoerfer @bitexpert At #laminas and #mezzio, we set `config.platform.php` to an imaginary maximum patch version of the minimum supported version of php, such as `8.2.99`, so regardless of the PHP version renovate uses, composer will always resolve the correct dependencies. Possibly a different solution, also potentially solving a different problem!

  12. @shochdoerfer @bitexpert At #laminas and #mezzio, we set `config.platform.php` to an imaginary maximum patch version of the minimum supported version of php, such as `8.2.99`, so regardless of the PHP version renovate uses, composer will always resolve the correct dependencies. Possibly a different solution, also potentially solving a different problem!

  13. @shochdoerfer @bitexpert At #laminas and #mezzio, we set `config.platform.php` to an imaginary maximum patch version of the minimum supported version of php, such as `8.2.99`, so regardless of the PHP version renovate uses, composer will always resolve the correct dependencies. Possibly a different solution, also potentially solving a different problem!

  14. @shochdoerfer @bitexpert At #laminas and #mezzio, we set `config.platform.php` to an imaginary maximum patch version of the minimum supported version of php, such as `8.2.99`, so regardless of the PHP version renovate uses, composer will always resolve the correct dependencies. Possibly a different solution, also potentially solving a different problem!

  15. @shochdoerfer @bitexpert At #laminas and #mezzio, we set `config.platform.php` to an imaginary maximum patch version of the minimum supported version of php, such as `8.2.99`, so regardless of the PHP version renovate uses, composer will always resolve the correct dependencies. Possibly a different solution, also potentially solving a different problem!

  16. @josh

    That’s a valid choice, if latency is already “good enough.”

    But runtime cost doesn’t magically disappear behind a CDN.

    Every request still has a cost, and sooner or later one slow response will lose you (or your clients) a customer.

    #Laravel absolutely wins on dev velocity.

    Anyone with patience and #YouTube (or #AI) can ship something fast, often with little understanding of the framework or even the #PHP language.

    #Mezzio wins when runtime, scale, and longevity actually matter.

  17. @josh

    That’s a valid choice, if latency is already “good enough.”

    But runtime cost doesn’t magically disappear behind a CDN.

    Every request still has a cost, and sooner or later one slow response will lose you (or your clients) a customer.

    #Laravel absolutely wins on dev velocity.

    Anyone with patience and #YouTube (or #AI) can ship something fast, often with little understanding of the framework or even the #PHP language.

    #Mezzio wins when runtime, scale, and longevity actually matter.

  18. @josh

    That’s a valid choice, if latency is already “good enough.”

    But runtime cost doesn’t magically disappear behind a CDN.

    Every request still has a cost, and sooner or later one slow response will lose you (or your clients) a customer.

    #Laravel absolutely wins on dev velocity.

    Anyone with patience and #YouTube (or #AI) can ship something fast, often with little understanding of the framework or even the #PHP language.

    #Mezzio wins when runtime, scale, and longevity actually matter.

  19. @josh

    That’s a valid choice, if latency is already “good enough.”

    But runtime cost doesn’t magically disappear behind a CDN.

    Every request still has a cost, and sooner or later one slow response will lose you (or your clients) a customer.

    #Laravel absolutely wins on dev velocity.

    Anyone with patience and #YouTube (or #AI) can ship something fast, often with little understanding of the framework or even the #PHP language.

    #Mezzio wins when runtime, scale, and longevity actually matter.

  20. @lo_fye

    #Mezzio’s ecosystem is the PHP-FIG / PSR ecosystem, not a framework-specific one.

    You don’t get:

    one blessed ORM
    one queue system
    one auth package
    one “#Laravel way”
    vendor lock-in

    You do get:

    PSR-7/15/17 (HTTP)
    PSR-11 (DI)
    PSR-14 (Events)
    PSR-3 (logging)
    PSR-6/16 (cache)
    PSR-18 (HTTP client)
    PSR-20 (clock)

    Which means you can plug in:

    Doctrine or Eloquent or PDO
    Laminas Cache or Symfony Cache
    Monolog or anything PSR-3
    Any PSR-15 middleware

    Different priorities

  21. @lo_fye

    #Mezzio’s ecosystem is the PHP-FIG / PSR ecosystem, not a framework-specific one.

    You don’t get:

    one blessed ORM
    one queue system
    one auth package
    one “#Laravel way”
    vendor lock-in

    You do get:

    PSR-7/15/17 (HTTP)
    PSR-11 (DI)
    PSR-14 (Events)
    PSR-3 (logging)
    PSR-6/16 (cache)
    PSR-18 (HTTP client)
    PSR-20 (clock)

    Which means you can plug in:

    Doctrine or Eloquent or PDO
    Laminas Cache or Symfony Cache
    Monolog or anything PSR-3
    Any PSR-15 middleware

    Different priorities

  22. @lo_fye

    #Mezzio’s ecosystem is the PHP-FIG / PSR ecosystem, not a framework-specific one.

    You don’t get:

    one blessed ORM
    one queue system
    one auth package
    one “#Laravel way”
    vendor lock-in

    You do get:

    PSR-7/15/17 (HTTP)
    PSR-11 (DI)
    PSR-14 (Events)
    PSR-3 (logging)
    PSR-6/16 (cache)
    PSR-18 (HTTP client)
    PSR-20 (clock)

    Which means you can plug in:

    Doctrine or Eloquent or PDO
    Laminas Cache or Symfony Cache
    Monolog or anything PSR-3
    Any PSR-15 middleware

    Different priorities

  23. @lo_fye

    #Mezzio’s ecosystem is the PHP-FIG / PSR ecosystem, not a framework-specific one.

    You don’t get:

    one blessed ORM
    one queue system
    one auth package
    one “#Laravel way”
    vendor lock-in

    You do get:

    PSR-7/15/17 (HTTP)
    PSR-11 (DI)
    PSR-14 (Events)
    PSR-3 (logging)
    PSR-6/16 (cache)
    PSR-18 (HTTP client)
    PSR-20 (clock)

    Which means you can plug in:

    Doctrine or Eloquent or PDO
    Laminas Cache or Symfony Cache
    Monolog or anything PSR-3
    Any PSR-15 middleware

    Different priorities

  24. @lo_fye

    #Mezzio’s ecosystem is the PHP-FIG / PSR ecosystem, not a framework-specific one.

    You don’t get:

    one blessed ORM
    one queue system
    one auth package
    one “#Laravel way”
    vendor lock-in

    You do get:

    PSR-7/15/17 (HTTP)
    PSR-11 (DI)
    PSR-14 (Events)
    PSR-3 (logging)
    PSR-6/16 (cache)
    PSR-18 (HTTP client)
    PSR-20 (clock)

    Which means you can plug in:

    Doctrine or Eloquent or PDO
    Laminas Cache or Symfony Cache
    Monolog or anything PSR-3
    Any PSR-15 middleware

    Different priorities

  25. Laravel avg response: ~250ms
    Mezzio avg response: ~45ms

    Same app. Same 12 routes. Routing + Response emission.

    Laravel: 12 invokable controllers
    Mezzio: 12 PSR-15 handlers

    #Laravel optimizes dev time.

    #Mezzio optimizes runtime.

    - Minimal bootstrap.
    - PSR-15 request pipeline, no magic.
    - No ORM unless you add one.
    - No global helpers, no facade resolution.
    - Handlers are plain objects with predictable lifecycles.

    Framework choice = real latency cost.

    #PHP

  26. Laravel avg response: ~250ms
    Mezzio avg response: ~45ms

    Same app. Same 12 routes. Routing + Response emission.

    Laravel: 12 invokable controllers
    Mezzio: 12 PSR-15 handlers

    #Laravel optimizes dev time.

    #Mezzio optimizes runtime.

    - Minimal bootstrap.
    - PSR-15 request pipeline, no magic.
    - No ORM unless you add one.
    - No global helpers, no facade resolution.
    - Handlers are plain objects with predictable lifecycles.

    Framework choice = real latency cost.

    #PHP

  27. Laravel avg response: ~250ms
    Mezzio avg response: ~45ms

    Same app. Same 12 routes. Routing + Response emission.

    Laravel: 12 invokable controllers
    Mezzio: 12 PSR-15 handlers

    #Laravel optimizes dev time.

    #Mezzio optimizes runtime.

    - Minimal bootstrap.
    - PSR-15 request pipeline, no magic.
    - No ORM unless you add one.
    - No global helpers, no facade resolution.
    - Handlers are plain objects with predictable lifecycles.

    Framework choice = real latency cost.

    #PHP

  28. Laravel avg response: ~250ms
    Mezzio avg response: ~45ms

    Same app. Same 12 routes. Routing + Response emission.

    Laravel: 12 invokable controllers
    Mezzio: 12 PSR-15 handlers

    #Laravel optimizes dev time.

    #Mezzio optimizes runtime.

    - Minimal bootstrap.
    - PSR-15 request pipeline, no magic.
    - No ORM unless you add one.
    - No global helpers, no facade resolution.
    - Handlers are plain objects with predictable lifecycles.

    Framework choice = real latency cost.

    #PHP

  29. Laravel avg response: ~250ms
    Mezzio avg response: ~45ms

    Same app. Same 12 routes. routing + response emission.

    Laravel: 12 invokable controllers
    Mezzio: 12 PSR-15 handlers

    Laravel optimizes dev time.

    #Mezzio optimizes runtime.

    - Minimal bootstrap.
    - PSR-15 request pipeline, no magic.
    - No ORM unless you add one.
    - No global helpers, no facade resolution.
    - Handlers are plain objects with predictable lifecycles.

    Framework choice = real latency cost.

  30. Create modules in seconds with Dotkernel DotMaker. It handles the file consistency and you can focus on your code.
    #PHP #mezzio
    shorturl.at/kBm3i

  31. Create modules in seconds with Dotkernel DotMaker. It handles the file consistency and you can focus on your code.
    #PHP #mezzio
    shorturl.at/kBm3i

  32. Create modules in seconds with Dotkernel DotMaker. It handles the file consistency and you can focus on your code.
    #PHP #mezzio
    shorturl.at/kBm3i

  33. Create modules in seconds with Dotkernel DotMaker. It handles the file consistency and you can focus on your code.
    #PHP #mezzio
    shorturl.at/kBm3i

  34. PHP DebugBar + REPL module for Mezzio Framework

    For real-time debugging, profiling, and experimenting with your app's internals.

    Built with:

    🔹 PHP DebugBar (php-debugbar/php-debugbar)
    🔹 Plates (thephpleague/plates)
    🔹 PsySH (bobthecow/psysh)]

    #PHP #Mezzio #DebugBar #REPL #Debugging #DeveloperTools #PHP8 #Frameworks

  35. PHP DebugBar + REPL module for Mezzio Framework

    For real-time debugging, profiling, and experimenting with your app's internals.

    Built with:

    🔹 PHP DebugBar (php-debugbar/php-debugbar)
    🔹 Plates (thephpleague/plates)
    🔹 PsySH (bobthecow/psysh)]

    #PHP #Mezzio #DebugBar #REPL #Debugging #DeveloperTools #PHP8 #Frameworks

  36. PHP DebugBar + REPL module for Mezzio Framework

    For real-time debugging, profiling, and experimenting with your app's internals.

    Built with:

    🔹 PHP DebugBar (php-debugbar/php-debugbar)
    🔹 Plates (thephpleague/plates)
    🔹 PsySH (bobthecow/psysh)]

    #PHP #Mezzio #DebugBar #REPL #Debugging #DeveloperTools #PHP8 #Frameworks

  37. PHP DebugBar + REPL module for Mezzio Framework

    For real-time debugging, profiling, and experimenting with your app's internals.

    Built with:

    🔹 PHP DebugBar (php-debugbar/php-debugbar)
    🔹 Plates (thephpleague/plates)
    🔹 PsySH (bobthecow/psysh)]

    #PHP #Mezzio #DebugBar #REPL #Debugging #DeveloperTools #PHP8 #Frameworks

  38. @julian `netglue/laminas-messenger` doesn't ship any middleware, or anything #Mezzio specific really - it's just factories, config and wiring for #Laminas ServiceManager DI really…

  39. @julian `netglue/laminas-messenger` doesn't ship any middleware, or anything #Mezzio specific really - it's just factories, config and wiring for #Laminas ServiceManager DI really…

  40. @julian `netglue/laminas-messenger` doesn't ship any middleware, or anything #Mezzio specific really - it's just factories, config and wiring for #Laminas ServiceManager DI really…

  41. @julian `netglue/laminas-messenger` doesn't ship any middleware, or anything #Mezzio specific really - it's just factories, config and wiring for #Laminas ServiceManager DI really…