On Mon, May 28, 2012 at 5:25 PM, Mark Volkmann <[email protected]> wrote: > On Mon, May 28, 2012 at 7:43 AM, Oliver Leics <[email protected]> wrote: >> On Mon, May 28, 2012 at 9:26 AM, babibu <[email protected]> >> wrote: >>> Why do you recommend using no flow control library? >> >> Because it's no rocket-science what libraries like async provide. They >> are very helpful in the beginning, to get used to the async >> programming style. But once you know how it works, you can just drop >> the async-helper-library from your dependencies and deal for yourself >> with all those callbacks with ease. Practice, well-known patterns and >> modularization are the keys. > > A downside to dropping the async functions and dealing with the same > functionality yourself is that everyone who looks at your code has to > examine the code to familiarize themselves with what you are doing. On > the other hand, when many people see things like async.parallel or > async.waterfall, they immediately know what is happening. That's the > benefit of standardizing on a widely used library.
With or without using the async-library, everyone who looks at your code has to examine the code to familiarize themselves with what you are doing. With or without using the async-library, you have to communicate what you are doing. Write proper comments (and document well!), use descriptive function-names and use standard/well-known callback patterns. - o -- 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
