4 ms·
Yeah that is a nightmare. But isn’t that a problem on all package systems except more dynamic runtimes like NPM which can load many copies of the same library?
by grandempire 2y ago
Yeah that is a nightmare. But isn’t that a problem on all package systems except more dynamic runtimes like NPM which can load many copies of the same library?
- hylaride 2y agoIt's a problem all languages have, but some are better at sorting it out. The way NPM does it solves one issue, but causes others. The big issue, IMHO, is that when you're dealing with interpreted languages it's very hard to lock down issues before runtime. With compiled or statically typed languages you tend to know a lot sooner where issues lie. I've had to update requests to deal with certificate issues (to support more modern ciphers/hashes etc) but I won't know until runtime if it even works.
- grandempire 2y agoAgreed. I am not saying NPM is better, just that it side steps dependency resolution problems through its runtime. (I do not want 20 copies of the same library in my process)