Apropos earlier threads, Miguel de Icaza has an interesting blog post on callbacks and C#Async:
http://tirania.org/blog/archive/2013/Aug-15.html He writes: > Just like in the Go To days, or the days of manual memory management, we are > turning into glorified accountants. Check every code path for the proper > state to be properly reset, updated, disposed, released. I agree with him on this, despite JavaScript closures. If anything, closures can potentially exacerbate the memory accounting problem. I think he is also right in quoting Dijkstra (I reproduce part of the quote below): > [O]ur intellectual powers are rather geared to master static relations and > that our powers to visualize processes evolving in time are relatively poorly > developed. For that reason we should do (as wise programmers aware of our > limitations) our utmost to shorten the conceptual gap between the static > program and the dynamic process, to make the correspondence between the > program (spread out in text space) and the process (spread out in time) as > trivial as possible. Lest I be perceived as “complaining”, I bring this up as academically interesting, not as a bumptious attempt to influence the future of NodeJS :-). —ravi -- -- 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 --- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
