Received: by 10.236.187.1 with SMTP id x1mr3771575yhm.8.1314830299079; Wed, 31 Aug 2011 15:38:19 -0700 (PDT) X-BeenThere: nodejs@googlegroups.com Received: by 10.150.173.9 with SMTP id v9ls1268154ybe.6.gmail; Wed, 31 Aug 2011 15:38:09 -0700 (PDT) Received: by 10.236.184.65 with SMTP id r41mr3929475yhm.6.1314830289581; Wed, 31 Aug 2011 15:38:09 -0700 (PDT) Received: by 10.236.184.65 with SMTP id r41mr3929472yhm.6.1314830289571; Wed, 31 Aug 2011 15:38:09 -0700 (PDT) Return-Path: Received: from mail-gw0-f50.google.com (mail-gw0-f50.google.com [74.125.83.50]) by gmr-mx.google.com with ESMTPS id d41si13379yhe.3.2011.08.31.15.38.08 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 31 Aug 2011 15:38:08 -0700 (PDT) Received-SPF: neutral (google.com: 74.125.83.50 is neither permitted nor denied by best guess record for domain of m...@boutiquing.com) client-ip=74.125.83.50; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 74.125.83.50 is neither permitted nor denied by best guess record for domain of m...@boutiquing.com) smtp.mail=m...@boutiquing.com Received: by gwj16 with SMTP id 16so588690gwj.37 for ; Wed, 31 Aug 2011 15:38:08 -0700 (PDT) Received: by 10.142.209.1 with SMTP id h1mr204257wfg.300.1314830287201; Wed, 31 Aug 2011 15:38:07 -0700 (PDT) MIME-Version: 1.0 Received: by 10.142.225.5 with HTTP; Wed, 31 Aug 2011 15:37:47 -0700 (PDT) In-Reply-To: <9ad69d1f-cb94-4766-a0ed-3c31e5228793@bl1g2000vbb.googlegroups.com> References: <0d912101-6930-4aad-b610-2a8e956310ed@u20g2000yqj.googlegroups.com> <9ad69d1f-cb94-4766-a0ed-3c31e5228...@bl1g2000vbb.googlegroups.com> From: Mark Hahn Date: Wed, 31 Aug 2011 15:37:47 -0700 Message-ID: Subject: Re: [nodejs] Re: ANN: threads - enabling safe use of synchronous coding To: nodejs@googlegroups.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable It doesn't matter what it is called as long as it isn't confusing. Marketing studies for product names have shown that names unrelated to function perform better in the market, hence Apple, Google, etc. I like the "ropes" moniker. On Wed, Aug 31, 2011 at 2:33 PM, rtweed wrote: > I really dont care what you want me to call it. =A0I spent a few minutes > looking for a name that was vaguely related to its architecture and > came up with threads and found the name wasn't registered in npm so > went with it. =A0I mainly wanted to get it out as soon as possible > because I have specific plans for its use. > > How about you guys vote for a name and I'll rename it accordingly :-) > > Rob > > On Aug 31, 10:19=A0pm, Joshua Holbrook wrote: >> Is it too late to rename it? Maybe "ropes." ;) >> >> --Josh >> >> >> >> >> >> >> >> On Wed, Aug 31, 2011 at 2:08 PM, Mark Hahn wrote: >> > Many more people than computer scientists could benefit from this and >> > it would be a shame if they didn't look into it because of its name. >> >> > On Wed, Aug 31, 2011 at 1:04 PM, Matt wrote: >> >> On Wed, Aug 31, 2011 at 2:43 PM, Isaac Schlueter wrote: >> >> >>> Yeah, -1 on the name. That's very confusing, on a point which is >> >>> already confusing enough. >> >> >> LOL, isn't this rather ironic, given it's built on child_process.fork= (), >> >> which isn't fork(2) at all, and is really quite confusing? >> >> >>> The child_process.fork doesn't create a new thread. =A0It creates a >> >>> full-fledged OS child process, complete with its own pid and memory >> >>> and everything. =A0You can send send it signals, renice it, etc. =A0= It >> >>> can't share memory directly with its parent. =A0It's not a thread. >> >> >> Threads have many definitions, not necessarily just those of shared P= ID and >> >> memory space. In fact the Wikipedia page specifically mentions a thre= ad >> >> being a "fork".=A0http://en.wikipedia.org/wiki/Thread_(computer_progr= amming) >> >> >>> Not to say this isn't a useful lib. =A0Seems like a nice little suga= r >> >>> layer over child_process.fork, which is probably very useful. =A0But >> >>> it's absolutely not in any way "multithreaded". >> >> >> Computer scientists would probably disagree with you. >> >> Matt. >> >> >> -- >> >> 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+unsubscribe@googlegroups.com >> >> For more options, visit this group at >> >>http://groups.google.com/group/nodejs?hl=3Den?hl=3Den >> >> > -- >> > Job Board:http://jobs.nodejs.org/ >> > Posting guidelines:https://github.com/joyent/node/wiki/Mailing-List-Po= sting-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+unsubscribe@googlegroups.com >> > For more options, visit this group at >> >http://groups.google.com/group/nodejs?hl=3Den?hl=3Den > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Post= ing-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+unsubscribe@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=3Den?hl=3Den >