[02:30:34] <ori>	 TimStarling: I noticed LuaSandboxInterpreter::loadString() is slightly more than 1% of index.php wall-clock time. Was bytecode caching ever under consideration for LuaSandbox? LuaSandbox::dump() and loadBinary() suggest the idea crossed your mind but AFAICT they're not used.
[23:12:04] <Krinkle>	 WordPress 6.9 release notes. Always interesting to see how they approach things. Despite their strict ever-lasting soft deprecation and compatibility with WP 0.1, and longer PHP support, they do encourage modern PHP functions through polyfills. https://make.wordpress.org/core/2025/11/17/miscellaneous-developer-focused-changes-in-6-9/
[23:15:01] <Krinkle>	 Simplepie is linked there which demonstrates a Packagist search skywards for PSR providers https://packagist.org/providers/psr/simple-cache-implementation
[23:15:10] <Krinkle>	 search keyword*
[23:16:17] <Krinkle>	 That's a use case I hadn't come across before. Even if interop is of relatively low importance for object cache imho, the discovery is cool.
[23:16:41] <Krinkle>	 I wonder if just being in MW soul out BagOStuff high on page 1.
[23:16:53] <Krinkle>	 would put*
[23:24:19] <apergos>	 for the php-challenged among us, what is meant by "polyfills" ?
[23:26:20] <Krinkle>	 a polyfill is where if a native function isn't defined (ie for an older php version) you define it yourself by the same name. So that the rest of the code and any plugins/extensions can use it unconditionally.
[23:27:41] <apergos>	 apparently it's just a shim :-P
[23:28:17] <Krinkle>	 MW and WP both do this from the highest to the lowest PHP version they support. Any trivial functions supported in PHP 8.2, 8.3, 8.4 we automatically also support down to PHP 8.1 and 8.2 via this polyfill
[23:28:34] <Krinkle>	 Yeah I think the two words can be used interchangeably