Thanks. My question really wasn't focused well, and it was easily read not as "please help me understand" but as "hurr durr Python is better". I think my react

Thanks. My question really wasn't focused well, and it was easily read not as "please help me understand" but as "hurr durr Python is better". I think my reaction comes from the dissonance between people saying "Deno is the best thing ever for CLI apps!" then following up with "Here are the ways it's better than Node!", without acknowledging all the other scripting languages out there. But I think I need to read that first line as having an implicit "...in the JS/TS ecosystem", and then it all makes sense. Since clearly one of Deno's draws is that it improves on the package management of Node, I was wondering why JS projects so often end up with such a long list of dependencies, compared to the Python/Go/C++ projects that I'm more familiar with. That's probably explained just by NPM making it easy, so people did it. (Sort of like how Java grew convoluted DI schemes because OO + GC + reflection made it possible.) One of these days I should learn more JS than having read through the Good Parts once. :-)