4 ms·
But also much more fragile. I've spent far too many hours in dependency hell on ruby / java projects when 2 packages required different versions of another pack
by TimJRobinson 11y ago
But also much more fragile. I've spent far too many hours in dependency hell on ruby / java projects when 2 packages required different versions of another package and you have to continually fiddle with versions to get them all working smoothly. I love that NPM packages have their own dependency tree so you're never stuck in that situation.
- sanderjd 11y agoAutomatic dependency resolution a-la Ruby's bundler should be required for any respectable dependency manager. In my experience, the algorithm nearly always automatically finds a successful set of dependencies, and when it doesn't, it is because I really have incompatibility that requires code changes in one dependency or another, and further verification. That isn't "dependency hell", it's just the reality that upgrades to one set of interfaces often require changes in another set that depends on them.
- 3pt14159 11y agoI never have problems with Ruby any more. Unless the gem is using the FFI or something weird it everything almost always works. In fact I've had way more problems with Node than with anything else.