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

 Replying to [comment:156 MikeSchinkel]:
 > 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.

 I'm not sure I follow or agree here.  I maintain that the vast majority
 whom are new to WordPress and to PHP _really_ don't care how an auto
 loader in core gets constructed.  They just care that core works, full
 stop.  Nothing about an autoloader in core increases the technical hurdle
 for the vast majority doing all the things they do with WordPress. By the
 time they care about core, they're at least at my level (Unrelated but you
 probably over-estimate my PHP skills, I've been around WP a long time and
 can figure things out by I'm a hack).

 The vast majority that touch PHP just tweak themes, and maybe right a
 simple functional plugins. Nothing about that space changes with an
 autoloader in core, let alone how an auto loader gets constructed.

 > 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.

 Certainly, adding composer for composer's sake should get discussed
 elsewhere and I certainly didn't mean to derail into that. Just as I said
 above, I don't think a composer vs non-composer autoloader makes a
 technical difference for anyone looking into core for the first time.

 FWIW, the interface vs. implementation abstraction seems way more
 complicated to me but I could figure it out and after a lot of years I've
 learned to embrace such abstractions.

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