WordPress.org

Make WordPress Core

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


Ignore:
Timestamp:
09/13/2017 06:39:39 PM (2 years ago)
Author:
dd32
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #21170, comment 153

    initial v1  
    22
    335 years ago, I think this would've been a great addition to the state of Javascript in WordPress - taking a concept WordPress developers were familiar with and providing a similar mechanism for the jumbled random pieces of Javascript inserted by all sorts of things, and actually getting it to all work together cohesively.
    4 But it's not 5 years ago, it's now 2017 and WordPress is behind the curve on modern Javascript adoption, we're playing catch up and we need to be looking at what will be useful over the coming ten years, and not just what has proved reliable in the past.
     4But it's not 5 years ago, it's now 2017 and WordPress is behind the curve on modern Javascript adoption, we're playing catch up and we need to be looking at what will be useful over the coming 10 years, and not just what has proved reliable in the past.
    55
    66The good news is that I don't think this patch/approach is incorrect or bad at all - Hooks & filters have certainly proved to be reliable in PHP, I just don't want us to run forward into adopting something which is based on historical JS usage in WordPress rather than future JS usage.