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

 Replying to [comment:155 jb510]:
 > As one of the those in the "different levels of programmers" group. I
 don't see how adding an autoloader to core would hurt my ability, or my
 fellow novice and intermediates, from working with WordPress.

 You misunderstood my comments. I would definitely like to see an
 autoloader added to WordPress. I proposed one 22 months ago
 [https://core.trac.wordpress.org/ticket/30203 here on Trac].  Instead I
 have an objection to the use of Composer as I believe it is a poor fit for
 use with WordPress.

 > In fact I feel like most new developers are coming to WP having learned
 current best practices elsewhere (Zend/Laravelle) so they are more
 confused when they discover WP doesn't do things more modern (advanced)
 way.

 You are definitely not in the majority of people working with WordPress
 and thus I did not include your archetype in the list above. My experience
 you represent a very tiny percent of people who are new to WordPress; most
 people new to WordPress were not previously PHP developers.   AND you also
 represent a group of people who ''(hopefully would)'' have the skills to
 figure things out vs. those who first learned PHP in order to theme
 WordPress or write a plugin for WordPress.

 > A point I'm unclear on at this point in the discussion is about use
 outside of core which I think needs at least superficial
 consideration....If the answer is based on composer. Is the thought that
 plugin/theme developers could then leverage composer directly from core to
 create their own auto-loader, or is the thought that they would directly
 use a Core autoloader class?  As a middle level dev, I only really care
 about two things, 1) that how core does it works seamlessly and
 painlessly, and 2) if I can/can't/should/shouldn't leverage how core does
 it.

 Those are great questions, and ones I am definitely not clear on either.

 But I do think to discuss Composer it should be done on a ticket that
 provides the proposal clearly in the title and description of the ticket.

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