don’t even try to learn what a software dependency
Everyone at my company keeps using the term “dependency hell” when referring to literally dependency management and order of operations with a modern package manager like NPM that tracks versions and dependencies.
They’ve literally never experienced working with dynamically linked libraries and they think it’s so hard because they have to understand a tree that exists in data form (e.g. package-lock.json) and can be easily visualized vs a tangled file system and LD_LIBRARY_PATH or Windows standard search order / HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\KnownDLLs.
These guys are living in the glory. I bet they don’t even know all the info they need is just in a fucking config file, in a damn manual somewhere or in the stupid docs that people doesn’t seem to bother reading anymore, or writing some decent ones.
Everyone at my company keeps using the term “dependency hell” when referring to literally dependency management and order of operations with a modern package manager like NPM that tracks versions and dependencies.
They’ve literally never experienced working with dynamically linked libraries and they think it’s so hard because they have to understand a tree that exists in data form (e.g.
package-lock.json
) and can be easily visualized vs a tangled file system andLD_LIBRARY_PATH
or Windows standard search order /HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\KnownDLLs
.It’s pathetic.
These guys are living in the glory. I bet they don’t even know all the info they need is just in a fucking config file, in a damn manual somewhere or in the stupid docs that people doesn’t seem to bother reading anymore, or writing some decent ones.