[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 schlessera):

 Replying to [comment:184 schlessera]:
 > As I find it very difficult to assess whether there's even any real
 interest in having an autoloader, I created a (non-binding !) Twitter poll
 to get a better overview. I would welcome anyone interested in the topic
 to leave their vote:
 > https://twitter.com/schlessera/status/773178479953272834

 The poll was running for a whole week and we now have the final voting
 results:

 [[Image(https://www.alainschlesser.com/wp-
 content/uploads/2016/09/Screenshot-2016-09-14-20.55.22.png)]]

 As the poll was meant to get reactions from developers, I think that
 participation was not too bad:

 [[Image(https://www.alainschlesser.com/wp-
 content/uploads/2016/09/Screenshot-2016-09-14-21.03.21.png)]]

 Assuming that the result is at least _somewhat_ representative, it let's
 us conclude the following:

 1. There's a general agreement that an autoloader is needed within Core
 and the the time is right.
 2. The majority prefers the Composer-provided autoloader over a custom-
 built one.

 It was decided to continue evaluating an implementation as a feature
 project, but I still wanted to add the results of this poll to the ticket
 for later reference.

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