Message from JavaScript discussions

December 2018

— Again, only matters for spawned processes, right?

— 

This is enough to make coroutines run non-deterministically

const end = performance.now() + ms;
while (performance.now() < end);

— It doesnt give anything for browser, right. as Dani cant hack Chrome/FF engine🤤

— It is all pure JS

— It matters only for spawned processes which want to take advantage of some form of deterministic execution order

Message permanent page

— Right

— Which they should not, imo

— It's the same as any other thread sync issue

— You use constructs which mitigate things like missed cycles

— Pure JS in browser runs ordered, and you may change the order without Herz

— It is coarse concurrency

— Meaning concurrency occurs on a whole-function basis rather than chunks of functions