CORRECTION, I take my last statement back, you DID add to the conversation and I am a bad reader.
I had already considered the performance issue of having the API functions not just call the callback, but also having to handle OPTIONAL additional parameters, which in node.js might happen some millions of times per second. A definitive statement in that direction is what I'm actually looking for, if THAT was indeed the reason. I dislike nesting my functions, even though pure functional style would go A LOT deeper (with the nesting) :) On Wed, Dec 12, 2012 at 12:16 PM, Ruben Tan <[email protected]> wrote: > I think you meant "closure". clojure is a language running on JVM. > > On Wednesday, December 12, 2012 6:59:56 PM UTC+8, greelgorke wrote: >> >> why? its the simpliest and most common way, that's it. passing by custom >> params has to be implemented in the async function itself, there is no >> native support in js nor node for this. and since use of clojures is very >> common in js world, mostly noone cares about it. but yes it may help to >> un-clutter the callbacks a bit and helpt to build pure functions with >> explicit parameters. but i doubt that it would be a performance improvement, >> because v8 optimized clojurescope-access very well, see here >> http://jsperf.com/bind-vs-clojure/2 -- 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
