Michael J. Ryan
tracker1 at gmail.com
Wed Nov 2 15:18:20 UTC 2016
Given how many bugs I've dealt with involving race conditions in .Net, I
would really rather have a solid worker pattern over any internal threading
inside the main event loop in js as this thread has proposed...
Adding an rpc-like promise callback in addition to, or over message passing
would be far safer...
Internal threading may be "a solved problem" but it creates so many new
ones with really weird bugs to go with them.
On Nov 2, 2016 8:03 AM, "Bradley Meck" <bradley.meck at gmail.com> wrote:
> > As I said... JS has mutable objects by default. The memory space SHALL
> be the same.
> > What is not being covered? Let it come to the surface.
> As stated, that single threaded access to objects and shared memory
> multi-threaded access are very different.
> On Wed, Nov 2, 2016 at 9:56 AM, Leo Dutra <leodutra.br at gmail.com> wrote:
>> Message passing between two objects is a Law of Nature, broad and
>> But there's more than just workers and process spawn in life.
>> As I said... JS has mutable objects by default. The memory space SHALL be
>> the same.
>> Atomic could handle the racing when needed and a Mutex for locking.
>> What is not being covered? Let it come to the surface.
> es-discuss mailing list
> es-discuss at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss