Skip to content

Where possible, we should move JavaScript to native/wasm code #15151

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

Open
sbc100 opened this issue Sep 27, 2021 · 1 comment
Open

Where possible, we should move JavaScript to native/wasm code #15151

sbc100 opened this issue Sep 27, 2021 · 1 comment

Comments

@sbc100
Copy link
Collaborator

sbc100 commented Sep 27, 2021

This is meta-issue for ongoing work for move as much code as possible out of JavaScript
and into C/C++.

In particular it would be good to focus of code that does HEAP access from JavaScript.
Doing this instead from native code has several advantages:

  • The syntax for heap access in JS much harder to read and write
  • JS heap access is currently slow when using ALLOW_MEMORY_GROWTH and USE_PTHREADS
  • Supporting wasm32 and wasm64 with the same JS code adds complexity ([wasm64] making JS bindings wasm64 aware #12869)
@sbc100 sbc100 changed the title Where possible we should move JavaScript to native/wasm code Where possible, we should move JavaScript to native/wasm code Sep 28, 2021
@sbc100
Copy link
Collaborator Author

sbc100 commented Jun 28, 2024

See #21379 and #22158

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

1 participant