> So, Instead of convenience I now have to hunt for some urls somewhere. Well yes.. but usually that is true for npm packages as well when one search for docum

> So, Instead of convenience I now have to hunt for some urls somewhere. Well yes.. but usually that is true for npm packages as well when one search for documentation or source code. > Deno is not a browser It tries hard to immitate the browser context and does so very successfully IMO. > From development point of view having to hunt down urls "in slack messages" is a nightmare. Well, that was just an example. I am just pointing out the concept of decentralization. You don't have to be reliant on npm and their systems. > In which manner? How does Deno know that a dependency X lives at url Y that was posted in a Slack channel somewhere? Since each dependency is an url, it will fetch all deps and download them in order to cache it. Pretty much how npm works as well, except that npm in reality only fetches from the npm registry even if I think it's possible to add github repos to the package.json. You also don't need a package.json which is great especially for smaller scripts. > Developers arguing that package management is bad is a new thing to me. It's not inherintly bad. I personally prefer to not be reliant on an american mega corporation which is known for it's anti-competitive practices and woke agenda. Their interest will certainly not align with mine. > How am I free to change it if a package I depend on specifies it dependency at a url x, and that package's dependencies specify them at url Y Well in that specific case you would need to download the entire tree and host it yourself. Then you can change the url. I mean, if you're happy with node and npm. Continue to use it. You don't have to switch to Deno but I am convinced it's the future for server side javascript. It's just... nicer in general.