> > Great writeup! Most these points are right on.
Thanks Tim! Positive feedback is welcome. > But I've also been severely bitten by > the performance and race-condition implications of this. ... > I've seen many cases where it's better and simpler to > just call right away. Can you give me an example? I've seen many cases where pulling in just one library causes my `npm ls` > output to be completely useless. I've never found `npm ls` to be particularly useful anyway, I'm generally only concerned by the packages defined in my package.json. What are you using `npm ls` for? > And stuff I know I'm not using like 5 different kinds of option parsers, > Ansi color libraries, > logging frameworks, and sometimes even testing frameworks. > Obviously testing frameworks should have been put in dev dependencies, that's an obvious mistake, but how would you suggest people author libraries that offer a commandline tool that supplies pretty output, without clogging up the deps and without reinventing the wheel? I know that was just an example, but I don't see a way of avoiding deps for functionality you may not be using without going full substack<https://plus.google.com/114198465647271367011/posts/AowKp99k496> . > I shouldn't have to install 5MB of javascript code in > dependencies just to use your simple library. > Probably true especially regarding code complexity, but disk space is cheap. Though, the time to install all that stuff is a real bummer. If `npm install` was faster, would this be less of an issue? -- 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
