[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:182 chrisvanpatten]:
 > If 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?

 Is that an actual explicitly stated goal of the WordPress project?

 After 7 years of working with WordPress professionally ''(and numerous
 programming languages before WordPress)'' I have come to the conclusion
 that WordPress best practices and PHP best practices are often at odds
 with one-another.  As such IMO trying to force PHP best practices on
 WordPress will ultimately do more harm to WordPress than benefit it.
 Especially related to integrating Composer into core. JMTCW.

 So before we power ahead trying to make WordPress follow PHP best
 practices when they are obviously at odds with the WordPress way we should
 get the core team to explicitly embrace that direction, and a good place
 to do it would be here:

 - https://wordpress.org/about/philosophy/

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