I think Deno is definitely an interesting project to take a look at, and it has some features that I like.
E.g. only having access to the network, file system etc. when it is explicitly allowed is a security measure, which is very important when your package relies on other third-party packages. By using these third-party packages you are always at the risk of the package getting compromised and it executing malicious code, using your package. This has already happened many times in the npm ecosystem and is one of the biggest problems of using npm. Restricting the access to important interfaces like the file system, reduces the risk of a compromised package causing any real harm on the system it is being run on.
Deno also instantly dies when any uncaught errors occur. This is good! You should NEVER EVER have any uncaught errors in your code, and it is really not hard to use try-catch blocks to catch errors. NodeJS is also working towards this, if an uncaught