On Tuesday, September 18, 2012 10:10:34 PM UTC+2, Isaac Schlueter wrote: > > On Tue, Sep 18, 2012 at 12:31 PM, Rick Waldron > <waldro...@gmail.com<javascript:>> > wrote: > > > > ... > > Thanks, Rick. Sorry, I didn't make this clear: your (and Doug > Crockford's) position that threads have no place in Javascript, is > pretty reasonable, and I appreciate you sharing the conversation you > had. You're good people :) > > > > On Tue, Sep 18, 2012 at 1:03 PM, Bruno Jouhier > <bjou...@gmail.com<javascript:>> > wrote: > > Would be interesting to have his opinion on WebWorkers. Aren't they > threads > > in JavaScript? (same model as TAGG: message passing and share nothing) > > The implementation of WebWorkers is explicitly vague. They can be > done using any concurrency mechanism (green threads, coroutines, > threads, processes, etc.) The node child_process.fork() API is very > similar. >
Implemented as green threads or coroutines??? That would be really daft. The UI thread would yield to the worker and be blocked while worker is running!!! How are they implemented in Chrome? As threads in V8 isolates (like TAGG), or as child processes? -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
