| 10 Dec 2025 |
 Qyriad | Which helps a lot | 17:46:25 |
 piegames | yes, that's why doing it in Rust will mean interop via RPC and subprocesses (which we want anyways) | 17:46:29 |
 Sergei Zimmerman (xokdvium) | That's the hard part too. I imagine bytecode to not be so compact so that serialising it and persisting would have a big overhead. Needs a policy and profiling to see which code is worth caching at all | 17:46:35 |
 @rosssmyth:matrix.org | There are interpreters in which parsing is on the critical path, but generally they are ones in which data is loaded dynamically. | 20:05:04 |
| @rosssmyth:matrix.org | * There are other interpreters in which parsing is on the critical path, but generally they are ones in which data is loaded dynamically. | 20:05:21 |
 jade_ | we could RPC a thread too | 21:42:54 |
| jade_ | either way is fine tbh | 21:43:00 |
| piegames | long-term the evaluator would be better as a subprocess anyways so I don't see the downsides | 21:43:39 |
| piegames | also it elegantly side-steps the current Rust linking issues | 21:43:48 |
| jade_ | smack the cherry-pick button, get it into the release branch of supported releases, include as patch in nixpkgs if you don't want to wait on someone releng'ing it. | 21:43:55 |
| jade_ | naming a piranha plant stuffie nom chompsky | 21:44:20 |
 helle (just a stray cat girl) | I'll see if I can handle that in the morning, sure | 21:48:29 |
