ama

There's a difference between being negative with specific complaints versus hyperbolic, drive-by FUD. Regarding your own complaints with Node. You're over-generalising. Nobody says you must use small modules. Larger libraries and frameworks exist. Same goes for build scripts. Also read this to get more context on small modules: https://github.com/sindresorhus/ama/issues/10

I'm sindresorhus. My thoughts on the left-pad situation: https://github.com/sindresorhus/ama/issues/367

> A little copying is better than a little dependency. I actually disagree with this. Given that we're already working with projects that can have several hundred dependencies - I think the goal ought to be in removing the weight of including the dependency. sindresorhus says it better than me though https://github.com/sindresorhus/ama/issues/10#issuecomment-1... I imagine it also depends on whether your place of employment is writing one giant single-repository codebase vs. several modular applications, as the latter clearly affords a package manager while the former eschews the complexity of composing systems.

> This GitHub comment by Sindre Sorhus (author of over 600 modules on npm) is my favorite writeup on the topic: https://github.com/sindresorhus/ama/issues/10#issuecomment-1.... If anything looking at sindresorhus's activity feed: (https://github.com/sindresorhus) perfectly supports the author's point. Maybe some people have so little to do that they can author or find a relevant package for every single ~10 line function they need to use in their code and then spend countless commits bumping project-versions and updating package.json files. I have no idea how they get work done though..

This comes up a lot when people discuss anything related to npm modules. It's easy to simply dismiss these trivial one-line modules as "insanity" and move on, but there's actually plenty of good reasons as to why many prefer to work with multiple small modules in this manner. This GitHub comment by Sindre Sorhus (author of over 600 modules on npm) is my favorite writeup on the topic: https://github.com/sindresorhus/ama/issues/10#issuecomment-1... TL;DR: Small modules are easy to reason about, and encourage code reuse and sharing across the entire community. This allows these small modules to get a tremendous amount of real world testing under all sorts of use cases, which can uncover many corner cases that an alternative naive inlined solution would never have covered (until it shows up as a bug in production). The entire community benefi

Another interesting argument for micro-modules: https://github.com/sindresorhus/ama/issues/10#issuecomment-1...

Sindre basically treats npm as his snippet database. I don't see anything wrong with it. See: https://github.com/sindresorhus/ama/issues/10#issuecomment-1...

May I just point out how awesome the original author is? I mean, I'm using his GitHub indicator (available as an extension for both Chrome[0] and Firefox[1]), I'm collaborating with him on his mega popular awesome list[2] (currently the top non-code repository on GitHub by the number of stars), he started the whole GitHub AMA idea[3], he developed a bunch of command line clients that I'm using regularly (like speed-test[4], is-reachable[5] and is-github-down[6])... And now this! This guy is unstoppable! [0] https://chrome.google.com/webstore/detail/notifier-for-githu... [1] https://github.com/sindresorhus/notifier-for-github-firefox [2] https://github.com/sindresorhus/awesome [3] https://github.com/sindresorhus/ama [4] https://github.com/sindresorhus/speed-test [5] https://github.com/sindresorhus/is-reachable [6] https://github.com/sindre

Not sure if he comes here, but Sindre Sorhus[1] is quite prolific. The answer, though, is not satisfactory: He doesn't work. He moved to Thailand and lives off savings. Here's the answer you are looking for: https://github.com/sindresorhus/ama/issues/167 and you can search more related questions in the issues. [1] https://github.com/sindresorhus