Skip to content
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

Open
feynon opened this issue Sep 27, 2023 · 5 comments
Open

What's an appropriate usecase for something like this? #14

feynon opened this issue Sep 27, 2023 · 5 comments

Comments

@feynon
Copy link

feynon commented Sep 27, 2023

No description provided.

@xujuntwt95329
Copy link
Contributor

Hi, the Wasmnizer-ts brings a subset of TypeScript to WebAssembly, it can be used in many areas as long as they need programming capabilities, some typical scenarios include:

  • Application programming language for IoT devices
    Wasmnizer-ts leverage WasmGC, so we don't need to compile a whole language runtime inside WebAssembly, this will make the generated wasm module very small;
  • Application programming language for function computing (FaaS)
    Wasmnizer-ts brings a new choice for developers;
  • A more friendly WebAssembly targeted language for frontend developers
    Wasmnizer-ts doesn't introduce new language, it's just like a new backend for TypeScript, so frontend developer can use WebAssembly without learning C/C++/Rust;

@feynon feynon changed the title Whata an appropriate usecase for something like this? What's an appropriate usecase for something like this? Sep 29, 2023
@feynon
Copy link
Author

feynon commented Sep 29, 2023

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?

@xujuntwt95329
Copy link
Contributor

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. Wasmnizer-ts provides a new choice: the frontend developers can write TypeScript and compiled to WebAssembly without learning a new language.

@feynon
Copy link
Author

feynon commented Sep 30, 2023

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.

@legezam
Copy link

legezam commented Jan 30, 2024

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?

@pgc pgc mentioned this issue Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants