Conversation
`mod_php` (via apache2) has been disrecommended by upstream PHP for years in favor of `php-fpm` (https://www.php.net/manual/en/install.unix.apache2.php). 8.6+ now builds every variant with zts enabled (2e430cd), and `mod_php` gains nothing from that -- it still can't use a threaded MPM, so the added thread-safety overhead is pure cost for zero benefit. Years of disrecommendation plus a new cost with no offsetting benefit is reason enough to drop the variant. Assisted-By: "claude my eyes right out"
|
I'm open to making this 9.0+ instead of 8.6+, but I think going all-in on ZTS is really a compelling lever for making this change too, so IMO 8.6 is the correct place for us to finally flip this and get rid of https://www.php.net/manual/en/install.unix.apache2.php really doesn't mince words here:
That last paragraph seems to imply that enabling ZTS allows switching to a better MPM, but it really doesn't (primarily because other non-PHP libraries need to be thread-safe too for that to work, and they're not necessarily going to be). |
mod_php(via apache2) has been disrecommended by upstream PHP for years in favor ofphp-fpm(https://www.php.net/manual/en/install.unix.apache2.php). 8.6+ now builds every variant with zts enabled (2e430cd), andmod_phpgains nothing from that -- it still can't use a threaded MPM, so the added thread-safety overhead is pure cost for zero benefit. Years of disrecommendation plus a new cost with no offsetting benefit is reason enough to drop the variant.Assisted-By: "claude my eyes right out"