Separate async functions into modules

[tejasmanohar]

I want to hear from the community on this one. I've seen a lot of modules that are basically individual functions from async published as modules. To avoid this redundancy, what do you think about separating each async function into separate modules?

[aearly]

Seems like #720 is a prereq. I like the idea, it's just a lot of work to set something like that up and maintain it.

Lodash publishes as a single module and as an ecosystem of modules. It's successful at this mainly because its maintainer works on it nearly full time. Caolan hasn't been around for almost a year. lodash-cli is a huge piece of software.

I like that there already are a lot of modules on npm that are just a single function from async, like each-async and async-reduce. Not very discoverable, but they are there.

[aearly]

Closing this for now. Maybe we can convince @jdalton to modularize lodash-cli's secret sauce. ;)

[jdalton]

It's successful at this mainly because its maintainer works on it nearly full time.

Naw, just a little bit each day. That little bit adds up though : P

FWIW I create the custom build in less than a month back in 2012 not working on it every day. I think it's something you all could totally tackle.

[aearly]

I'd like to learn more about how lodash-cli works, but the 3000 line source is a bit... daunting. Any guidance?

If I'm going to take a day to figure out how it works, I might as well take the time to also factor it into comprehensible chunks -- would that be welcome?

[jdalton]

I might as well take the time to also factor it into comprehensible chunks -- would that be welcome?

Totally.