5 ms·
Except a good package manager will let you specify exactly which version you wish to depend upon, so any changes you make upstream will have no effect on people
by naasking 11y ago
Except a good package manager will let you specify exactly which version you wish to depend upon, so any changes you make upstream will have no effect on people who protect themselves against automatic version updates.
Seriously, the properties of good package management should be obvious by now. Any design that can break dependents and there's nothing they can do to protect themselves is broken.
- efaref 11y agoThat's just a no-true-scotsman fallacy. And pinning versions just means you lose automatic updates, which is surely the point of using a package manager in the first place. Otherwise you might as well just download the package and include it verbatim.
- icebraining 11y agoNo, it's not an NTS fallacy. And the package manager is mostly useful for tracking updates and simplify the process; having it automatically update is completely optional, and personally, I never do.
- naasking 11y agoExactly. A notification that new updates are available would be nice, but I don't think automatic updates should be the default, even if "semantic versioning" says the update should be backwards compatible.
- stcredzero 11y agoNo, it's not an NTS fallacy. No True Scotsman is so often mis-attributed, that the mis-attribution needs to be its own fallacy.
- smarks 11y agoExactly. That's the No True No True Scotsman Fallacy Fallacy.
- TeMPOraL 11y agoCompare also with Fallacy Fallacy - just because the argument is fallacious, doesn't mean the overall point is wrong.
- stcredzero 11y agoThere's this "Tone Argument" Fallacy Fallacy. You can't win an argument by complaining that the other's tone is unpleasant. So that's a valid fallacy, but it only applies to a particular argument in a particular circumstance. Certain people on the Internet then make the illogical jump to the conclusion that they are therefore justified to use whatever tone they care to in any argument. (And lo and behold, they always "win" arguments.)
- coldtea 11y agoAnd wait till you hear what a sufficiently smart compiler can do! http://c2.com/cgi/wiki?SufficientlySmartCompiler http://c2.com/cgi/wiki?SufficientlySmartCompiler
- Bjartr 11y agoBut there already exist package managers that let you pin to a specific version like he's saying they should e.g. Maven, so I don't think your link quite applies here.
- coldtea 11y agoNpm allows that too -- you just specify an explicit version number, e.g. "1.5.3" instead of "*" or "^1.5.3" etc. My comment was against this belief that "smarter" tools in general are some sort of panacea. For example pining to a specific version won't help you match if the package is removed altogether (as in this case), and ever worse if it's replaced afterwards by another (newly registered) with an incompatible same version out. It won't try to overwrite your specific install of course (since the version already matches what you have), but you'll feel the pain when you try to duplicate/deploy etc a new install with the same package listing -- suddenly the package either won't be there (or will be modified in the worst case scenario). So, then we opt for ever more features of a "sufficiently smart package manager", e.g. signatures, permanence of anything published etc...
- deong 11y agoWithout knowing much of how npm works, I'm going to assume you have ways of protecting yourself there too. If nothing else, good old "cp -r" can effectively let you pin to a version. The point is that people use package managers and third party modules installed from them to automate tedious work, and anything automated will have the potential to do something other than what you want. Is that risk high? Not really, but it's not zero either.