Mark Jaquith
Mark Jaquith
Could md5 the file and store that as post meta, or something.
In fact, we do the same URL thing for everyone. Kind of clever to make it so that you get an editing interface if you tap through, but if you...
An early version had this capability, and I think we'll probably add it back at some point.
@felixarntz yeah, we can check the impact (maybe as % of front page load time taken by this query) at various byte sizes. 250k, 500k, 1m, 2m, say. Would be...
One downside of this proposal is that when you do the weekly calibration run, any options that aren't used on that load will be ejected from autoload, and then moved...
@pbearne Not necessarily. For sites using the default transient PHP memory object cache, we could just look inside the one-by-one object cache to see what got put in there before...
How would we store the registered options and how would we know when they weren't used anymore?
> Registered options will be stored in memory, the same way how other registered entities are stored (an array in the global scope). Hmm. But WordPress queries the autoloaded options...
This issue could use a second look now that APO is in the picture.
The Svelte 5 Preview Repl seems to support TypeScript. Can it be assumed that when Svelte 5 is released, that repl will graduate?