Leo Dutra (2016-11-02T14:09:56.000Z)
leodutra.br at gmail.com (2016-11-02T14:24:23.319Z)
There's nothing about threading that is not problem with Event loop. I'd say there's even less problems. The proposal is a seamless behaviour, equals to what we have now. Message passing is not a problem of JS developer in the case, but a V8/WhateverMonkey problem. Changing a value inside a multithread async MUST behave in the same way of a change inside a single threaded async. The same way, non-referenced variables SHALL NOT be scoped in the thread. This is not Java with volatiles. This is the plain old JS with clojures, openess and loose bare metal control. Thread interruption is a bad practice anyway. And we could have a Mutex class for the specific case or another idea. Workers are evented and started, not pooled and easy to use.