[wp-trac] [WordPress Trac] #32845: Introduce wp_include()

[WordPress Trac]

#32845: Introduce wp_include()
-----------------------------+-----------------------
 Reporter:  johnjamesjacoby  |       Owner:
     Type:  feature request  |      Status:  reopened
 Priority:  normal           |   Milestone:
Component:  Plugins          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  close            |     Focuses:
-----------------------------+-----------------------

Comment (by johnjamesjacoby):

 Thanks everyone that gave feedback so far. I have some responses that I'll
 bullet below, because I find Trac's quote styling to be pretty terrible
 and difficult to grok.

 * BuddyPress & bbPress are both *fully* pluggable, in that even the base
 class can be unhooked and replaced (as if `wp();` could do the same
 thing.)
 * The file inclusion vs. load order is an issue. Ideally plugin.php would
 be moved higher up to be more accommodating in this regard (I had
 originally had it hacked around more, but wanted to minimize the footprint
 for the sake of making the intent a bit more clear.)
 * In my experience, rarely if ever do functions relocate anyways, for the
 reasons stated in this ticket. See also #21788 where I've championed
 something fairly innocuous for 3 years. This function makes where
 functions live less important, IMO, and instead forces everyone to
 consider the WordPress development environment for exactly what it's
 always been: unpredictable. Actions and filters are creating technical
 debt, and a library and lexicon of calculated intercept points that need
 some kind of blessing and blue moon to make happen. See #23016.
 * Being told to fork WordPress one day, and being steered away from
 forking BackPress another, is I guess a topic dorky blog and not for Trac,
 but consider that it seems there's no third option, which is make
 WordPress more flexible. Cake or death, basically.
 * It's fine with me if the core team thinks this is truly a horrible idea
 and wants to tuck it under the rug, but I'm still not sure I completely
 agree with that assessment, and would like to see/help the project get to
 a more flexible and decoupled place.
 * The pluggable nature of BuddyPress & bbPress has not introduced any
 additional burden on those respective teams, nor has it pigeonholed us
 from improving the software over time. If anything, no one even knows it's
 possible to do.

 Feel free to close this again if y'all want. I'll figure out another
 solution that is less impactful to core.

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