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

 I think I'm still missing something important here.

 Classes autoloading is very nice for OOP apps. However WordPress is
 **not** an OOP app. It's true, there are about 200 classes. Many of them
 are just containers for namespacing the functions inside. These are not
 meant to be extended or used in any OOP way.

 There are also about 4750 "loose" functions. What does autoloading do for
 them?

 As far as I see autoloading is **maybe nice to have** for the couple of
 hundred classes in WordPress. We can certainly do that when the minimum
 required PHP version allows it. However using a "side" functionality of a
 third party app to add this now seems premature. Also considering all the
 things that are breaking. I don't see the big benefits from doing this.

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