-
-
Notifications
You must be signed in to change notification settings - Fork 377
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EXP] with-wasm #102
Comments
Would be great if the community can spearhead this :) - I think plasmo has most of the tooling needed to support wasm, i.e via web accessible resource and the url scheme. |
Watch this repo: https://github.com/PlasmoHQ/with-wasm-zig We're learning zig boiiii (and zig -> wasm too kek) |
Once the setup is done, if it's lean enough we might just throw it in our |
@lolimay the zig experimentation is done for stage 1. Feel free to checkout the repo linked above. I noted a tons of work that we can do to improve the DX for zig <-> ts (via wasm). If anyone would like to help out, pls chime in on the discord :D |
How do you envision this feature/change to look/work like?
Provide "out-of-box" support for WASM integration.
Web Assembly (Wasm) Support (Integration & Recipes)
What is the purpose of this change/feature? Why?
For some performance sensitive cases, like video encoding/decoding, WASM does matter.
I made a benchmark for base64 encoding/decoding before (rust WASM version is 6X faster than pure JavaScript version on my macbook m1). Another example is that tf.js blogged how WASM helped them get 10X performance improvement.
It will be great if we can provide some "out-of-box" integration for WASM. The "integration" could be example projects, APIs , some recipes (Best Practices for instance) in the documentation even a Javascript/Rust hybird project template.
(OPTIONAL) Example implementations
No response
(OPTIONAL) Contact Details
No response
Verify canary release
plasmo
canary releaseCode of Conduct
The text was updated successfully, but these errors were encountered: