(Not sure yet how much I believe this claim) Perhaps CPU-bound alone justifies sync, but maybe not callable on UI thread. You won't do better than a background thread, be it app- or browser-owned. Former is more flexible and inherits existing DoS limits. Latter needs custom limit
-
-
Replying to @davidben__ @jyasskin and
"UI thread" is the sort of assumption in system design that frequently defeats responsiveness (while improving throughput). Most engineers live in someone else's framework; also responsiveness is king on the client side.
0 replies 0 retweets 2 likes -
Replying to @BRIAN_____ @davidben__ and
I hear compilers are "a thing" these days.
2 replies 0 retweets 4 likes -
Replying to @slightlylate @BRIAN_____ and
If equivalent WASM'd crypto methods are outperforming native ones, can we at least agree that's a problem worth solving?
1 reply 0 retweets 3 likes -
Replying to @jaffathecake @BRIAN_____ and
"outperforming" is multi-faceted
1 reply 0 retweets 3 likes -
Replying to @slightlylate @BRIAN_____ and
For this particular crypto case it'd be good to know specifics. What's the size and shape of the issue before and after WASM.
1 reply 0 retweets 1 like -
Replying to @jaffathecake @BRIAN_____ and
WASM doesn't change anything other than that people who were C/C++ folks were sold a "minimal changes" bill of goods.
1 reply 0 retweets 2 likes -
Replying to @slightlylate @jaffathecake and
WASM is a capability in the sense that getting half your CPU back is a capability. In a tight loop, that's transformative. It changes nothing about the ecosystem outside that tight loop.
1 reply 0 retweets 5 likes -
Replying to @slightlylate @BRIAN_____ and
Right, so it's worth learning more about cases where that becomes better than native implementations
1 reply 0 retweets 2 likes
Native vs. non-native isn't meaningful. It's about scheduling; who makes sure that the "ui thread" (a convention loosely enforced) remains responsive? What measures are taken to enforce it? At what cost?
-
-
Replying to @slightlylate @BRIAN_____ and
I guess I'm more interested in cases where WASM is better than native in a dedicated worker.
1 reply 0 retweets 1 like -
Replying to @jaffathecake @BRIAN_____ and
Would like to understand these as well. I suspect that arguments for synchronous behavior discount network time implicitly and in ways that are not flattering...but use cases matter. If you're building git and hashes are everything, it's perhaps an open question.
0 replies 0 retweets 3 likes
End of conversation
New conversation -
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.