On Fri, Aug 30, 2013 at 9:08 AM, Dean Landolt <d...@deanlandolt.com> wrote:
> Which means you have to wrap pretty much any zalgo-promise, or use some > goofy apply mechanism. Assuming you meticulously add all this boilerplate > then yes, at this point Juraj is right. It "solves" the problem (with a > nextTick or equivalent, of course). But at what cost? > This sounds like the opposite of promises solving a problem, and exactly like what Isaac said about abstraction not mattering. As soon as you use nextTick() or equivalent, you've proven the point that being consistently async is what matters, not the abstraction over function invocation. -- -- 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 --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
