Isn't that only a problem if you are only invested in the US? There exists ETFs that are invested in multiple developed countries, such as index funds that track the MSCI World.
The first page of their documentation [0] mentions this:
> Opening a database
> In your Deno program, you can get a reference to a KV database using Deno.openKv(). You may pass in an optional file system path to where you'd like to store your database, otherwise one will be created for you based on the current working directory of your script.
In fact, only the last page in the documentation speaks about KV on Deno Deploy.
When you’re trying to run a quick script or just want a “playground” environment where you can test your code, it holds you back.
For example: I’m making a web app with Svelte in TypeScript and I’m trying to test a part of its code. To do that, I have to build the app first because TypeScript needs transpiling which in turn needs bundling etc…
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