@alan no problem!
@brandon, I stand corrected. near-hit is more accurate!
On Sat, Jun 23, 2012 at 6:07 AM, Alan Gutierrez a...@prettyrobots.com wrote:
On Fri, Jun 22, 2012 at 04:21:00AM +1200, Dominic Tarr wrote:
also, this is control flow, not flow control.
This near collision in
On 6/21/12 7:30 AM, Mariusz Nowak wrote:
Alan, we use asynchronous programming for tasks that take time, so in
that case, whether we wrap such tasks with closure or prototype solution
wouldn't make difference in performance. I think debating on performance
in that case is pointless.
I believe
On Fri, Jun 22, 2012 at 04:21:00AM +1200, Dominic Tarr wrote:
also, this is control flow, not flow control.
This near collision in nomenclature is most unfortunate, but control flow
refers to the transference of control from one phase to the next. (this is the
case you are discussing)
flow
Alan, we use asynchronous programming for tasks that take time, so in that
case, whether we wrap such tasks with closure or prototype solution
wouldn't make difference in performance. I think debating on performance in
that case is pointless.
As a side node be sure to check also
also, this is control flow, not flow control.
This near collision in nomenclature is most unfortunate,
but control flow refers to the transference of control from one
phase to the next.
(this is the case you are discussing)
flow control refers to controling rates of (eg, data) flow through a
George carlin has an opinion on this nomenclature issue
http://m.youtube.com/#/watch?desktop_uri=/watch?v=zuCN6CD8j_sv=zuCN6CD8j_sgl=US
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message
