Login
You're viewing the assemblag.es public feed.
  • Gina Peter BanyardGirgias@phpc.social
    Sep 6, 2026, 10:22 AM

    Spitting out that contributing upstream feels like it is not worth your effort, even if it would help everyone, because you can't use it for years due to supporting ancient versions is one of the reasons why WP is seen as holding PHP back.

    I've only ever seen WP developers use Rector to *downgrade* their PHP code as they want to write modern code. Nobody asked you to maintain PHP 5.2 compat in 2019 (for WP 5.1). For context this means no namespaces, as this is a PHP 5.3 feature.

    💬 2🔄 0⭐ 0

Replies

  • Gina Peter BanyardGirgias@phpc.social
    Sep 6, 2026, 10:25 AM

    So really if WP cannot be bothered to engage with Internals, attempt to upstream features that would be useful to them and the rest of the ecosystem, and wants to support ancient versions for business reasons, why should I, a PHP core developer trying to move the language forward, engage with WordPress? I'm not going to spend my time trying to understand the ecosystem and find ways to improve it when I could do literally anything else with more cooperative parts of the ecosystem.

    💬 0🔄 1⭐ 2
  • Steve Grunwellstevegrunwell@phpc.social
    Sep 6, 2026, 6:17 PM

    @Girgias I gave a talk at WordCamp Detroit in 2019 entitled "A Crash-course in PHP Namespaces for WordPress Developers", and there were definitely some folks who were *amazed* that we didn't have to live in a world of "pluginname_function_name()"

    That talk was seven years ago, and we've had namespaces in #PHP for SEVENTEEN YEARS!

    💬 0🔄 0⭐ 0