4 ms·

Thanks again for this. My goals are: Deep copy value passing semantics by default (with outs for hotpath and some optimization). Persistence by default using

Thanks again for this. My goals are: Deep copy value passing semantics by default (with outs for hotpath and some optimization). Persistence by default using SQLite. (Again, opt out for hot paths). Lua tables, but callable. Also every object is a continuation. Optimizations for js are float64 arrays with the 0 index holding some meta stuff - but semantically just objects and messages. No variables, just fields. Fields can be thought of as canned message responses. Fallthrough is “call”.

Rochus 5mo ago
When you consider SQLite, you might want to get around SQL for impedance and performance reasons. There is a robust and decently fast key/value store in the backend. I used it in some of my projects (e.g. https://github.com/rochus-keller/udb https://github.com/rochus-keller/udb used e.g. in https://github.com/rochus-keller/crossline/ https://github.com/rochus-keller/crossline/). Depending on read/write frequency, lmdb or tidesdb might be a better fit.
- NuclearPM 5mo ago
  This is cool. I wonder if WASM would work here as a target for the k/v store.