-
Couldn't load subscription status.
- Fork 2
Open
Description
I think WASM usage could be improved as follows (sorting short term & quick wins first):
- Have a separate repo for the WASM modules so that the build process that happens in
client-sideis fully traceable (where does the module we're running comes from?). The pipeline could ensure that the modules are versioned as well, do automatic builds, etc. - Use WASM bundles, e.g.
openfhe-bundle.wasmcontains OpenFHE tools,go.wasmcontains the Go stuff, etc. - Implement WASM module compression, e.g. https://github.com/httptoolkit/brotli-wasm
- Probably one for later: look into optimizations with binaryen in case that's not already part of the process.
collapsinghierarchy
Metadata
Metadata
Assignees
Labels
No labels