The problem is that most devs expect agility but many modules live for 10 years+ based on whatever they were based on back in the day with no real desire to rew

The problem is that most devs expect agility but many modules live for 10 years+ based on whatever they were based on back in the day with no real desire to rewrite it with the latest package management thingy. So then we end up with a mix of old and new and the promise of "moving to a bright new world" that just won't happen. As another poster said, since we know that package management is a pain, we should be able to solve all of these issues when we create a new language eco-system, not rush to get the exciting part released with "hello world" and wait for the problems to roll in later. Interestingly, nuget as a philosophy isn't terrible but there are extreme performance issues and crazy things like not tying a package to a specific feed so if you install it, it asks all of the feeds if it has a copy, most of which will 404. Updates usually take an age but once they are installed, it usually runs OK :-)