News for hackers. Stuff that matters.
Re:Package Management: The problem with using version ranges by sjrd on Thursday July 13, 2017 @03:57AM (#14759523)
How come this is not already obvious to everyone?

I completely agree with the article. Version ranges are evil. Avoid them at all cost.

Re:Package Management: The problem with using version ranges by yuchi on Thursday July 13, 2017 @04:02AM (#14759541)
That’s not right. Ranges are powerful and important, but you need a locking mechanism too otherwise you‘ll loose control. Npm and Yarn got finally right and dependency management in the npm ecosystem is now a breeze.
Re:Package Management: The problem with using version ranges by andybak on Thursday July 13, 2017 @06:12AM (#14760068)
> How come this is not already obvious to everyone?

Because other people have different priorities and have come to a different cost/benefit ratio value than you?

Re:Package Management: The problem with using version ranges by alexscheelmeyer on Thursday July 13, 2017 @07:33AM (#14760428)
One reason is that many developers work with package managers / languages that are INCAPABLE of handling multiple versions of the same dependency. Without this you quickly get version deadlocks without semver.

Another reason is that many developers are obsessing on getting the latest version of their dependencies for fear of security issues or just missing out on the latest and greatest - and they often completely ignore retesting the application since they now have someone to blame if it fails (that other developer should not have pushed the breaking change with a minor version bump!)

I agree with you that it should be the standard to have fixed versions and update your dependencies at a time of your choosing so that everything can get tested properly - but it seems to be an uphill battle.

Re:Package Management: The problem with using version ranges by eeZah7Ux on Thursday July 13, 2017 @09:56AM (#14761221)
> many developers are obsessing on getting the latest version of their dependencies for fear of security issues

Getting the latest version is how you get new vulnerabilities.

Various software distributors, including some Linux distros let software bake in for this reason and can be even faster than the upstreams in developing and applying patches to known vulnerabilities.

Also, unfixed but known vulnerabilities are less dangerous: security and system engineers can work around them, also IDS/IPS can detect and often block attacks.