Message from JavaScript discussions

December 2018

— It's so powerful

— 

I see no problem in debugging parallel code, you have to *unpack* it first, because, if something can run parallel, then it can be chained in a debug sequence where you step over each function, check the result, check the execution code and when it's okay, pack it back into parallel.. but the debugging in parallel, when its packed and runs simultaneosly is a problem.

— I don't understand what you mean by 'pack'

— Are you talking about Hz specifically?

— Packed, it's when it runs parallel.. depending on time may be a mistake. with this code:

spawn(sleep, 1000);
spawn(sleep, 2000);
you will get different results in async vs parallel mode. results should be equal to be useful, imo.

Message permanent page

— 

spawn(computeOneConcern, params1);
spawn(computeAnotherConcern, params2);
spawn(makeNetworkRequest);
...
waitAllDone();
...
getUseOfResults();

Message permanent page

— Do you mean, transpiled / without transpiling?

— It doesnt matter, the problem happens only when concerns meet

— I have never seen packed before

— I don't understand the meaning

— Async is mostly parallel too

— Sleep function depends on time, time is a single concern, see