DEV Community

Discussion on: Deno is coming

Collapse
 
harshakns profile image
Narasimha Sriharsha KANDURI

i have few questions.
1) It doesn't have a centralized package management like package.json.
Q) Imagine you have two developers who install whatever they wish to get the work done. Does one need to check all those files to get the list of what dependencies are installed?

2)Secure by default. No file, network, or environment access, unless explicitly enabled.

Q) Is this a big thing? then do other languages have this feature by default? can't we manage by using user groups in unix based systems?

3)Supports TypeScript out of the box.
Q) can add type script support if i need whats the big deal?

4)Ships only a single executable file.
Q) i use linux and never had any problems like this can anyone explain why this is a big usp

5)Has built-in utilities like a dependency inspector (deno info) and a code formatter (deno fmt).
Q) npm, eslint and prettier => node + some scripts?

6)Has a set of reviewed (audited) standard modules that are guaranteed to work with Deno: deno.land/std
Q) does this mean all those tons of code on github which work with node are dead?