ok so package management and dependency solving are meant to cut down on bloat. you don’t get much in the way of dependencies on windows systems because, aside from like directx and .net everything comes packaged with the libraries it needs. so, you’re downloading the same libraries multiple times, having multiple copies hanging out on your system, bloating up the whole works. dependency checks cut down the cost of running and maintaining the system, and also the costs of hosting and distributing software (whether that’s online or offline distribution doesn’t matter, space and bandwidth are space and bandwidth).
it’s not without drawbacks in any system, even POSIX-compliant ones like haiku, gnu/linux or osx but considering the versatility of libraries (and the number of copies of multiple libraries you could have as a result) outweighs the inconvenience of (by this point, mostly automated, fast even on dial-up) dependency resolving.
and i won’t pretend for another second windows hasn’t had the same problem (and, without package management and automated dependency resolving, so very much worse) when .DLL hell is so very well known by anyone who’s lived in a windows system for a significant amount of time.