This all misses the bigger point: WASM isn't actually an assembly for the web; it's more of a math co-processor. Limited applications for forseeable future = \https://twitter.com/callahad/status/937728124451786752 …
-
-
Replying to @slightlylate
Yeah, that's the part of the story that tends to get left out: there is currently no DOM or web APIs to access from your WASM code. It is *only* for processing data and passing it back to JS.
1 reply 0 retweets 1 like -
Replying to @AmeliasBrain @slightlylate
(Or, that's my understanding. Ready to be corrected. Maybe folks are already working on DOM libraries for web assembly. Or WebGL contexts that can be manipulated directly?)
1 reply 0 retweets 0 likes -
Replying to @AmeliasBrain
The challenge is threading. DOM isn't thread-safe in basically all implementations. Will be many years before it is. JS/WASM will need to lock to share access.
2 replies 0 retweets 2 likes -
Replying to @slightlylate @AmeliasBrain
the host bindings proposal will give WebAssembly access to the DOM, and it's not expected to take very long. IIRC expected in < 1 yearhttps://github.com/WebAssembly/host-bindings …
2 replies 7 retweets 34 likes -
Replying to @linclark @AmeliasBrain
I have doubts about that timeline; I keep asking to have something sent to the
@w3ctag for an early look. Crickets so far.1 reply 0 retweets 0 likes -
Were you asking about host bindings or about GC (which DOM access was expected to be blocked on)? Because host bindings proposal is pretty new, intro-ed to move DOM access ahead of GC. GC is definitely expected to have a longer timeline
1 reply 0 retweets 0 likes
The scale of the API surface needed to access most of the DOM is daunting. I've asked our team to think of it as being similar to thunks to a restricted JS subset (it'd need disaster if only DOM could be bound to)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.