4 ms·
> "we added a bunch of complexity on top of the problem without actually solving it" It solved it as much as is possible within the current state of software d
by 0xbadcafebee 6y ago
> "we added a bunch of complexity on top of the problem without actually solving it"
It solved it as much as is possible within the current state of software design.
> Package managers are supposed to prevent conflicts and manage giant dependency graphs
Actually, they can't do that. They can look for the conflicts they're programmed to look for by packages, and they can walk dependency graphs that are generated by the packages in the repos maintained by a person. The root of the problem is that modern software architecture (even for trendy languages) cannot express the dependencies in the first place.
I wrote you an explanation, but it ran to 1,355 words, so I Gist'd it here https://gist.github.com/peterwwillis/e96854532f471c739983c0bba7608834 https://gist.github.com/peterwwillis/e96854532f471c739983c0b...