Skip to content

Add notes for 2021-08 plenary #153

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

Merged
robpalme merged 12 commits into from
Sep 21, 2021
Merged

Add notes for 2021-08 plenary #153

Changes from 1 commit
Commits
Show all changes
12 commits
Select commit Hold shift + click to select a range
1f48e90
Add notes for 2021-08 plenary
robpalme Sep 16, 2021
903e8a0
Update aug-31.md
js-choi Sep 16, 2021
4aadfae
Update aug-31.md
js-choi Sep 16, 2021
574fd95
Update sept-01.md
js-choi Sep 16, 2021
c680ab4
Update meetings/2021-08/sept-01.md
robpalme Sep 17, 2021
225f869
Update meetings/2021-08/sept-01.md
robpalme Sep 17, 2021
94b95ed
Update meetings/2021-08/sept-01.md
robpalme Sep 17, 2021
a88729a
Update meetings/2021-08/sept-01.md
robpalme Sep 17, 2021
00d8d7c
Update meetings/2021-08/sept-01.md
robpalme Sep 17, 2021
d71b16a
Update meetings/2021-08/sept-01.md
robpalme Sep 17, 2021
07b4c7e
Update meetings/2021-08/sept-01.md
robpalme Sep 17, 2021
bb3c92b
Update meetings/2021-08/sept-01.md
robpalme Sep 17, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update meetings/2021-08/sept-01.md 
Co-authored-by: Jack Works <[email protected]>
  • Loading branch information
@robpalme @Jack-Works
robpalme and Jack-Works authored Sep 17, 2021
commit 07b4c7ee2588e7b0d91f56319fc484fac62866ce
2 changes: 1 addition & 1 deletion meetings/2021-08/sept-01.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -500,7 +500,7 @@ SYG: Thank you, Mark, for your perspective. It’s somewhat of a philosophical d

MM: I was reluctant to approve SharedArrayBuffers. And the reason I approved it is that the pressure from games made it seem like it was inevitable that whether TC39 approved it or not. All the browsers were going to implement it and games were going to use it. And then far, the reason that we’re still in a good place is basically because SharedArrayBuffers has been a resounding adoption disaster. People don’t use it. And hopefully they will continue to be an adoption disaster and anything that makes shared memory multithreading usable will make it more adoptable, which will be a strict backward motion from the current state where people could use it and destroy safety properties, in theory. But right now, at least they’re not.

JWK: One of the primary use cases for shared memory and shared structs are for WebAssembly, but WebAssembly needs a shared struct because they need to handle the code that compiled from C++ or some other languages like that. So I think it’s acceptable to keep the shared struct inside multiple Wasm threads, but not let them into the JavaScript side. Multiple Wasm threads can [do?] programming by the shared data by the shared memory and if they want to send the results to JavaScript, they need to go through the message passing. I think that is better to have.
JWK: One of the primary use cases for shared memory and shared structs are for WebAssembly, WebAssembly needs a shared struct because they need to handle the code compiled from C++ or some other languages. I think it’s acceptable to keep the shared struct inside multiple Wasm threads, but not let them leaked into the JavaScript side. Multiple Wasm threads can program by the shared memory and if they want to send the results to JavaScript, they need to go through the message passing. I think that is better to have.

SYG: I disagree and I think real products would as well.

Expand Down