They chose for a decentralised package management system whereas Node has a centralised one. A tradeoff as you mentioned is that you can't just take down malicious packages. I'm personally not too concerned with this because of the following:
1. The default permissions while running a script are stricter than Node's, you get told when your code tries to access your file system or network
2. Code I write for Deno typically uses fewer dependencies than the equivalent code for Node, simply because of how Deno has a good standard library with many web APIs
> the Deno teams stance on security is not so funny
1. The default permissions while running a script are stricter than Node's, you get told when your code tries to access your file system or network
2. Code I write for Deno typically uses fewer dependencies than the equivalent code for Node, simply because of how Deno has a good standard library with many web APIs
> the Deno teams stance on security is not so funny
Can you give examples of this?