Ability to use as a framework

[ttodua]

WordPress provides more than 600+ framework-like functions (get_option/set_option, transcients, sanitize-functions and more, which ​are seen in test).
I doubt that there may be other people like our company, where we use WordPress as a backend helper framework, to make use of it's goodies (hundreds of useful functions).

As speed & performance matter, people has asked for this feature many times (i.e. ​example1 or ​example2)

It might be some useful to have one additional alternative for "SHORTINIT" constant:

• SHORTINIT_WITHOUT_DB (to return from "wp-settings.php" right before require_wp_db())

# Performance gains #
Per my tests, compared to SHORTINIT, this approach loads wp-core about 10x faster (avoiding DB calls, etc).

Attaching the patches.

[ttodua]

To test simply:

$x= microtime(true);
define('SHORTINIT_WITHOUT_DB', true);  //as opposed to define('SHORTINIT', true); 
require(__DIR__."/src/wp-load.php");
var_dump(  microtime(true)- $x );

[sabernhardt]

Related: #41783

[jorbin]

This doesn't feel like it fits the current goals of WordPress as a project. SHORTINIT is already undertested, adding a new constant that adds yet another consideration for how files are loaded will make it harder to change the load process. I suggest that this is closed as wontfix.

[jorbin]

Meant to leave it open for discussion (hence the 2nd-opion keyword), so reopening.

[desrosj]

Thanks for this suggestion @ttodua! However, I agree with @jorbin's assessment above, so I'm going to close this one out.

Discussion can always continue on closed tickets, and they can be reopened in the future should conditions change.