[wp-trac] [WordPress Trac] #36335: Next generation: core autoloader proposal

[WordPress Trac]

#36335: Next generation: core autoloader proposal
-----------------------------+------------------
 Reporter:  dnaber-de        |       Owner:
     Type:  feature request  |      Status:  new
 Priority:  normal           |   Milestone:  4.7
Component:  General          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  has-patch        |     Focuses:
-----------------------------+------------------

Comment (by TJNowell):

 It's nice to see somebody playing devils advocate :)

 I would note that a Composer autoloader is not a full copy of Composer,
 and PSR standards autoloaders aren't relevant here as Core doesn't use
 PSR. Composer is being used as a build time tool here much in the way that
 NPM or Grunt might be used, only the final autoloader produced is
 relevant.

 As an aside, Core could include a Composer autoloader if it exists, even
 if it doesn't make use of it internally. This would be a great help for
 those of us who use Composer, eliminating an extra step in the setup, and
 standardising when the autoloader is added.

 The Composer classmap autoloader is widespread and battle tested, I
 believe atm that puts it ahead of homegrown options regardless of best
 practices. If better can be made I'm sure the Composer project will be
 interested in our findings.

 Mike, if you'd like to work on a generator proposal so that we can have
 Composer build an autoloader that matches your own specifications rather
 than those of the Composer project I believe that would be the most
 productive action to take. At that point we can make direct comparisons,
 and perhaps learn things of practical use

--
Ticket URL: <https://core.trac.wordpress.org/ticket/36335#comment:152>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform