Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #60414, comment 49


Ignore:
Timestamp:
06/04/2026 02:32:29 PM (2 months ago)
Author:
tha_sun

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #60414, comment 49

    initial v1  
    55**Motivation and scope**
    66
    7 The primary motivation is bootstrap performance. On large-scale, high-traffic sites I have implemented custom front controllers that strip unnecessary file includes from the default bootstrap reduce response times by 500ms or more on AJAX and REST API requests — code paths that never use 90% of the classes WordPress eagerly requires. A native classmap autoloader in core eliminates that overhead without requiring site-specific hacks, and provides the infrastructure for further lazy-loading improvements downstream.
     7The primary motivation is bootstrap performance. On large-scale, high-traffic sites I have implemented custom front controllers that strip unnecessary file includes from the default bootstrap significantly reduce response times on AJAX and REST API requests — code paths that never use 90% of the classes WordPress eagerly requires. A native classmap autoloader in core eliminates that overhead without requiring site-specific hacks, and provides the infrastructure for further lazy-loading improvements downstream.
    88
    99I support the intentionally minimal scope to maximize the chance of acceptance: