But don't we all use a small fraction of library/package and language functionality. - In C's stdio, I've used a fraction of calls - In Ruby/Rails + gems, I u

But don't we all use a small fraction of library/package and language functionality. - In C's stdio, I've used a fraction of calls - In Ruby/Rails + gems, I use a fraction of calls - In Node/Express, I use a fraction of calls - In frontend javascript, I use a fraction of the native calls In frontend dev, I get that this means forcing users to download a library, but for many use cases 4 kb gzipped isn't a big deal (esp if CDNs are involved). I think it'd be interesting to poll developers on what part of Lodash/Underscore causes them concern: 1. The extra download time/bandwidth 2. The extra costs of packaging (failed builds, extra packaging process) 3. The speed of computation (assuming that some native functions are faster) 4. The concern that libraries should only be used when they are highly utilized (e.g., at least 20% of a library's code should be used before it is appropriate to include it)