-
Notifications
You must be signed in to change notification settings - Fork 26
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
What's an appropriate usecase for something like this? #14
Comments
Hi, the
|
The first two make sense, for use-cases outside browsers. The last one is somewhat blurry to me. I'm trying to understand it Why would I compile my code to WASM as a frontend developer for frontend usecases? What benefit does that give me when compared to the traditional way? |
In frontend projects, it's very common to build some CPU intensive logic to WebAssembly to get better performance (e.g. photoshop on the web). Currently some statically typed languages such as C/C++/Rust can be successfully compiled to WebAssembly and work well, but the frontend developers are not familiar with these languages. |
Got it, understood. Reminded me of this effort: Typescript as fast as Rust: Typescript++ by Zaplib people, which is discontinued now and discussed in their post mortem blog. |
And how does it compare to AssemblyScript? I get that AssemblyScript is a different language ie it has its own compiler frontend as well, but it is also advertising itself of being a subset of TypeScript. Who and why anyone would choose wasmnizer-ts over AssemblyScript? |
No description provided.
The text was updated successfully, but these errors were encountered: