Depends on what you consider to be problematic with process.* , process.cwd() in particular bit me while trying a couple things, but could be worked around, a slightly more annoying error dealt with cluster using env variables, once again possible to work around.
As stated, I really like the approach taken by threads a gogo. I am not against threading, just very cautious. On Sunday, September 16, 2012 6:11:48 PM UTC-5, rektide wrote: > > Thanks so much for the informative reply: that's a lot of things I don't > know about! > > On Sunday, September 16, 2012 6:22:50 PM UTC-4, Bradley Meck wrote: >> >> There are long discussions in the Node community about what happened when >> we did try to use Isolates. The lack of thread level protections from >> things like mucking with process.* > > > Caveat emptor, doesn't seem like a real issue, just a fact of life. > > >> and the fact that native modules need to add complex support for Isolates >> to be first class (many C level libraries deal poorly with Isolates due to >> them not being exactly like threads from what I understand) are fairly well >> discussed. > > > This in particular would be great to read about! This seems like the chief > potential show-stopper, and most open ended problem. > > >> In addition things like C's abort(), and any shared memory still cause >> problems with Isolates. > > > I'm less willing to say caveat emptor here, sounds harrier, but again > "doing it and creating potential problems" (particularly if they're exit > case problems) seems preferable to not doing it. > > >> It would be interesting to delve into these problems, but for example if >> you use rust the runtime has explicit knowledge of threads rather than v8 >> so you can reduce most of the problems with concurrency to message passing >> and the same problems as process.* > > People who complain about threads generally do not have in depth knowledge >> of difficulties in doing so with Node's environment, but should feel free >> to look them up and discuss solutions rather than simply stating "it should >> have threads". > > > I have done some attempts at research on the topic: this has been > considerably more informative than any threads I've turned up. Perhaps I > was doing my search wrong. That all said, apologies for not being able to > bring a more balanced perspective to my "should have threads" stance, I > would like to be able to do better. > > >> personally really like what Threads a Go Go does, but it still faces the >> difficulties listed above difficulties when you start to delve deep into it. > > > Thanks for contributing. > >> >> > -- 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
