I'm just saying that's why I stopped using them, not that it's a differentiating factor between static and dynamic languages. I wrote books about Perl, I taught classes on Perl. Having to install stuff from CPAN was probably the most common complaint. I wrote a new CPAN client at some point, and it didn't help. Enough was enough; the approach failed and I moved on to writing my code some other way (as did all of those students, probably). npm seems to have gotten something that mostly works; I use that and tolerate it because I have no other choice for client-side stuff, but I don't really do enough browser programming to call myself a Javascript user.

Yes, static languages have dependency hell. I've ./configure'd a million times and have wanted to die about 80% of the time. I've used buildroot and have wanted to die 100% of the time. I never seriously programmed in C or C++ to say that I've stopped using them, so while they're broken... you can't stop using something that you haven't started using. (I still cringe when I see that some C-based project I want to use doesn't have binaries. It's especially annoying because I mostly use Windows now. I want "dc" in Powershell because that is my preferred calculator app... but can't compile it, and apparently neither can anyone else. Wow.)

Python is a pretty great programming language... but it's just not worth the tradeoffs. It is nice that bottle is one file; that is going to increase its adoption. It is not a solution to any general problem, though; the next library you depend on is going to require virtualenv and 100 dependencies, and they will fail to install.