News for hackers. Stuff that matters.
Re:Disabling npm's progress bar yields a 2x npm install spee... by technomancy on Wednesday January 27, 2016 @01:48AM (#10978646)
> I hold up Bundler as one of the great success stories of open source

It's a great success in many ways, but the problem it solves is completely self-inflicted by rubygems. I've also been doing Ruby for over a decade, but I've also learned a lot from other library ecosystems, and I feel pretty confident saying that disallowing version ranges makes all those headaches completely evaporate.

Re:Disabling npm's progress bar yields a 2x npm install spee... by glenjamin on Wednesday January 27, 2016 @03:30AM (#10978934)
I'm with you that version ranges cause problems, but my belief is that lockfiles are a better solution.

Generally I'd use semver ranges in libraries, and then fixed versions + lockfiles for transitive deps in applications.

I suppose this is roughly equivalent to doing `:pedantic :abort` in leiningen, except you wont't have as many warning to squash - either way you have to rely on the test suite to tell you if the versions you've pegged work.

Re:Disabling npm's progress bar yields a 2x npm install spee... by caoilte on Wednesday January 27, 2016 @12:05PM (#10981205)
I've also been on that journey and am starting to feel the same way about variance.