News for hackers. Stuff that matters.
Re:A Taste of JavaScript's New Parallel Primitives by pfooti on Thursday May 05, 2016 @04:05PM (#11639280)
That's pretty rad - the vast majority of what I would see myself wanting to do in a multithreaded javascript world would be limited to something with transferrable arraybuffers. Like: "hey, worker, go do some work and lmk when you're done". Moving big chunks of memory around in ways that atomically only ever have one allowed accessing thread would be plenty.
Re:A Taste of JavaScript's New Parallel Primitives by yoklov on Thursday May 05, 2016 @04:48PM (#11639560)
I thought this too, but the fact that you can't send only a chunk of an array buffer is a huge limitation. It basically limits you do using a background thread to do something, instead of dividing the work among many (well, you can, but you loose most of the benefit of transferrable).
Re:A Taste of JavaScript's New Parallel Primitives by Klathmon on Thursday May 05, 2016 @05:01PM (#11639641)
Well you can still divide the work among many workers, you just need to incur the cost of copying/splitting the buffer before you start sending them off.

In most cases you know how many workers you want at the start of the program, so that cost of splitting/merging only happens once (and you can do that splitting/merging in a worker to avoid hanging the main thread) and then you can pass those chunks around freely.

Re:A Taste of JavaScript's New Parallel Primitives by yoklov on Thursday May 05, 2016 @10:32PM (#11641295)
For workloads like graphics, the cost of splitting/merging happens each time.