Discussion on: Getting Started with Deno 🦕

I got interested since it was promised to be a better version of node.js that's how far I got, and just started playing around with it.

I'm not too sure about the integrity of the imports.

I do believe once we deploy, it's all compiled, so no worry on the imports there.

i fail to see what deno is solving

I think deno is trying to be a "better node". How?

• Improved security. No file, network, or environment access, unless explicitly enabled.
• Better compatibility with web standards.
• Has common utilities built-in like a code formatter, a bundler and some others. Even typescript support is built-in.

Sound good, right? But do we need it? I don't know.

i wonder how is dealt/checked integrity of imports

The details of that are here: Integrity checking & lock files

what happens if we start deplaying deno and suddenly one single tiny online dependency is not available for undefined time frame

Even npm can fail, right? What do you do then?

In the case of deno you can choose to get your dependencies from a cdn, and just trust that it'll be there. The other option is to take the deno cache directory and put that on source control, they explain how here.