Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Threading, and Dogmatisms.
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
rektide  
View profile  
 More options Sep 19 2012, 11:08 pm
From: rektide <rekt...@voodoowarez.com>
Date: Wed, 19 Sep 2012 20:08:32 -0700 (PDT)
Local: Wed, Sep 19 2012 11:08 pm
Subject: Re: [nodejs] Re: Threading, and Dogmatisms.

On Wednesday, September 19, 2012 8:55:00 PM UTC-4, Isaac Schlueter wrote:

> > No, Isaac. I feel pissed on here. Ack that.

> Ack'ed.

> Your original request for threads-in-node has been met with
> explanations from me, Ben, and Paddybyers about what would need to be
> done to make that happen, and what the challenges are.

You are projecting defensively: I never requested this feature. I have no
expectations for it.

> There's
> nothing else to discuss here.

I'd love an explanation fulfilling my February request: what factors lead
to it being deemed Isolates was adding too much internal complexity?

We have had some discussion, but as to the effort that got the furthest,
that seems to have been fairly close, the most information we have for it's
cancellation is still:

cause[d] too much instability in node's internal functionality

And your guidance to go figure out what that means for myself:

You should treat this as an experiment: your goal could be to figure out

> why several people close to the Node project are so against a threading API,

Guess? Repeat the experiment and guess? That's a productive use of my time,
becoming as good as Node devs at Node? You thought writing that would be a
productive suggestion for a mailing list? I'm all for leadership by
anarchy, but certainly there's no reason we ought NOT talk, why finding
concordance with another or learning from another is a BAD thing?

I don't demand my 'intellectual curiosity' be satisfied, I'm fine with "I'm
not going to tell you." But I here re-affirm that this hunger is not sated,
and that this issue is not closed. If there are Node.js people that feel
they can provide technical contributions about what happened, I probably am
not going to directly make Node.js better with that knowledge, but I think
we'd all be better for the wisdom you knowing people can share.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.