WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #36335, comment 182


Ignore:
Timestamp:
09/06/2016 02:19:24 PM (4 years ago)
Author:
chrisvanpatten
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #36335, comment 182

    initial v1  
    88If the goal is to—over dozens of cycles—make WordPress more consistent with generally accepted PHP best practices, what's the gain right now from putting in code—and creating technical debt—that's out of line with those best practices?
    99
    10 I'm not saying there isn't merit to a non-Composer autoloader, just that it seems like this is the kind of thing where it might be better to avoid an autoloader entirely and push for improvements in other areas… renaming classes, getting some kind of consistent hierarchy in place, pushing for 5.3 version minimum and namespaces, etc. That might take a while, but it seems like that groundwork is necessary anyway to really get the _most_ value out of an autoloader.
     10I'm not saying there isn't merit to a non-Composer autoloader, just that it seems like this is the kind of thing where it might be better to avoid an autoloader entirely and push for improvements in other areas… renaming classes, getting some kind of consistent hierarchy in place, pushing for 5.3 version minimum and namespaces, etc. That might take a while, but it seems like that groundwork is necessary anyway to really get the _most_ value out of any autoloader, whether custom or Composer-based.