2 ms·
> If you do have a bad package manager, there is a cost of adding a dependency, and you should consider it. That's what pdkl95's point was. That's great, and m
by naasking 11y ago
> If you do have a bad package manager, there is a cost of adding a dependency, and you should consider it. That's what pdkl95's point was.
That's great, and my point was that with a good package manager, that cost is effectively zero.
> And the dependency cost I talk about is universal -- any package manager that allows for easy package updates is open to critical packages being broken.
Automatic updates are a terrible idea, even if the developer purports to use "semantic versioning" and the update is supposed to be backwards compatible. Specifying a version should be mandatory.
Your package manager could easily notify you that updates are available, but it should never update for you. That's as "easy" as updates should get, because anything else inevitably introduces silent breaking changes.
- Manishearth 11y ago> my point was that with a good package manager, that cost is effectively zero. yes, which doesn't refute pdkl95's point. If you're not in the world with a good package manager, you should consider the cost of the dependency. The Node ecosystem seems to not have done that. That's the bottom line here, if there is a cost to dependencies (which you don't seem to disagree with, at least wrt NPM), then you shouldn't have dependencies for 11-line functions. Everything else is orthogonal.