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

[V8 team proposal] The future of WebAssembly #4

Closed
mathiasbynens opened this issue Oct 6, 2017 · 4 comments
Closed

[V8 team proposal] The future of WebAssembly #4

mathiasbynens opened this issue Oct 6, 2017 · 4 comments
Labels

Comments

@mathiasbynens
Copy link

mathiasbynens commented Oct 6, 2017

Session Title:
The future of WebAssembly

Session Abstract:

Discuss current threading proposal:

  • Roughly equivalent to SharedArrayBuffer + Web Workers
  • Atomics and futexes give native-level performance for low-level concurrency
  • Still in “WASM is a machine” style, no new concurrency constructs
  • Why is this hard for anything other than low-level shared memory?

Current thinking on integration with the DOM/JS:

  • Opaque references to JS objects can flow through WASM code
  • Access must be accomplished through imported JavaScript functions

Approximate Duration:
30 minutes

Your Name:
Ben Titzer

Your Twitter handle:
v8js

Requirements:
[x] No
[ ] Yes => Please share what do you need.

Complexity:
[ ] Advanced
[x] Intermediate
[x] Beginner

@mathiasbynens
Copy link
Author

For Nov 13.

@littledan
Copy link

FWIW I'm starting out getting involved in Wasm; I could come if it is helpful, but nowhere near as much of an expert as Ben.

@flaki
Copy link

flaki commented Oct 30, 2017

/cc @badboy

@jhnns
Copy link

jhnns commented Nov 2, 2017

There's some overlap with #9 but I still think it's better to keep them separated.

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

No branches or pull requests

5 participants