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.

Sign up for GitHub

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

Jump to bottom

Compile to wasm instead of js #14

Open

Nimaoth opened this issue Jun 29, 2024 · 0 comments

Labels

Owner

Nimaoth commented Jun 29, 2024 •

edited

Loading

Currently the browser version is based on js

Problems:

Slow (bad Nim->JS codegen, interaction with DOM (technically not necessary))
Optimizations are either good for native and bad for js or the other way round
- E.g. Native prefers object, stack allocation etc., JS prefers ref object and preventing copies
Lots of wrapping around APIs because JS backend and native backend are so different
Issues with big int

Advantages of wasm:

Closer to native backend -> ptr, cast etc work properly
Better performance

Rendering should probably switch to WebGL

Open questions:

How to do interface between WASM <-> JS with async functions

The text was updated successfully, but these errors were encountered:

Nimaoth added the enhancement label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment