Skip to content

WASM usage #10

@matiasinsaurralde

Description

@matiasinsaurralde

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-side is 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.wasm contains OpenFHE tools, go.wasm contains 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions