WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #21170, comment 174


Ignore:
Timestamp:
09/14/2017 10:06:14 PM (22 months ago)
Author:
PeterRKnight
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #21170, comment 174

    initial v1  
    11Regardless of the sudden change of course, will we see the hooks API on npm soon? It would be good to use in plugins right now.
    22
    3 Although it seems reasonable to hold off on this, it is striking how reluctant we are to embrace things that have served WordPress well as we attempt to modernise. Hooks & filters are the bread and butter of extending WordPress, it's one of the most battle tested overwhelmingly successful design patterns but it seems like there's a negative bias against it simply because it is not new? Hooks and filters is something that WordPress has gotten right despite all the flack WordPress gets for its architectural state.
     3Although it seems reasonable to hold off on this, it is striking how reluctant we are to embrace things that have served WordPress well as we attempt to modernise. Hooks & filters are the bread and butter of extending WordPress, it's one of the most battle tested overwhelmingly successful design patterns but it seems like there's a negative bias against it simply because it is not new? Hooks and filters are something that WordPress has gotten right despite all the flack WordPress gets for its architectural state.
    44
    55I'm not sure there is a JS project out there that has achieved the same ease of customization, allowing 3rd parties to modify just about every behaviour and string of an app on the same scale as we find in WordPress. So I don't understand why we've become transfixed with JS frameworks and evolving practices found in projects that don't even begin to resemble or emulate the needs of WordPress. They're not designed for an ecosystem of thousands of plugin and theme developers that want the power to change every piece of behaviour. Instead it seems like we need the blessing of some mythical standard in the JS developer community rather than forging our own decisions based on what we know works, and perhaps even doing things unique to WordPress.