| 10 Dec 2025 |
 piegames | we won't get much faster than that (though I expect that a parse that can directly emit Bytecode should be a little bit faster still because more compact representation), but the Rust rewrite still needs to be at least as fast as now and that's no small feat | 17:23:20 |
| piegames | * we won't get much faster than that (though I expect that a parser that can directly emit Bytecode should be a little bit faster still because more compact representation), but the Rust rewrite still needs to be at least as fast as now and that's no small feat | 17:23:45 |
 Rutile (rootile) | In reply to @piegames:flausch.social
we won't get much faster than that (though I expect that a parser that can directly emit Bytecode should be a little bit faster still because more compact representation), but the Rust rewrite still needs to be at least as fast as now and that's no small feat Could the rust version be possibly be writtten with cache in mind from the beginning? | 17:25:15 |
| piegames | yes, but the issue is, what is your cache key? | 17:25:37 |
| piegames | inode number and ctime might be our best bet | 17:28:31 |
| piegames | but in terms of cachable data structures, bytecode gives us that for free | 17:29:02 |
| piegames | * but in terms of cachable data structures, bytecode gives us that bit for free | 17:29:28 |
 Charles | In reply to @piegames:flausch.social
yes, but the issue is, what is your cache key? What do other interpreters do? | 17:31:54 |
| piegames | I don't think any other interpreters have comparable performance requirements for parsing | 17:33:30 |
| piegames | if there constraints weren't as tight we could just go content-addressed and use a hash | 17:33:43 |
 Qyriad | bytecode is our::Qyriad's long term goal | 17:35:18 |
| Qyriad | or really whenever someone pays us for it | 17:35:25 |
| Qyriad | * or whenever someone pays us for it | 17:35:36 |
| piegames | I think browser engines have sufficient control over their baseline caching pipelines and what data changes when that they can probably just track what changes easily, but I'm guessing here | 17:36:08 |
