On Thu, Nov 3, 2016 at 9:10 AM, Michał Wadas <[email protected]> wrote:
> Why you can't solve it with shared memory buffer? Shared - I mean instance > of *SharedArrayBuffer. * > > not in node; in browser ya... where webworkers are threads. (and not in javascript base) And while firefox is beginning to look appealing again I'm stuck on chrome (native android) > On 3 Nov 2016 5:05 p.m., "J Decker" <[email protected]> wrote: > >> >> >> On Wed, Nov 2, 2016 at 7:44 AM, Michał Wadas <[email protected]> >> wrote: >> >>> Actually, is there any problem that can't be easily solved with >>> message-passing for high-level structures or low-level shared memory >>> buffers? >>> >>> >> Yes, meshing dynamic geometries that involve a few 20k faces. If you >> have a thread do the work, the overhead of srealizing the resulting buffers >> will kill any benefit. >> >> But; typed arrays can be shared also. (they are with C++ addons in node) >> >> The biggest problem with node's lack of threads is they really need >> separate but equal heaps. I heard that there's a global heap lock... that >> wouldn't be required except when allocating addition space for each heap. >> >> >> >> To the general - stop treating programmers like idiots. Give us the >> rope. Let us hang ourselves. >> >> >>> _______________________________________________ >>> es-discuss mailing list >>> [email protected] >>> https://mail.mozilla.org/listinfo/es-discuss >>> >>> >>
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
