Synchronous APIs Generally Considered Harmful is probably the one 'harmful' essay that the Web apparently needs but I don't think has gotten
-
-
@wycats Not so. Modal dialogs on main thread are counterexample. But again: I'm asking only about workers.@domenic@briankardell -
@BrendanEich apis would work diff depending on thread, or only available in one or the other? Does seem a little weird.@wycats@domenic -
@briankardell Assume no DOM or other APIs on compute worker, but still want sync input for Emscripten et al.@wycats@domenic -
@BrendanEich sync input like file/xhr?@wycats@domenic -
@briankardell Any sync input on a worker.@wycats@domenic -
@BrendanEich but those same things can happen in the main thread, right? They'd be different based on where they ran?@wycats@domenic -
@briankardell some APIs are already main thread only. Are you srsly objecting to worker-only APIs?@wycats@domenic -
@BrendanEich I'm not, no, I'm asking whether there are/would be examples that work in both main/worker differently.@wycats@domenic - 1 more reply
New conversation -
-
-
@wycats@BrendanEich@briankardell that is too drastic of a statement. Shared memory multithreading is fork-the-lang. Sync is fine. -
@domenic@BrendanEich@briankardell let's see how far async/await takes us for non-emscripten use-cases.
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.